From owner-svn-ports-all@freebsd.org Tue Jul 2 19:28:18 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 3445315DB602 for ; Tue, 2 Jul 2019 19:28:18 +0000 (UTC) (envelope-from timur@bat.ru) Received: from mail-oi1-f179.google.com (mail-oi1-f179.google.com [209.85.167.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9AEC6CAD5 for ; Tue, 2 Jul 2019 19:28:17 +0000 (UTC) (envelope-from timur@bat.ru) Received: by mail-oi1-f179.google.com with SMTP id e189so14019510oib.11 for ; Tue, 02 Jul 2019 12:28:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=E9G4bmY0k3w3rH8mBX6riDOI5KF1WHajl/g6Oghla/A=; b=d8289sHBqb6ho8Ar9v4OL35DS8shUSFsBAuj3m3pDMfQDJRAO/8+UOakL3Sf4vmzt/ OSD8ELQBVCGr0FYXMdizsFn+Jz7pEjdq75QhZDlujXfOKWuwKjfPb5Ju96SF91K6Ak0O /+0RqF+vn0hRB9AGKgeaqvtGxbKq6GgSVogIMVkFOHdX2z4eH+71/xI9L+tqNHnOsKVd Wg+zTqDS/GDCHmy1P3T7O4vTwSB7DbQxOab/nVeqGFjtutCESkwCIY8QQ6cs9kWAEZfR 9VBEDDGwF39N89bqWTgwGTbww/sP+vtu4J7P36/45NQmblcd3xXCPJOCL8m4wmSKI+En sS5A== X-Gm-Message-State: APjAAAX6kq+ijIaP3ULCsSZNKBHpIr5bQUP++C42Ml94te4pBIrFAN+o GAXjK+tQadjzKx0KAvhf8Cpn4H/SlNE0Ss4U9SBLpA== X-Google-Smtp-Source: APXvYqx0ru2V67hqgMfFk3pnpPXuT7XTyJArM5cm48n/DKOuPUR5M7JPogit77lBhyxXQJtX25AS/mNkCo92LKoyP4g= X-Received: by 2002:aca:5346:: with SMTP id h67mr3750406oib.55.1562095696445; Tue, 02 Jul 2019 12:28:16 -0700 (PDT) MIME-Version: 1.0 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> <38AAD2AA-702E-4285-8C77-22DEB00810B6@FreeBSD.org> In-Reply-To: <38AAD2AA-702E-4285-8C77-22DEB00810B6@FreeBSD.org> From: "Timur I. Bakeyev" Date: Tue, 2 Jul 2019 21:27:48 +0200 Message-ID: Subject: Re: svn commit: r504590 - in head/net: samba46 samba47 samba48 To: Baptiste Daroussin Cc: =?UTF-8?Q?T=C4=B3l_Coosemans?= , ports-committers@freebsd.org, svn-ports-all , svn-ports-head X-Rspamd-Queue-Id: A9AEC6CAD5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.94 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_SHORT(-0.94)[-0.944,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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:28:18 -0000 On Tue, 2 Jul 2019 at 21:24, Baptiste Daroussin wrote: > > > Le 2 juillet 2019 20:45:21 GMT+02:00, "Timur I. Bakeyev" < > timur@freebsd.org> 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. 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. Bakeyev" > > > >> a > >> > >> =C3=A9crit : > >> > >>> Tonight I hope to commit 4.10 port. > >> > >> > >> > >> 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. > >> > > > >> > > 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. The biggest difference is the drop of the dependency on > >> Python27, > >> > > as far as I can see. > >> > > > >> > > New Samba port doesn't use external databases/ldb*, so > >security/sssd > >> may > >> > > use any of those freely now. > >> > > > >> > > The samba4[47] are outdated and should disappear in the middle of > >the > >> > > August. > >> > > > >> > > The samba48 will remain for a while, but not for long, as > >samba411 us > >> > > pushing from behind. It'll be (hopefully) > >> > > the only consumer of the talloc1/tevent1/tdb1 ports, which should > >> disappear > >> > > together with Samba 4.8. > >> > > > >> > > In general I'd prefer to see SAMBA_DEFAULT to be bumped to 410, > >but > >> this is > >> > > up to the portmgr. > >> > > >> > 4.8 goes EoL upstream mid-September (about 2 weeks before Q4), so > >> > making 4.10 now would be good, but I believe it's just too late for > >> > that. 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. > >> > > >> > Since you said that the new libs are API compatible, is it possible > >to > >> > make 4.8 use the new libs? If not, then all non-samba consumers > >will > >> > have to switch to the legacy libs. They can be switched back after > >the > >> > 2019Q3 branch has been created (together with making 4.10 the > >default > >> > which probably needs an exp-run). > >> > >> It is and I tried to build everything with the new lib. 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. > >> > >> 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. > >> > > > >No, you are wrong. It MAY look like the LDB libs are almost the same > >crom > >1.1-1.6 branches, > >but there is the reason why developers don't stick to one branch cross > >different versions of > >Samba. > > > >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. > >We went through > >that when Perl-Parse-Pidl was used cross several versions of Samba and > >the > >results were > >disastrous. > > > > Thanks for clarification! > > > > >> For the set of library yes they are fully backward compatible > >according to: > >> https://abi-laboratory.pro/index.php?view=3Dtimeline&l=3Dtalloc > >> https://abi-laboratory.pro/index.php?view=3Dtimeline&l=3Dtevent > >> https://abi-laboratory.pro/index.php?view=3Dtimeline&l=3Dtdb > >> > >> the problem is on the python binding if any. > >> > >> The current situation is a big mess for end users of those libraries! > >> > > > >Here I absolutely agree.The 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. > > > >As an effort to address concerns of Samba 4.8 users I altered the port, > >with few knobs set to completely > >build with the bundled libraries, not using any from outside. > > > >I hope this is good enough solution for those, who want to have a > >mixture > >of Samba 4.8, SSSD and other consumers > >of talloc/tdb/ldb in one system. > > > >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 > good fix if the default is to bundle ( the build packages use the default > options) > > If not can you make it default so we can branch the quarterly, and start > building packages ? > Ok, let me check that it also works in such configuration at least for the basic file server. AD almost always is the matter of manual build. With regards, Timur.