Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-16 Thread Steve Langasek
Thanks for this patch. Based on the rest of the discussion I don't believe this is something we need in Debian. Do you want to propose this to upstream? On Thu, Feb 08, 2024 at 08:27:00AM +0300, Michael Tokarev wrote: > Attached is a sketch to make pam compatible. > I had a more complete and *t

Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-14 Thread Steve Langasek
On Wed, Feb 07, 2024 at 09:06:58AM +0100, Helmut Grohne wrote: > On Wed, Feb 07, 2024 at 04:32:45AM +0100, Guillem Jover wrote: > > Yes, I'm not sure I understand either. This is what symbol versioning > > makes possible, even providing different variants for the same symbol, > > see for example gl

Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-08 Thread Sam Hartman
> "Helmut" == Helmut Grohne writes: Helmut> pam seems difficult: | extern time_t Helmut> pam_misc_conv_warn_time; /* time that we should warn user */ Helmut> | extern time_t pam_misc_conv_die_time; /* cut-off time for Helmut> input */ Helmut> We cannot symbol-version thes

Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-07 Thread Michael Tokarev
07.02.2024 11:06, Helmut Grohne : .. pam seems difficult: | extern time_t pam_misc_conv_warn_time; /* time that we should warn user */ | extern time_t pam_misc_conv_die_time; /* cut-off time for input */ Attached is a sketch to make pam compatible. I had a more complete and *tested* fi

Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-07 Thread Helmut Grohne
Hi Andreas, On Wed, Feb 07, 2024 at 03:47:37PM +0100, Andreas Metzler wrote: > Package: libselinux1t64 > Replaces: libselinux1 > Provides: libselinux1 (= 3.5-2.1~exp1) > Breaks: libselinux1 (<< 3.5-2.1~exp1) > > Afaiui libselinux1t64 must not fullfill dpkg 1.22.4's dependency on > "libselinux1 (>

Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-07 Thread Andreas Metzler
On 2024-02-06 Helmut Grohne wrote: > Package: libselinux1t64 [...]> This looks fairly innocuous. We create a minimal sid chroot and install > libselinux1t64 using apt. What could possibly go wrong? Well, apt thinks > that it would be a good idea to avoid coinstalling breaking packages and > first

Re: Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-07 Thread Helmut Grohne
Hi Guillem, On Wed, Feb 07, 2024 at 04:32:45AM +0100, Guillem Jover wrote: > Yes, I'm not sure I understand either. This is what symbol versioning > makes possible, even providing different variants for the same symbol, > see for example glibc or libbsd. I think symbol versioning is subtly differ

Bug#1063329: libselinux1t64: breaks system in upgrade from unstable

2024-02-06 Thread Helmut Grohne
Package: libselinux1t64 Version: 3.5-2.1~exp1 Severity: grave X-Debbugs-Cc: vor...@debian.org, debian-devel@lists.debian.org Hi, I was looking into performing an upgrade test of libselinux1 with piuparts and that didn't go well. I spare you the piuparts stuff and go into crafting a minimal reprod