Control: tags -1 
thanks

On Wed, Mar 05, 2025 at 07:33:08AM +0100, John Paul Adrian Glaubitz wrote:
> It seems though that adduser has been released with this fix but I'm still
> seeing this issue. I may have to regenerate all chroots.

adduser 3.144 is the current version that has all fixes that we
currently have. Can you probably give a reproducer? Do the chroots
contain private data or is it possible to see such a chroot? Or can you
manually execute the adduser call from dbus with --stdoutmsglevel=trace?

I would be very interested in writing a test case avoiding this in the
future, but I need to know what's special in those chroots.

I tried upgrading systemd-nspawn containers (with dbus-system-bus-common
installed manually) from last week's sid to current sid, and from trixie
to sid without problems. Upgrades from bookworm to sid fail because we
had too overzealous dependencies on perl versions, that should not apply
when upgrading inside unstable, and is fixed in git.

I am available on IRC if that helps.

Greetings
Marc

Reply via email to