Bug#963971: [Pkg-samba-maint] Bug#963971: samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency
On Sat, Jul 04, 2020 at 03:21:03PM +0200, Mathieu Parent wrote: Le sam. 4 juil. 2020 à 15:15, Michael Stone a écrit : On Sat, Jul 04, 2020 at 07:28:32AM +0200, Mathieu Parent wrote: >clone 963971 -1 >tag 963971 + upstream >tag -1 + upstream fixed-upstream patch >reassign -1 sssd-ad-common > >Le lun. 29 juin 2020 à 14:48, Michael Stone a écrit : >> >> Package: samba-libs >> Version: 2:4.12.3+dfsg-2 >> Severity: critical >> Justification: breaks the whole system >> >> The new samba-libs package changes the soname of libndr from libndr.so.0 to >> libndr.so.1 without reflecting this change in the package name. sssd-ad-common >> has a dependency on samba-libs (>= 2:4.11.5+dfsg) and links to libndr.so.0. >> When the samba-libs package is updated and libndr.so.0 disappears sssd fails to >> start, which then makes a system's remote users unavailable. (Worse, this >> doesn't happen until the next time sssd restarts--which may not be until the >> next reboot.) > >It looks to be fixed in sssd 2.3.0: >https://github.com/SSSD/sssd/commit/bc56b10aea999284458dcc293b54cf65288e325d > >I'm cloning this bug: >- on the samba side I'll add a breaks: sssd-ad-common (<< 2.3.0) >- on the sssd side, an update to 2.3.0+ is needed Going forward, do things using samba-libs need a strict version depenedency since there is no ABI version in the package name? No, I think. According to the sssd commit, sssd 2.3 will still build on older samba-libs. Not a build-time dependency, a run-time dependency; if there is no guarantee that the ABI is stable between versions, a dependency on "samba-libs >= something" simply isn't valid. (Packages built from the samba source package already have a dependency on "samba-libs = version" but there currently isn't anything telling other packages that the dependencies need to work that way.)
Bug#963971: [Pkg-samba-maint] Bug#963971: samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency
Le sam. 4 juil. 2020 à 15:15, Michael Stone a écrit : > > On Sat, Jul 04, 2020 at 07:28:32AM +0200, Mathieu Parent wrote: > >clone 963971 -1 > >tag 963971 + upstream > >tag -1 + upstream fixed-upstream patch > >reassign -1 sssd-ad-common > > > >Le lun. 29 juin 2020 à 14:48, Michael Stone a écrit : > >> > >> Package: samba-libs > >> Version: 2:4.12.3+dfsg-2 > >> Severity: critical > >> Justification: breaks the whole system > >> > >> The new samba-libs package changes the soname of libndr from libndr.so.0 to > >> libndr.so.1 without reflecting this change in the package name. > >> sssd-ad-common > >> has a dependency on samba-libs (>= 2:4.11.5+dfsg) and links to libndr.so.0. > >> When the samba-libs package is updated and libndr.so.0 disappears sssd > >> fails to > >> start, which then makes a system's remote users unavailable. (Worse, this > >> doesn't happen until the next time sssd restarts--which may not be until > >> the > >> next reboot.) > > > >It looks to be fixed in sssd 2.3.0: > >https://github.com/SSSD/sssd/commit/bc56b10aea999284458dcc293b54cf65288e325d > > > >I'm cloning this bug: > >- on the samba side I'll add a breaks: sssd-ad-common (<< 2.3.0) > >- on the sssd side, an update to 2.3.0+ is needed > > Going forward, do things using samba-libs need a strict version > depenedency since there is no ABI version in the package name? No, I think. According to the sssd commit, sssd 2.3 will still build on older samba-libs. Regards -- Mathieu Parent
Bug#963971: [Pkg-samba-maint] Bug#963971: samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency
On Sat, Jul 04, 2020 at 07:28:32AM +0200, Mathieu Parent wrote: clone 963971 -1 tag 963971 + upstream tag -1 + upstream fixed-upstream patch reassign -1 sssd-ad-common Le lun. 29 juin 2020 à 14:48, Michael Stone a écrit : Package: samba-libs Version: 2:4.12.3+dfsg-2 Severity: critical Justification: breaks the whole system The new samba-libs package changes the soname of libndr from libndr.so.0 to libndr.so.1 without reflecting this change in the package name. sssd-ad-common has a dependency on samba-libs (>= 2:4.11.5+dfsg) and links to libndr.so.0. When the samba-libs package is updated and libndr.so.0 disappears sssd fails to start, which then makes a system's remote users unavailable. (Worse, this doesn't happen until the next time sssd restarts--which may not be until the next reboot.) It looks to be fixed in sssd 2.3.0: https://github.com/SSSD/sssd/commit/bc56b10aea999284458dcc293b54cf65288e325d I'm cloning this bug: - on the samba side I'll add a breaks: sssd-ad-common (<< 2.3.0) - on the sssd side, an update to 2.3.0+ is needed Going forward, do things using samba-libs need a strict version depenedency since there is no ABI version in the package name?
Bug#963971: [Pkg-samba-maint] Bug#963971: samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency
clone 963971 -1 tag 963971 + upstream tag -1 + upstream fixed-upstream patch reassign -1 sssd-ad-common Le lun. 29 juin 2020 à 14:48, Michael Stone a écrit : > > Package: samba-libs > Version: 2:4.12.3+dfsg-2 > Severity: critical > Justification: breaks the whole system > > The new samba-libs package changes the soname of libndr from libndr.so.0 to > libndr.so.1 without reflecting this change in the package name. sssd-ad-common > has a dependency on samba-libs (>= 2:4.11.5+dfsg) and links to libndr.so.0. > When the samba-libs package is updated and libndr.so.0 disappears sssd fails > to > start, which then makes a system's remote users unavailable. (Worse, this > doesn't happen until the next time sssd restarts--which may not be until the > next reboot.) It looks to be fixed in sssd 2.3.0: https://github.com/SSSD/sssd/commit/bc56b10aea999284458dcc293b54cf65288e325d I'm cloning this bug: - on the samba side I'll add a breaks: sssd-ad-common (<< 2.3.0) - on the sssd side, an update to 2.3.0+ is needed Regards -- Mathieu Parent