From owner-freebsd-ports@freebsd.org Thu Sep 12 11:13:33 2019 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 059F0F2C76 for ; Thu, 12 Sep 2019 11:13:33 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (net-2-44-121-52.cust.vodafonedsl.it [2.44.121.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mailserver.netfence.it", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Tbjl45XBz47gQ; Thu, 12 Sep 2019 11:13:31 +0000 (UTC) (envelope-from ml@netfence.it) Received: from guardian.ventu (88-147-119-21.v4.ngi.it [88.147.119.21] (may be forged)) (authenticated bits=0) by soth.netfence.it (8.15.2/8.15.2) with ESMTPSA id x8CBDOve094505 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 12 Sep 2019 13:13:25 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host 88-147-119-21.v4.ngi.it [88.147.119.21] (may be forged) claimed to be guardian.ventu From: Andrea Venturoli Subject: Status of samba ports To: timur@FreeBSD.org, freebsd-ports@freebsd.org Message-ID: Date: Thu, 12 Sep 2019 13:13:23 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.83 X-Rspamd-Queue-Id: 46Tbjl45XBz47gQ X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of ml@netfence.it has no SPF policy when checking 2.44.121.52) smtp.mailfrom=ml@netfence.it X-Spamd-Result: default: False [-2.81 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994,0]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[netfence.it]; IP_SCORE(-1.72)[ip: (-5.57), ipnet: 2.44.0.0/16(-2.79), asn: 30722(-0.27), country: IT(0.03)]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:30722, ipnet:2.44.0.0/16, country:IT]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2019 11:13:33 -0000 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.