[Pkg-samba-maint] First tests on 3.2.0-pre2

[Christian Perrier]

Yesterday and today, I did preliminary tests to package 3.0.2-pre2.

I used the debian/ directory from branches/experimental (the one used
for 3.2.0-pre1 we have in experimental).

What I did up to now on patches:

cups.patch
 -->no change
documentation.patch
 -->deactivated (manpages have been messed up upstream)
fhs-newpaths.patch
 -->applied upstream (sligthly differently but seems consistent)
fhs-filespaths.patch
 -->applied upstream (sligthly differently but seems consistent)
fhs-filespaths-debatable.patch
 -->much lighter
    Most of it have been applied upstream
    We still have changes for the location of:
    - winbindd_cache.tdb: we use "cachedir", upstream uses "lockdir"
                          upstream says this should be persistent
                          across reboots
    - secrets.tdb: upstream uses private_dir, we use state_dir: weird?
    - printing.tdb: upstream uses lockdir, we use cachedir. upstream
                    says it should be persistent across reboots
                    ditto for printing/
    - gpo cache (gpo_fetch.c): upstream uses lockdir, we use cachedir
    - idmap_cache.tdb: upstream uses lockdir, we use cachedir
                       IIRC, upstream also said that this should
                       be preserved across reboots
               
        
fhs-assignpaths.patch
 -->kept. But changes are now in source/configure and no longer
          source/configure.in
installswat.sh.patch
 -->kept
non-linux-ports.patch
 -->kept
pam-examples.patch
 -->kept
README_nosmbldap-tools.patch
 -->kept
no_smbmount_symlink.patch
 -->dropped as upstream drops smbfs support
smbclient-pager.patch
 -->kept
smbmount-mtab-flags.patch
 -->dropped as upstream drops smbfs support
smbmount-nomtab.patch
 -->dropped as upstream drops smbfs support
smbstatus-locking.patch
 -->dropped as upstream drops smbfs support
undefined-symbols.patch
 -->kept (very slightly adapted)
VERSION.patch
 -->kept (and modified, as usual)
#adapt_machine_creation_script.patch
 -->deactivated (manpages have been messed up upstream)
autoconf.patch
 -->kept (and modified, as usual)
#missing_userspace_bugzilla999.patch
 -->apparently applied
#linux-cifs-user-perms.patch
 -->apparently applied. TO CHECK !
cifs-umount-trailing-slashes.patch
 -->kept (and modified, as usual)
#cifs-umount-same-user.patch
 -->applied upstream
smbpasswd-syslog.patch
 -->kept (very slightly adapted)


In summary, what I would like to get comments about is:


fhs-filespaths-debatable.patch:

  We seem to have a strategical choice to make here. Either drop the
  patch and get closer of upstream's behaviour. That would need to
  move files for our users during upgrades. Or we keep the remaining
  changes...

linux-cifs-user-perms.patch:

  I'm unsure about upstream changes being the same than ours. I need
  some expertise here.

missing_userspace_bugzilla999.patch:
  Same questions

I didn't commit possibles changes to the SVN because I still need to
test the package build...but, please already comment if you can.

-- 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20080306/fdb3af34/attachment.pgp