Your message dated Sat, 03 Jun 2023 00:50:40 +0200
with message-id <45563422.fMDQidcC6G@bagend>
and subject line close
has caused the Debian Bug report #1023321,
regarding vmdb2: Seems to require 'mount-on' parameter for mounting root
filesystem
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.)
--
1023321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023321
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vmdb2
Version: 0.26-2
Severity: important
Tags: upstream
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
In https://salsa.debian.org/raspi-team/image-specs/-/merge_requests/61
I am/was trying to fix an ambiguity issue I had by replacing tag values
which look like filesystem paths with 'tag-X'.
For mounting 'tag-root' I explicitly added ``dirname: '/'``.
Old:
```
- mount: /
```
New:
```
- mount: tag-root
dirname: '/'
```
I did NOT set the 'mount-on' parameter as there was not an already
mounted filesystem.
But trying to build an image resulted in the following error:
```
remembering /dev/mapper/loop0p1 as tag-firmware
remembering /dev/mapper/loop0p2 as tag-root
Exec: ['/sbin/mkfs', '-t', 'vfat', '-n', 'RASPIFIRM', '/dev/mapper/loop0p1']
Exec: ['blkid', '-c/dev/null', '-ovalue', '-sUUID', '/dev/mapper/loop0p1']
Exec: ['/sbin/mkfs', '-t', 'ext4', '-L', 'RASPIROOT', '/dev/mapper/loop0p2']
Exec: ['blkid', '-c/dev/null', '-ovalue', '-sUUID', '/dev/mapper/loop0p2']
ERROR: no mount-on tag given
ERROR: Exception('no mount-on tag given')
Something went wrong, cleaning up!
```
The [documentation](https://vmdb2-manual.liw.fi/#step-mount) already has
``FIXME: this may be wrong?`` and that statement seems to be correct.
- -- 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/XblvOeH7bbgUCY2JI3AAKCRDXblvOeH7b
bt2HAP9m9MT+8dnx6kw5k1e4I9b/mPoRT5OWOPZT0ACQh+gMGQEA5LAyv78YMj1x
Mkd9wkFPf2CLwrCnRO3w0PTGd9Lc+gE=
=Aspx
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
