Your message dated Tue, 5 May 2026 13:53:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#1135732: debvm: systemd is still included when run
with --init-system=none
has caused the Debian Bug report #1135732,
regarding debvm: systemd is still included when run with --init-system=none
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1135732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135732
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debvm
Version: 0.5.2
Severity: normal
X-Debbugs-Cc: [email protected]
Usertags: minidebconf-hamburg-2026
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
running debvm-create --init-system=none -- --include=openrc gets me:
[...]
Add existing services ...
* service savecache added to runlevel off
* service cgroups added to runlevel sysinit
* Caching service dependencies ... [ ok ]
**********************************************************************
*** WARNING: if you are replacing sysv-rc by OpenRC, then you must ***
*** reboot immediately using the following command: ***
for file in /etc/rc0.d/K*; do s=`basename $(readlink "$file")` ; /etc/init.d/$s
stop; done
**********************************************************************
Setting up liblz4-1:amd64 (1.10.0-10) ...
Setting up libapt-pkg7.0:amd64 (3.3.0) ...
Setting up apt (3.3.0) ...
Processing triggers for libc-bin (2.42-15) ...
I: running --customize-hook directly:
/usr/bin/../share/debvm/customize-dpkgavailable.sh /tmp/mmdebstrap.M2QtTkNV7F
Replacing available packages information from <standard input>.
Information about 74318 packages was updated.
I: running --customize-hook in shell: sh -c 'echo 'testvm' >"$1/etc/hostname"'
exec /tmp/mmdebstrap.M2QtTkNV7F
I: running --customize-hook in shell: sh -c 'printf '127.0.0.1
localhost\n127.0.1.1 %s\n::1 ip6-localhost ip6-loopback\n' 'testvm'
>"$1/etc/hosts"' exec /tmp/mmdebstrap.M2QtTkNV7F
I: running --customize-hook in shell: sh -c 'echo "LABEL=debvm / ext4 defaults
0 0" >"$1/etc/fstab"' exec /tmp/mmdebstrap.M2QtTkNV7F
I: running --customize-hook directly:
/usr/bin/../share/debvm/customize-kernel.sh /tmp/mmdebstrap.M2QtTkNV7F
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Solving dependencies... Done
The following NEW packages will be installed:
3cpio dracut-install initramfs-tools initramfs-tools-bin initramfs-tools-core
klibc-utils kmod libklibc libkmod2 libsystemd-shared linux-base
linux-base-7.0.3+deb14-cloud-amd64 linux-base-cloud-amd64
linux-binary-7.0.3+deb14-cloud-amd64 linux-image-7.0.3+deb14-cloud-amd64
linux-image-cloud-amd64 linux-modules-7.0.3+deb14-cloud-amd64 logsave mount
systemd udev
[...]
So openrc gets installed, but systemd gets installed *after* that, which
is not what should happen. I suspect something Depends:/Recommends: on
systemd and that pull it in then.
best,
werdahias
- -- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.18-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled
Versions of packages debvm depends on:
ii dash 0.5.12-12
ii dpkg-dev 1.23.7
ii e2fsprogs 1.47.4-1
ii ipxe-qemu 2.0.0+dfsg- de5
ii libarchive13t64 3.8.7-1
ii mmdebstrap 1.5.7-3
ii qemu-system-arm [qemu-system-any] 1:11.0.0+ds-1
ii qemu-system-mips [qemu-system-any] 1:11.0.0+ds-1
ii qemu-system-misc [qemu-system-any] 1:11.0.0+ds-1
ii qemu-system-ppc [qemu-system-any] 1:11.0.0+ds-1
ii qemu-system-riscv [qemu-system-any] 1:11.0.0+ds-1
ii qemu-system-s390x [qemu-system-any] 1:11.0.0+ds-1
ii qemu-system-sparc [qemu-system-any] 1:11.0.0+ds-1
ii qemu-system-x86 [qemu-system-native] 1:11.0.0+ds-1
Versions of packages debvm recommends:
ii arch-test 0.22-1.1
ii binfmt-support 2.2.2-8
ii dosfstools 4.2-1.2
ii fdisk 2.42-5
ii file 1:5.46-5+b2
ii mount 2.42-5
ii mtools 4.0.49-1
ii openssh-client 1:10.3p1-2
ii ovmf 2025.11-5
ii qemu-system 1:11.0.0+ds-1
ii qemu-user-binfmt [qemu-user-static] 1:11.0.0+ds-1
ii seabios 1.17.0-1
ii systemd-ukify 260.1-1
ii uidmap 1:4.19.3-2
Versions of packages debvm suggests:
pn ovmf-ia32 <none>
ii qemu-efi-aarch64 2025.11-5
pn qemu-efi-arm <none>
ii qemu-efi-riscv64 2025.11-5
ii qemu-system-gui 1:11.0.0+ds-1
pn systemd <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iIsEARYKADMWIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCafnGNRUcd2VyZGFoaWFz
QGRlYmlhbi5vcmcACgkQ7L7btge5sr6q4QEA9+wFs8tN9KggBl6erY0wg9gHECzp
5w3CP/ie6OsSm6gA/j0tjcNQltoUToxhPaUCdyi/MehCLyke6ZkEfXSnn/EO
=8M80
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi Matthias,
On Tue, May 05, 2026 at 12:28:10PM +0200, Matthias Geiger wrote:
> running debvm-create --init-system=none -- --include=openrc gets me:
>
> [...]
> Add existing services ...
> * service savecache added to runlevel off
> * service cgroups added to runlevel sysinit
> * Caching service dependencies ... [ ok ]
> **********************************************************************
> *** WARNING: if you are replacing sysv-rc by OpenRC, then you must ***
> *** reboot immediately using the following command: ***
> for file in /etc/rc0.d/K*; do s=`basename $(readlink "$file")` ;
> /etc/init.d/$s stop; done
> **********************************************************************
> Setting up liblz4-1:amd64 (1.10.0-10) ...
> Setting up libapt-pkg7.0:amd64 (3.3.0) ...
> Setting up apt (3.3.0) ...
> Processing triggers for libc-bin (2.42-15) ...
> I: running --customize-hook directly:
> /usr/bin/../share/debvm/customize-dpkgavailable.sh /tmp/mmdebstrap.M2QtTkNV7F
> Replacing available packages information from <standard input>.
> Information about 74318 packages was updated.
> I: running --customize-hook in shell: sh -c 'echo 'testvm'
> >"$1/etc/hostname"' exec /tmp/mmdebstrap.M2QtTkNV7F
> I: running --customize-hook in shell: sh -c 'printf '127.0.0.1
> localhost\n127.0.1.1 %s\n::1 ip6-localhost ip6-loopback\n' 'testvm'
> >"$1/etc/hosts"' exec /tmp/mmdebstrap.M2QtTkNV7F
> I: running --customize-hook in shell: sh -c 'echo "LABEL=debvm / ext4
> defaults 0 0" >"$1/etc/fstab"' exec /tmp/mmdebstrap.M2QtTkNV7F
> I: running --customize-hook directly:
> /usr/bin/../share/debvm/customize-kernel.sh /tmp/mmdebstrap.M2QtTkNV7F
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Solving dependencies... Done
> The following NEW packages will be installed:
> 3cpio dracut-install initramfs-tools initramfs-tools-bin
> initramfs-tools-core klibc-utils kmod libklibc libkmod2 libsystemd-shared
> linux-base linux-base-7.0.3+deb14-cloud-amd64 linux-base-cloud-amd64
> linux-binary-7.0.3+deb14-cloud-amd64 linux-image-7.0.3+deb14-cloud-amd64
> linux-image-cloud-amd64 linux-modules-7.0.3+deb14-cloud-amd64 logsave mount
> systemd udev
> [...]
> So openrc gets installed, but systemd gets installed *after* that, which
> is not what should happen. I suspect something Depends:/Recommends: on
> systemd and that pull it in then.
I argue that this is not-a-bug. Even if it were, it would not be one in
debvm.
udev depends on "systemd | systemd-standalone-sysusers |
systemd-sysusers". To me, this looks like the correct dependency for
getting a working systemd-sysusers implementation. apt chooses the
default implementation "systemd" as no other is already satisfied and
systemd happens to be easily satisfiable. You appear to want a
non-default implementation of systemd-sysusers. Please be explicit about
that in your invocation. For instance, you might choose
--include=opensysusers. Once doing so, systemd is no longer included in
your rootfs image.
Hence closing this bug
Helmut
--- End Message ---
