Re: Status of samba ports
On Thu, Sep 19, 2019 at 4:54 PM Rick Miller wrote: > Hi, > > On Thu, Sep 12, 2019 at 7:13 AM Andrea Venturoli wrote: > >> Hello. >> >> I'd like some information WRT to the status of samba ports, what is >> [not] working, what *should* be working and what is planned. >> > > security/sssd with SMB enabled fails to build due to dependency conflicts > w/ Samba, which bundles ldb, tbd, tevent, and talloc. Previous to recent > commits in these past few months, it was possible to build Samba w/o the > bundled libraries, but those commits now install those by default. This > makes building security/sssd with SMB=on impossible. Several bug reports > describe the problem: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230705 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231846 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238465 > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230705> > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231846> > > A couple problems contribute to the complexity here: > > * security/sssd is woefully out of date at v1.11 while the project is > shipping v2.2 > * Samba bundles dependencies > * Recent commits to Samba ports have made it impossible to build SSSD w/ > SMB=on > > I've not been able to spend any time because of a plethora of competing > priorities though submitted patches can be tested with relative ease. That > said, my preference is to always build/install recent software and > dependencies. Maintaining old software and dependencies is too much work > for so little benefit. This is to say it would be good to see SSSD 2.2 with > a dependency on a recent Samba > It seems these conflicts arise from an incorrect dependency given the Samba default version described in PR 238465. Replacing the ldb14 dependency with ldb15 along with other configurations now build security/sssd that functions as desired. This configuration does not address the need to update security/sssd to a newer version however. — Rick > -- Take care Rick Miller ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Status of samba ports
Hi, On Thu, Sep 12, 2019 at 7:13 AM Andrea Venturoli wrote: > Hello. > > I'd like some information WRT to the status of samba ports, what is > [not] working, what *should* be working and what is planned. > security/sssd with SMB enabled fails to build due to dependency conflicts w/ Samba, which bundles ldb, tbd, tevent, and talloc. Previous to recent commits in these past few months, it was possible to build Samba w/o the bundled libraries, but those commits now install those by default. This makes building security/sssd with SMB=on impossible. Several bug reports describe the problem: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230705 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231846 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238465 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230705> <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231846> A couple problems contribute to the complexity here: * security/sssd is woefully out of date at v1.11 while the project is shipping v2.2 * Samba bundles dependencies * Recent commits to Samba ports have made it impossible to build SSSD w/ SMB=on I've not been able to spend any time because of a plethora of competing priorities though submitted patches can be tested with relative ease. That said, my preference is to always build/install recent software and dependencies. Maintaining old software and dependencies is too much work for so little benefit. This is to say it would be good to see SSSD 2.2 with a dependency on a recent Samba. -- Take care Rick Miller ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Status of samba ports
On Tue, 17 Sep 2019 08:55:00 -0400, Robert Huff stated: >Andrea Venturoli writes: > >> Sorry for being pedantic, but I believe a lot of us would benefit >> from some guidance: >> _ should we upgrade promptly to 4.10? Will it work or will it be a >> waste of time? >> _ should we stay on 4.8, because it will be the default on FreeBSD >> for a long time still? And will it be fixed? >> _ should we just wait for a (working) 4.11 to come our way? When >> will this happen? > > I'd prefer to wait for 4.11, assuming it appears in a > reasonable >time-frame. > What would encourage that would be a "migrating for dummies" >document from 4.8, as I understand this is not a trivial process. Samba announced the availability of Samba 4.11.0 for download. You might want to contact the samba port maintainer, ti...@freebsd.org, regarding when he plans to release it to the port system. -- Carmel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Status of samba ports
Andrea Venturoli writes: > Sorry for being pedantic, but I believe a lot of us would benefit from > some guidance: > _ should we upgrade promptly to 4.10? Will it work or will it be a waste > of time? > _ should we stay on 4.8, because it will be the default on FreeBSD for a > long time still? And will it be fixed? > _ should we just wait for a (working) 4.11 to come our way? When will > this happen? I'd prefer to wait for 4.11, assuming it appears in a reasonable time-frame. What would encourage that would be a "migrating for dummies" document from 4.8, as I understand this is not a trivial process. Respectfully, Robert Huff ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Status of samba ports
On 2019-09-12 13:13, Andrea Venturoli wrote: Hello. I'd like some information WRT to the status of samba ports, what is [not] working, what *should* be working and what is planned. ... Is it supposed to be production ready? What does and what does not work? Is there some page (wiki or whatever) that outlines the status of Samba on FreeBSD? Is there anything we can do to help? Hello. While we are still in the dark here, 4.11 was released today, obsoleting 4.8, which I think is the default version on FreeBSD. Sorry for being pedantic, but I believe a lot of us would benefit from some guidance: _ should we upgrade promptly to 4.10? Will it work or will it be a waste of time? _ should we stay on 4.8, because it will be the default on FreeBSD for a long time still? And will it be fixed? _ should we just wait for a (working) 4.11 to come our way? When will this happen? bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Status of samba ports
Hello. I'd like some information WRT to the status of samba ports, what is [not] working, what *should* be working and what is planned. I'm using samba48 at several sites and I'm obviously encountering the problem described in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239480 Today I tried a classicupgrade (with samba48) and it ended with a core dump of python2.7. I wasn't surprised at all, of course. Since this is (at least for now) a test, I decided to try 4.10: I was surprised to see a similar error! I know the problems with ACL/ZFS/etc... (in the past I had to apply patches and add extra argument to "samba-tool domain classicupgrade" or "samba-tool domain provision" to work around this). However, I wasn't expecting this to fail in a way similar to how 4.8 does, i.e. with the messages: INFO 2019-09-12 13:06:52,919 pid:4760 /usr/local/lib/python3.6/site-packages/samba/provision/__init__.py #2286: Setting up share.ldb Unable to find backend for '/var/db/samba4/private/share.ldb' - do you need to set LDB_MODULES_PATH? ERROR(ldb): uncaught exception - None File "/usr/local/lib/python3.6/site-packages/samba/netcmd/__init__.py", line 185, in _run return self.run(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/samba/netcmd/domain.py", line 1690, in run useeadb=eadb, dns_backend=dns_backend, use_ntvfs=use_ntvfs) File "/usr/local/lib/python3.6/site-packages/samba/upgrade.py", line 743, in upgrade_from_samba3 use_ntvfs=use_ntvfs, skip_sysvolacl=True) File "/usr/local/lib/python3.6/site-packages/samba/provision/__init__.py", line 2287, in provision share_ldb = Ldb(paths.shareconf, session_info=session_info, lp=lp) File "/usr/local/lib/python3.6/site-packages/samba/__init__.py", line 115, in __init__ self.connect(url, flags, options) If I understand correctly, the above problem with 4.8 is due to its dependency on Python 2.7; I thought 4.10, which is using Python 3.6, would not exhibit this behaviour... Any comment on this? I know I can try and build 4.8 with external dependencies; in fact I tried, but had no luck so far. Since Samba 4.8 will stop being supported in a very short time, I'd like to stop wasting my time with it and start moving to 4.10. Is it supposed to be production ready? What does and what does not work? Is there some page (wiki or whatever) that outlines the status of Samba on FreeBSD? Is there anything we can do to help? bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
