On Thu, 2024-02-29 at 13:31 -0700, Sam Hartman wrote:
> > > > >
> I tried to make the revert work either if you didn't have libpam0t64
> at
> all or if you did, but we're more focused on people who never
> upgraded.
>
> If you do run into breakage, we'll work with you to find a solution.
I
> "Christoph" == Christoph Anton Mitterer writes:
Christoph> Do you happen to know whether there's anything needed in
Christoph> terms of clean up for people who had already upgraded
Christoph> now? Like manually doing whatever was done via the
Christoph> runuser?
I think
On Thu, 2024-02-29 at 08:14 +0100, Helmut Grohne wrote:
> Can you locate a more complete upgrade log?
Attached is the excerpt from APT's term.log, if that helps.
Cheers,
Chris.
term.log.xz
Description: application/xz
On Thu, 2024-02-29 at 08:50 -0700, Sam Hartman wrote:
> > > > >
> Steve and I agreed to revert the rename on IRC, effectively
> accepting
> the ABI break because it doesn't matter for the archive.
> We may look at better solutions when we have a bit of time.
Do you happen to know whether
> "Helmut" == Helmut Grohne writes:
Helmut> I believe pam will have to be reverted and implemented as
Helmut> dual ABI instead.
I'm not very comfortable with this approach.
The tentative patch did not fill me with confidence; my gut is that it
was not as robust as an approach that
On Thu, Feb 29, 2024 at 08:14:30AM +0100, Helmut Grohne wrote:
> Ideally, we'd get a reproducer using
>
>mmdebstrap SOMERELEASE /dev/null --variant=apt --include=SOMEPACKAGES
> --customize-hook='echo SOURCES_LIST_LINE > "$1/etc/apt/sources.list"'
> --chrooted-customize-hook="apt-get update"
Processing control commands:
> severity -1 serious
Bug #1065017 [src:pam] runuser: error while loading shared libraries:
libpam.so.0
Severity set to 'serious' from 'normal'
--
1065017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065017
Debian Bug Tracking System
Contact
7 matches
Mail list logo
