Hi,

Quoting Benjamin Drung (2026-11-19 22:42:43)
> Package: mmdebstrap
> Version: 1.7.0-5
> Severity: normal
> Tags: ftbfs

I don't think this is the correct tag because this is not mmdebstrap failing to
build on Ubuntu but mmdebstrap not being able to create chroots for Ubuntu, no?

> X-Debbugs-Cc: [email protected], [email protected]
> User: [email protected]
> Usertags: amd64
> 
> Dear Maintainer,
> 
> mmdebstrap fails to build images for Ubuntu xenial:
> 
> ```
> $ mmdebstrap xenial xenial.tar http://archive.ubuntu.com/ubuntu
> I: automatically chosen mode: unshare
> I: chroot architecture amd64 is equal to the host's architecture
> I: finding correct signed-by value...
> done
> I: automatically chosen format: tar
> I: using /tmp/mmdebstrap.SPrWJ7eEHl as tempdir
> I: running apt-get update...
> done
> I: downloading packages with apt...
> done
> I: extracting archives...
> done
> I: installing essential packages...
> done
> [...]
> Setting up systemd (229-4ubuntu21.31) ...
> Created symlink /etc/systemd/system/getty.target.wants/[email protected], 
> pointing to /lib/systemd/system/[email protected].
> Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target, 
> pointing to /lib/systemd/system/remote-fs.target.
> Created symlink 
> /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service, pointing 
> to /lib/systemd/system/systemd-timesyncd.service.
> Initializing machine ID from random generator.
> Adding group `systemd-journal' (GID 101) ...
> Done.
> chfn: PAM: Critical error - immediate abort
> adduser: `/usr/bin/chfn -f systemd Time Synchronization systemd-timesync' 
> returned error code 1. Exiting.
> dpkg: error processing package systemd (--install):
>  subprocess installed post-installation script returned error exit status 1

Why do you suspect mmdebstrap to be the problem, given the above? Did you
investigate the reason for chfn exiting with a ciritical error related to pam?

It reminds me of a problem we used to have six years ago with mmdebstrap
running in "proot" mode (that mode no longer exists). Under proot, one would
get the following in the systemd postinst:

chfn: PAM: System error
adduser: `/usr/bin/chfn -f systemd Time Synchronization systemd-timesync' 
returned error code 1. Exiting.

And here is a similar error with fakechroot
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745082#75

And here is the issue with proot: https://github.com/proot-me/PRoot/issues/156

So in either case it wasn't mmdebstrap doing the wrong thing. Can you present
evidence that this is actually a bug in mmdebstrap?

> The systemd package calls:
> 
> adduser --quiet --system --group --no-create-home --home /run/systemd \
>     --gecos "systemd Time Synchronization" systemd-timesync
> 
> Then adduser calls /usr/bin/chfn from passwd.
> 
> I compared xenial with bionic: on xenial systemd is installed as part of
> the essential packages, but on bionic systemd is part of the remaining
> packages.

Still sounds like a bug in one of the involved packages to me and not like a
bug in mmdebstrap.

> mmdebstrap also fails to build images for Ubuntu trusty:
> 
> ```
> $ mmdebstrap trusty trusty.tar http://archive.ubuntu.com/ubuntu
> I: automatically chosen mode: unshare
> I: chroot architecture amd64 is equal to the host's architecture
> I: finding correct signed-by value...
> done
> I: automatically chosen format: tar
> I: using /tmp/mmdebstrap.w0v46VeV27 as tempdir
> I: running apt-get update...
> done
> I: downloading packages with apt...
> done
> I: extracting archives...
> done
> I: installing essential packages...
> done
> dpkg: error: failed to open package info file `/var/lib/dpkg/available' for 
> reading: No such file or directory

/var/lib/dpkg/available is no longer needed since dpkg 1.17.11, so mmdebstrap
stopped writing it. For creating chroots for older releases, have a look at the
jessie-or-older hooks shipped by mmdebstrap. Using these you can create chroots
for Debian unstable going as far back as 2006-08-04 using snapshot.debian.org.
That should be more than sufficient for Ubuntu, no?

> I know that these are old Ubuntu releases, but they still get paid
> support by Canonical. I like to use sbuild unshare to build package for
> these releases.

I'm not here to volunteer my freetime for Canonical. If somebody is paying
money for this, then they should pay a person to fix these things. I hope I was
able to give you sufficient feedback for such a thing to happen.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to