Your message dated Sat, 13 Apr 2024 14:19:52 +0200
with message-id <20240413141952.f4b35790d1f719e859ebe...@paranoici.org>
and subject line Re: Bug#1061816: mmdebstrap-autopkgtest-build-qemu VM image 
cannot be updated with sbuild-qemu-update
has caused the Debian Bug report #1061816,
regarding mmdebstrap-autopkgtest-build-qemu VM image cannot be updated with 
sbuild-qemu-update
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 ow...@bugs.debian.org
immediately.)


-- 
1061816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mmdebstrap
Version: 1.4.1-1
Severity: normal

Hello again Johannes!

As I said in bug report [#1061634], I've been able to create a QEMU/KVM
virtual machine image for autopkgtests:

  $ mkdir -p ~/var/cache/sbuild/
  $ cd /dev/shm
  $ TMPDIR=/dev/shm mmdebstrap-autopkgtest-build-qemu \
                    --size=25G --boot=efi sid sid-amd64.img
  $ chmod 660 sid-amd64.img
  $ mv -i sid-amd64.img ~/var/cache/sbuild/

[#1061634]: <https://bugs.debian.org/1061634>

It works for autopkgtests, but I wanted to use the same virtual machine
image to build Debian packages with sbuild-qemu.
The first thing I tested is the update of the VM image with
sbuild-qemu-update:

  $ sbuild-qemu-update --arch=amd64 sid-amd64.img
  qemu-system-x86_64 -enable-kvm -object 
rng-random,filename=/dev/urandom,id=rng0 -device 
virtio-rng-pci,rng=rng0,id=rng-device0 -device virtio-serial -nic 
user,model=virtio -m 1024 -smp 1 -nographic sid-amd64.img

This command does not seem to work: it uses 100 % of one CPU core and
seemingly does nothing, until I interrupt it by pressing [Ctrl+C].

Is there any special tweak or configuration needed to use
sbuild-qemu-update with mmdebstrap-autopkgtest-build-qemu VM images?
Where is this documented?

Otherwise, if this is an actual bug, please fix
mmdebstrap-autopkgtest-build-qemu
or help sbuild-qemu developers to fix sbuild-qemu-update.

Thanks for your time and dedication!



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages mmdebstrap depends on:
ii  apt      2.7.10
ii  perl     5.38.2-3
ii  python3  3.11.6-1

Versions of packages mmdebstrap recommends:
ii  arch-test            0.21-1
ii  fakechroot           2.20.1+ds-15
ii  fakeroot             1.33-1
ii  gpg                  2.2.40-1.1+b1
ii  libdistro-info-perl  1.7
ii  libdpkg-perl         1.22.2
ii  mount                2.39.3-6
ii  uidmap               1:4.13+dfsg1-3+b1

Versions of packages mmdebstrap suggests:
pn  apt-transport-tor  <none>
ii  apt-utils          2.7.10
ii  ca-certificates    20230311
ii  debootstrap        1.0.134
ii  distro-info-data   0.60
ii  dpkg-dev           1.22.2
pn  genext2fs          <none>
ii  perl-doc           5.38.2-3
pn  qemu-user          <none>
pn  qemu-user-static   <none>
pn  squashfs-tools-ng  <none>
ii  systemd            255.2-4

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: sbuild
Source-Version: 0.85.7


On Sat, 30 Mar 2024 00:28:55 +0100 Francesco Poli wrote:

> On Thu, 28 Mar 2024 10:05:53 +0100 Johannes Schauer Marin Rodrigues wrote:
> 
> [...]
> > Could you temporarily add a symlink from OVMF_CODE.fd to OVMF_CODE_4M.fd and
> > check if it still works?
> 
> Well, apparently it works:
[...]

And now , with sbuild-qemu/0.85.7, it works without the need to
manually add any symlink.
So I think this bug report may be closed: I am doing so with this
e-mail message.

Thanks for fixing the bug!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE

Attachment: pgpy8JMTwXQ5V.pgp
Description: PGP signature


--- End Message ---

Reply via email to