Package: mmdebstrap
Version: 1.4.1-1
Severity: normal

Hello Johannes!

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/

It is able to run autopkgtests:

  $ autopkgtest --output-dir     ./${SRCPKG}_autopkgtest.out \
                --summary        ./${SRCPKG}_autopkgtest.summary \
                --apt-upgrade -B ./${SRCPKG}_amd64.changes -- \
                qemu --boot=efi --overlay-dir /dev/shm \
                ~/var/cache/sbuild/sid-amd64.img

My comments / suggestions for improvements:

  * I had to manually fix the permissions, since the image file was
    originally created with the following weird ones:

      $ ls -l --si sid-amd64.img 
      -rw-r-xrwx 1 $USER $USER 27G Jan 27 17:48 sid-amd64.img

    I think the file permissions should be set (possibly at the end of the
    mmdebstrap-autopkgtest-build-qemu run) as they would "naturally"
    result from the user's umask:

      $ cd /dev/shm
      $ touch foo
      $ ls -l --si foo 
      -rw-rw---- 1 $USER $USER 0 Jan 27 19:00 foo

    That's why I manually changed the permissions at the end:

      $ chmod 660 sid-amd64.img
      $ ls -l --si sid_amd64.img
      -rw-rw---- 1 $USER $USER 27G Jan 27 17:48 sid-amd64.img

    I suggest that mmdebstrap-autopkgtest-build-qemu applies this fix
    automatically.

  * I was surprised to see a 25 GiB image fit into a 7.7 GiB filesystem:

      $ cd /dev/shm
      $ ls -l -h sid-amd64.img
      -rw-rw---- 1 $USER $USER 26G Jan 27 17:48 sid-amd64.img
      $ df -h .
      Filesystem      Size  Used Avail Use% Mounted on
      tmpfs           7.7G  765M  7.0G  10% /dev/shm

    Well, the mystery is solved by looking at the allocated size:

      $ ls -l -h -s sid-amd64.img 
      662M -rw-rw---- 1 $USER $USER 26G Jan 27 17:48 sid-amd64.img

    Would it be less confusing, if mmdebstrap-autopkgtest-build-qemu created
    .qcow2 images?

    
-- 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

Reply via email to