Hi Steve, On Sat, Oct 19, 2013 at 10:16:31AM -0700, Steve Langasek wrote: > Ok. I think we need to undo this /var/lib/samba/private nonsense. It is a > pointless and imperfect migration (as shown by this bug report), and the > only rationale upstream ever gave for keeping these files in a separate > "private" directory is some stupid and ancient target OS that couldn't > properly set per-file permissions. Debian users have been using > /var/lib/samba exclusively for the better part of a decade; migrating to > this private/ directory adds no value for our users.
The samba4 packages use /var/lib/samba/private, so upgrading from those (and from the earlier samba 4.0.x packages in experimental and unstable) would need some work. Obviously this would impact a much smaller group of users than the upgrade from samba 3.6 to 4.0. On the other hand, I also think we should at least consider the upstream request to avoid having this change reverted. As this won't be sorted out in the next few days, and I want to get the other improvements into unstable, I added a check in postinst which should at least abort instead of silently using the wrong data. I intend to upload this fairly soon. This change doesn't preclude a move either way. Obviously, this also doesn't fix this bug. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
