Now that Samba 4 is out it's time to unmask it. I talked upstream and if there are major issues with config files it can be slotted without any problems. I'm about to do some tests in a VM. If others would like to join me that would be great.
# Patrick Lauer <email@example.com> (07 Apr 2010)
# Keeping samba-4 masked until release.
We'll need re-keywording for all except x86 and amd64, too.
There's an issue or two with the current ebuild.
First of all, it seems '--with-modulesdir=' option has been misunderstood both in net-fs/samba *and* in sys-libs/ldb.
There's much that suggests, that in *both* the value should be '/usr/$(get_libdir)/samba' - simply compare with samba3 install.
On that note, /usr/lib/mit_samba.so looks out of place, but I can't say where it should belong, if not there.
That line for 'Make all .so files executable' seem redundant, though perhaps didn't build with all useflags set, so I might be missing a file or two.
It would be nice if 'server' useflag got restored (also gvfs has samba[smbclient] dep that this ebuild doesn't satisfy).
On a final note: I've got a hack that makes samba4 build with heimdal[ssl], though it obviously needs work (and needs dev-libs/openssl instead).
Created attachment 332180 [details, diff]
hack for heimdal[ssl]
They don't support mit-krb5 for domain controllers.
Given that samba ebuild has just been changed in regard of that module path, perhaps ldb ebuild should be too ?
That would remove the need for those moves in samba ebuild.
Now that samba-4.1.0 was released we should finally unmask samba-4.0.x:
09:49:48 <@Poly-C_atwork> DrEeevil: IMHO we should at least provide some portage news item.
09:50:20 <@Poly-C_atwork> And we should target that to samba-4.0.x as I think 4.1.x is way too early for unleashing to ~arch right now.
So anything else we need to consider?
well, I think it's time to unmask it now, because Windows 8.1 don't play well with samba 3.6.x, every login need to input twice password, so because of UAC, there is no chance to login second time with admin privilege, and that makes impossible to install any software placed on a samba server with windows 8.1.
What happened to this, are we going to unmask?
Created attachment 376356 [details, diff]
updated version of the hack - builds with samba 4.1.7
When will Samba 4.1.13 be unmasked? Whould be nice to give it a try. Samba 4 was released in 2012. Why does it take such a long time to be availabe in Gentoo for the users? I recognized the the bugs this bug is depending on...
It seems like Samba 3.x is being discontinued upstream when 4.2 is released - please see: https://download.samba.org/pub/samba/rc/WHATSNEW-4.2.0rc3.txt
+ 07 Mar 2015; Lars Wendler <firstname.lastname@example.org> package.mask:
+ Unleash samba-4 to ~arch
Asking for QA involvement here.
This bug is blocked by a number of tracked bugs which nobody bothered to fix before unmasking. Now users are having those issues, and I don't see anyone stepping up to fix them.
Seconded here. At the very least please apply already proposed patch to use internal heimdal library. At least this will fix mutual block with mit-krb5 and all related software. At this very case bundled library is a good solution, probably the best we have available in practical terms.
This bug is pointless now that samba is unmasked.
Any bug that needs to be tracked, please add it to bug 489762