[pkg-go] Bug#1053677: base-files: /var/lock points to non-existing /run/lock

[Santiago Vila]

reassign 1053677 debos
thanks

El 11/10/23 a las 23:50, Diederik de Haas escribió:
> - install `debos` in a virtual machine
> - extract the attached archive*
> - do `cd run-lock-issue`
> - run `debos image.yml [2>&1 | tee -a build.log]`

Ok, I finally arrived at this point.

[ Note: I'm doing all this from a machine running bookworm ]

# debos image.yml
2023/10/15 20:55:56 error creating fakemachine: <nil>, kvm backend not supported: open /dev/kvm: no such file or directory, uml backend not supported: user-mode-linux not installed

[ I'm on a virtual machine, and having /dev/kvm available inside the virtual machine itself
is called "nested virtualization", and it's considered a "special feature", so I decided
to try the user-mode-linux route ].

After installing user-mode-linux:

2023/10/15 20:59:49 error creating fakemachine: <nil>, kvm backend not supported: open /dev/kvm: no such file or directory, uml backend not supported: libslirp-helper not installed
2023/10/15 20:59:49 fakemachine not supported, running on the host!

After installing libslirp-helper:

# debos image.yml
stat /lib/systemd/systemd-resolved: no such file or directory

After installing systemd-resolved:

# debos image.yml
Running /debos --artifactdir /root/run-lock-issue /root/run-lock-issue/image.yml --internal-image /dev/disk/by-fakemachine-label/fakedisk-0 using uml backend
2023/10/15 21:04:56 ==== image-partition ====
2023/10/15 21:04:57 Action `image-partition` failed at stage Run, error: exec: "parted": executable file not found in $PATH

After installing parted:

# debos image.yml

and then I finally can see what you reported:

2023/10/15 21:13:11 run-installer-script.sh | Reading package lists...
2023/10/15 21:13:13 run-installer-script.sh | Building dependency tree...
2023/10/15 21:13:13 run-installer-script.sh | Reading state information...
2023/10/15 21:13:14 run-installer-script.sh | E: Could not open lock file /var/lock/aptitude - open [...]

If I use deboostrap alone without debos, this is what happens:

# debootstrap trixie /tmp/trixie http://deb.debian.org/debian
[...]

# ls -l /tmp/trixie/run
total 24
-rw-r--r-- 1 root root    0 Oct 15 21:32 adduser
drwxrwxrwt 3 root root 4096 Oct 15 21:31 lock
drwxr-xr-x 2 root root 4096 Oct 15 21:31 log
drwxr-xr-x 2 root root 4096 Oct 15 21:30 mount
drwxr-xr-x 2 root root 4096 Oct 15 21:31 sendsigs.omit.d
lrwxrwxrwx 1 root root    8 Oct 15 21:31 shm -> /dev/shm
drwxr-xr-x 9 root root 4096 Oct 15 21:31 systemd
drwxr-xr-x 2 root root 4096 Oct 15 21:31 user

This seems a bug in debos to me. Hence I'm doing a reassign.

Thanks.