On Mon, Aug 01, 2016 at 02:47:33PM +0200, L.P.H. van Belle wrote: > Hai > > Yes, I totaly understand this, but i do have a problem with fixing 4.2.10. in debian. 4.2.10 in debian needs fixing, totaly agree on that, but due to the many changes between 4.1.x <=> 4.2.x im not totaly conviced to put all the time in the 4.2.x fixes, i'll explain why. > > The 4.2.10 packages are (sorry) bad. > I used them about 15 min after that i started recompiling again, started with the 4.3.9 at that time and i moved quickly to 4.4.3. as of this point im getting good results in my network. Similar regressions that existed in upstream 4.2.10 existed in 4.3.7 and 4.4.2; both were released to fix the same set of security issues. 4.3.9, 4.4.3 and 4.2.12 were subsequently released to fix the regressions in the security releases. This is why 4.2.14 needs to be uploaded to jessie-updates. > 4.2.10 has lots of regression bugs, files packaged in wrong packages, things like that, which also give problems when upgrading to higher version. > Im not flaming here, its just as it is now, not good, and i want beter samba packages for everybody not just me. > Even its really out of the normal scope, i would propose that to update samba (again) in stable to 4.4.5. > Beside that, Debian Stretch is about to start to freeze in three months. > And Q3 the "Please finish up things for Stretch", should be adressed also. > ( see my bug report 832880 ) > This all automaticly resolves a lot of bugs since these are fixed in upsteam samba already and in my opinion the 4.4.5 are very stable and better for production use as 4.2.x is. ( same for 4.4.3). If there are serious issues in upstream Samba 4.2 that are not fixed by 4.2.14, we can look at backporting them. But please let us know what they are by filing detailed bug reports and if possible linking to the relevant bug in the upstream bug tracker. Uploading a new major version of Samba to stable is risky, as we have seen with the update to 4.2.10 in jessie. Normally, we have the Debian release process to iron out major bugs in the upstream code as well as the packaging. Unfortunately the set of security patches that prompted 4.2.10 and 4.3.7 to be released was not available for Samba 4.1, and it is so large that it is not easily or reliably backportable to 4.1 (~200 patches). This is why we opted to upload a new major Samba version to jessie. Bug 832880 is a bug in the unstable package, not the jessie package. Cheers, Jelmer > > -----Oorspronkelijk bericht----- > > Van: Andrew Bartlett [mailto:abartlet@samba.org] > > Verzonden: vrijdag 29 juli 2016 0:41 > > Aan: Alexander Wirt; L.P.H. van Belle > > CC: Jelmer Vernoo??; debian-backports@lists.debian.org; ivodd@debian.org; > > Achim Gottinger > > Onderwerp: Re: samba 4.4.5 backports > > > > On Thu, 2016-07-28 at 10:33 +0200, Alexander Wirt wrote: > > > On Thu, 28 Jul 2016, L.P.H. van Belle wrote: > > > > > > > Hai, > > > > > > > > > > > > > > > > Im ready to upload samba and its needed dependecies to jessie > > > > backports. > > > > Samba 4.4.5 amd64 and i386 > > > As is already said, we won't accept the package unless a regular > > > samba > > > maintainer backs that backport. > > > > Just to be clear, as everyone seems to be piling on here, Louis has > > been encouraged by myself to undertake this work. > > > > That said, Jelmer is correct about us needing, as a team, to be able to > > handle the current workload before we proceed further. > > > > Louis, > > > > Thanks for what you have done so far. I hope to get a chance to look > > into it soon. However, Jelmer is right, if you could help us out with > > the packages we have already (we need current 4.2 packaged for stable, > > for example), that would go a long way to showing that we have the > > sustainable level of help we need to also have a backport. > > > > (That is, our Debian stable users are rightly screaming about the > > issues in the 4.2 release that are not being addressed in a timely > > manner, we need to get that under control before we add 4.4 or 4.5 to > > the mix). > > > > I realise this might feel like a bit of a bait-and-switch, but it > > really will help us over-all. > > > > Thanks, > > > > Andrew Bartlett > > > > -- > > Andrew Bartlett > > https://samba.org/~abartlet/ > > Authentication Developer, Samba Team https://samba.org > > Samba Development and Support, Catalyst IT > > https://catalyst.net.nz/services/samba > > > > > > > >
Attachment:
signature.asc
Description: PGP signature