The issue here is that packages built against samba-libs get a
dependency on samba-libs >= version, and they really either need a
dependency on samba-libs == version or the samba-libs package needs to
be versioned (e.g., samba-libs2, samba-libs3, etc.) and conflict with
other versions, or samba-libs needs to Breaks: every dependent package
on every update, or somesuch. The current state of affairs results in
every change to the samba-libs libraries breaks other packages compiled
against them (namely sssd) until those packages are recompiled, but
there is nothing in the dependencies to enforce that.
- Bug#1013259: samba-libs: Possible policy violation Michael Stone
- Bug#1013259: samba-libs: Possible policy violation Michael Tokarev
- Bug#1013259: samba-libs: Possible policy violat... Michael Stone
- Bug#1013259: samba-libs: Possible policy vi... Michael Tokarev
- Bug#1013259: [Pkg-samba-maint] Bug#1013... Michael Tokarev
- Bug#1013259: samba-libs: Possible polic... Michael Tokarev
- Bug#1013259: samba-libs: Possible ... Ralph Boehme
- Bug#1013259: samba-libs: Possi... Michael Tokarev
- Bug#1013259: samba-libs: P... Andreas Schneider
- Bug#1013259: samba-libs: P... Andreas Schneider
- Bug#1013259: samba-libs: Possible polic... Michael Stone