On Mar 13, 2025, at 00:29, Xavier Beaudouin <[email protected]> wrote: > I think there is some ports that have dependencies with sudo and Mark may > need sudo with sssd flavor... > > Is this the case ? > > Kind regards, > Xavier > > ----- Mail original ----- >> De: "Gleb Popov" <[email protected]> >> À: "Mark Millard" <[email protected]> >> Cc: "FreeBSD Mailing List" <[email protected]> >> Envoyé: Jeudi 13 Mars 2025 07:08:25 >> Objet: Re: sudo-1.9.16p2_1 [. . .] conflicts with sudo-sssd-1.9.16p2_1 [. . >> .] on /usr/local/bin/cvtsudoers > >> On Thu, Mar 13, 2025 at 8:41 AM Mark Millard <[email protected]> wrote: >>> >>> ... >> >> Why do you need both of these installed?
I simply updated a previously working environment via pkg using my historical file listing origins (both platforms). The behavior is new in my context. My file of origins to update/install has historically explicitly listed security/sudo and still does at this point. I've never had an explicit reference to sudo-sssd or sssd2 in that file or made manually. My guess is that something that I reference has gained a dependency (possibly indirectly). I've not investigated yet. https://cgit.freebsd.org/ports/tree/UPDATING does not mention sudo more recently than the 20231027 entry. Nor does it mention sudo-sssd or sssd2 . (But this was not a source-based update context.) If nothing else, a forced mutual exclusion should be documented if it is going to exist. === Mark Millard marklmi at yahoo.com
