Date: Mon, 30 Sep 2019 11:42:55 -0400 From: Rick Miller <vrwmiller@gmail.com> To: Andrea Venturoli <ml@netfence.it> Cc: freebsd-ports <freebsd-ports@freebsd.org>, timur@freebsd.org Subject: Re: Status of samba ports Message-ID: <CAHzLAVG9Vz8KoTV7UEtH%2BiOyLwnW8CXgkgQtm278Zov4Az03dQ@mail.gmail.com> In-Reply-To: <CAHzLAVGrVQP0adWW8uUvjj=3zQbn=Wm-ZGs2ML64zz=E1yaE8w@mail.gmail.com> References: <adfc315a-8f79-7b64-3bfc-14be00615fb0@netfence.it> <CAHzLAVGrVQP0adWW8uUvjj=3zQbn=Wm-ZGs2ML64zz=E1yaE8w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 19, 2019 at 4:54 PM Rick Miller <vrwmiller@gmail.com> wrote: > Hi, > > On Thu, Sep 12, 2019 at 7:13 AM Andrea Venturoli <ml@netfence.it> 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=3Don impossible. Several bug repor= ts > describe the problem: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230705 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231846 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238465 > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230705>; > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231846>; > > 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=3Don > > 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. Tha= t > 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 wi= th > 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. =E2=80=94 Rick > -- Take care Rick Miller
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVG9Vz8KoTV7UEtH%2BiOyLwnW8CXgkgQtm278Zov4Az03dQ>