On Tuesday, 1 November 2022 11:21:55 CET Michael Tokarev via samba-technical
wrote:
> 01.11.2022 13:14, Ralph Boehme wrote:
> > On 11/1/22 09:15, Michael Tokarev via samba-technical wrote:
> >> Control: tag -1 + upstream
> >>
> >> Original context was at http://bugs.debian.org/1013259 , but
On Tuesday, 1 November 2022 11:21:55 CET Michael Tokarev wrote:
> 01.11.2022 13:14, Ralph Boehme wrote:
> > On 11/1/22 09:15, Michael Tokarev via samba-technical wrote:
> >> Control: tag -1 + upstream
> >>
> >> Original context was at http://bugs.debian.org/1013259 , but whole
> >> thing *now*
Hmm. Other sssd packages are also affected by this.
Not only sssd-ad but sssd-ipa and sssd-ad-common.
Added the Breaks for these in Bullseye (and also in Ubuntu Jammy, which
has exactly the same problem). Will be in the next upload.
/mjt
On Tue, Nov 01, 2022 at 10:59:11AM +0300, Michael Tokarev wrote:
And this revealed one more issue here, now with samba 4.17. Where, the
same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3!
And it looks like *this* is what you're talking about now, once 4.17 with
this new
On 11/1/22 09:15, Michael Tokarev via samba-technical wrote:
Control: tag -1 + upstream
Original context was at http://bugs.debian.org/1013259 , but whole
thing *now* has is about completely unnecessary soname bump of libndr
in 4.17 due to debugging refinements.
to me this looks like a
01.11.2022 13:14, Ralph Boehme wrote:
On 11/1/22 09:15, Michael Tokarev via samba-technical wrote:
Control: tag -1 + upstream
Original context was at http://bugs.debian.org/1013259 , but whole
thing *now* has is about completely unnecessary soname bump of libndr
in 4.17 due to debugging
Control: tag -1 + upstream
Original context was at http://bugs.debian.org/1013259 , but whole thing *now*
has is about completely unnecessary soname bump of libndr in 4.17 due to
debugging
refinements.
01.11.2022 11:07, Michael Tokarev wrote:
01.11.2022 10:59, Michael Tokarev wrote:
..
And
01.11.2022 10:59, Michael Tokarev wrote:
..
And this revealed one more issue here, now with samba 4.17. Where, the
same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3!
And it looks like *this* is what you're talking about now, once 4.17 with
this new libndr.so.3 hits
31.10.2022 19:14, Michael Stone wrote:
If you can come up with a better solution than a strict dependency, great. But
the current situation, in which samba upgrades randomly render systems unusable
is, in my opinion, much much much worse than an overly strict dependency.
Fundamentally the
If you can come up with a better solution than a strict dependency, great. But
the current situation, in which samba upgrades randomly render systems unusable
is, in my opinion, much much much worse than an overly strict dependency.
Fundamentally the problem is that you're promising future
31.10.2022 18:15, Michael Stone wrote:
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
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
On Mon, 2022-06-20 at 10:39 +0200, Hannes Eberhardt wrote:
> Package: samba-libs
> Version: 2:4.16.1+dfsg-8~bpo11+1
> Severity: normal
> X-Debbugs-Cc: hannes.eberha...@neumannmueller.com
>
> Dear Maintainer,
>
> I noticed that sssd service of a freeipa-client installation broke
> with the
Package: samba-libs
Version: 2:4.16.1+dfsg-8~bpo11+1
Severity: normal
X-Debbugs-Cc: hannes.eberha...@neumannmueller.com
Dear Maintainer,
I noticed that sssd service of a freeipa-client installation broke with the
following error message because of missing library.
sssd[651553]:
14 matches
Mail list logo
