From owner-svn-ports-all@freebsd.org Tue Jul 2 19:24:40 2019 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E55E915DB513; Tue, 2 Jul 2019 19:24:39 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7FA886C83B; Tue, 2 Jul 2019 19:24:39 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from ivaldir.etoilebsd.net (etoilebsd.net [178.32.217.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 25BDA606; Tue, 2 Jul 2019 19:24:39 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from [192.168.0.104] (91-166-102-26.subs.proxad.net [91.166.102.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ivaldir.etoilebsd.net (Postfix) with ESMTPSA id 93F2FB97D2; Tue, 2 Jul 2019 21:24:37 +0200 (CEST) Date: Tue, 02 Jul 2019 21:24:37 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: <201906192240.x5JMequU017187@repo.freebsd.org> <20190628070305.eim4o3d77iyti5d5@ivaldir.net> <20190629160445.051f2426@kalimero.tijl.coosemans.org> <20190702141756.1f0b14b7@kalimero.tijl.coosemans.org> <20190702122219.lqecdgrgpkhtkeqk@ivaldir.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: svn commit: r504590 - in head/net: samba46 samba47 samba48 To: "Timur I. Bakeyev" CC: =?UTF-8?Q?T=C4=B3l_Coosemans?= , ports-committers@freebsd.org, svn-ports-all , svn-ports-head From: Baptiste Daroussin Message-ID: <38AAD2AA-702E-4285-8C77-22DEB00810B6@FreeBSD.org> X-Rspamd-Queue-Id: 7FA886C83B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.982,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2019 19:24:40 -0000 Le 2 juillet 2019 20:45:21 GMT+02:00, "Timur I=2E Bakeyev" a =C3=A9crit : >On Tue, 2 Jul 2019 at 20:26, Baptiste Daroussin >wrote: > >> On Tue, Jul 02, 2019 at 02:17:56PM +0200, T=C4=B3l Coosemans wrote: >> > On Mon, 1 Jul 2019 01:23:34 +0200 "Timur I=2E Bakeyev" > >> > wrote: >> > > On Sat, 29 Jun 2019 at 22:50, Baptiste Daroussin > >> wrote: >> > >> Le 29 juin 2019 20:40:53 GMT+02:00, "Timur I=2E Bakeyev" > >> a >> > >> =C3=A9crit : >> > >>> Tonight I hope to commit 4=2E10 port=2E >> > >> >> > >> It does not solve rhe pb, staying on the legacy libs is the >solution, >> as I >> > >> said even fedora is on the legacy >> > >> >> > > I've committed net/samba410=2E >> > > >> > > My view on the situation is that all the ports, which use >> > > devel/{talloc,tevent}, databases/tdb should keep >> > > using them, unless they are broken by using them(but that >shouldn't >> happen, >> > > API still should remain >> > > the same=2E The biggest difference is the drop of the dependency on >> Python27, >> > > as far as I can see=2E >> > > >> > > New Samba port doesn't use external databases/ldb*, so >security/sssd >> may >> > > use any of those freely now=2E >> > > >> > > The samba4[47] are outdated and should disappear in the middle of >the >> > > August=2E >> > > >> > > The samba48 will remain for a while, but not for long, as >samba411 us >> > > pushing from behind=2E It'll be (hopefully) >> > > the only consumer of the talloc1/tevent1/tdb1 ports, which should >> disappear >> > > together with Samba 4=2E8=2E >> > > >> > > In general I'd prefer to see SAMBA_DEFAULT to be bumped to 410, >but >> this is >> > > up to the portmgr=2E >> > >> > 4=2E8 goes EoL upstream mid-September (about 2 weeks before Q4), so >> > making 4=2E10 now would be good, but I believe it's just too late for >> > that=2E A port like this needs at least a few weeks of wider testing >> > before it can be pushed to users of the quarterly branches who >expect >> > more stability=2E >> > >> > Since you said that the new libs are API compatible, is it possible >to >> > make 4=2E8 use the new libs? If not, then all non-samba consumers >will >> > have to switch to the legacy libs=2E They can be switched back after >the >> > 2019Q3 branch has been created (together with making 4=2E10 the >default >> > which probably needs an exp-run)=2E >> >> It is and I tried to build everything with the new lib=2E the problem I >am >> stuck >> with is the following, to have ldb12 building with new talloc, I need >to >> build >> it without python, but I don't know what is the impact of that to end >> users=2E >> >> My understading is any samba should be able to run with any ldb >version >> which >> makes me wonder why we have that many version in the tree instead of >> always the >> latest one=2E >> > >No, you are wrong=2E It MAY look like the LDB libs are almost the same >crom >1=2E1-1=2E6 branches, >but there is the reason why developers don't stick to one branch cross >different versions of >Samba=2E > >At least, NO ONE gives the guarantee, that the intermix of LDB and >Samba >versions will >work as intended and you won't hit any obscure and hard to pin point >bugs=2E >We went through >that when Perl-Parse-Pidl was used cross several versions of Samba and >the >results were >disastrous=2E > Thanks for clarification! > >> For the set of library yes they are fully backward compatible >according to: >> https://abi-laboratory=2Epro/index=2Ephp?view=3Dtimeline&l=3Dtalloc >> https://abi-laboratory=2Epro/index=2Ephp?view=3Dtimeline&l=3Dtevent >> https://abi-laboratory=2Epro/index=2Ephp?view=3Dtimeline&l=3Dtdb >> >> the problem is on the python binding if any=2E >> >> The current situation is a big mess for end users of those libraries! >> > >Here I absolutely agree=2EThe said commit was trying to put in line all >the >consumers of the related libraries, >leaving legacy to where it belongs - behind, but we got unhappy Matt=2E > >As an effort to address concerns of Samba 4=2E8 users I altered the port, >with few knobs set to completely >build with the bundled libraries, not using any from outside=2E > >I hope this is good enough solution for those, who want to have a >mixture >of Samba 4=2E8, SSSD and other consumers >of talloc/tdb/ldb in one system=2E > >My only concern now - should it be the default for the port or just >documented in the UPDATING? > >With regards, >Timur I haven t checked yet your commit, will do tomorrow, this sounds like a go= od fix if the default is to bundle ( the build packages use the default opt= ions) If not can you make it default so we can branch the quarterly, and start b= uilding packages ? Thank you, Best regards, Bapt