Package: vmdb2
Version: 0.26-2
Severity: minor
Tags: upstream
X-Debbugs-Cc: l...@liw.fi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

For the 'Raspberry Pi image specs' project, I made a MR to
switch from 'qemu-debootstrap' to 'debootstrap':
https://salsa.debian.org/raspi-team/image-specs/-/merge_requests/62

But just replacing 'qemu-debootstrap' with 'debootstrap' wasn't
sufficient and caused a build failure.
That surprised me as I _thought_ 'qemu-debootstrap' just called
debootstrap and we didn't get any failure then.
Trying to find the cause of this failure let me to inspect the source
and then I found 'require_empty_target', but found it was not documented
in the upstream manual: https://vmdb2-manual.liw.fi/#step-debootstrap

Hopefully this bug will remedy that.

Cheers,
  Diederik

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vmdb2 depends on:
ii  cmdtest         0.32.14.gcdfe14e-5
ii  debootstrap     1.0.128+nmu2
ii  e2fsprogs       1.46.6~rc1-1+b1
ii  kpartx          0.9.0-4+b1
ii  parted          3.5-2
ii  python3         3.10.6-1
ii  python3-jinja2  3.0.3-2
ii  python3-yaml    6.0-3
ii  qemu-utils      1:7.1+dfsg-2+b1

Versions of packages vmdb2 recommends:
ii  ansible           6.4.0+dfsg-1
ii  dosfstools        4.2-1
ii  qemu-user-static  1:7.1+dfsg-2+b1

vmdb2 suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCY2JriwAKCRDXblvOeH7b
bgG5AQCMe7BvfZyUpHs+ilC+aH3VWUiugKajQvUUXegkXwFxqQEA1HSaBML8c6bF
+yqI4Zd5kxyux4kscP6w4J/hsg4wOwA=
=stqp
-----END PGP SIGNATURE-----

Reply via email to