[Pkg-samba-maint] freeze planning for samba packages

Ivo De Decker ivo.dedecker at ugent.be
Sat May 26 20:52:45 UTC 2012


Fellow packagers,

With the freeze approaching, it's time to plan the final changes to the samba
packages for wheezy. Here are some suggestions. Please add yours.


Samba 3.6
=========

Samba 3.6.6 will (hopefully) be released soon, so we should be able to get it
in before the freeze. Christian, I suspect you plan to upload a package to
unstable soon after samba 3.6.6 is released?

Are there any bugs we still want to get fixed in wheezy, which have a clear
path to a solution, but which just need a little more work?


I would like to get a fix in for the shadow_copy problem (it doesn't work
without wide links). This has been fixed in master for some time now, but it
is unclear if the fix will be backported upstream in time for samba 3.6.6. If
there are no objections, I will prepare a patch for this, which can be
included in the 3.6.6 debian package upload (if upstream doesn't include it
already). This way, the fixed version of the shadow_copy2 module can be in
wheezy.
https://bugzilla.samba.org/show_bug.cgi?id=7287

Christian, is there any news on the 'force user' bug you talked about?
https://bugzilla.samba.org/show_bug.cgi?id=8598


Samba 4
=======

The situation for Samba 4 is more complicated.

The current package in unstable is blocked for 2 reasons:

- tdb doesn't build on some archs, because a test in the testsuite fails.
  Based on Rusty's mail, it seems the test is fairly recent, so the issue has
  probably been there for some time. I think the best solution is to disable
  this specific test for now. I have a patch more or less ready for this, that
  will be uploaded to the BTS shortly.
  Jelmer, how do you want to handle this? Do you have time to look at this
  yourself, or do you want someone else to upload a fix?

- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670413
  The samba4 package fails to configure correctly on first installation. I
  haven't investigated this bug yet, but I can easily reproduce it.

If we want to get Samba4 in wheezy, we should get a package in testing before
the freeze.

Other open issues:

- Jelmer mentioned that it is probably best to rename some binary packages and
  to remove those that will not be part of the final samba4 release.

- With the last alpha released, the first beta of samba4 should appear next
  week. It seems obvious that this should be the version that goes into
  wheezy.

- During the freeze, a lot of important fixes will go into samba4 upstream.
  I don't really know how these should be handled, but with 2 release wizards
  on the team, it should be no problem to clarify this :)


Cheers,

Ivo




More information about the Pkg-samba-maint mailing list