Hi! Sorry for the delay. On Monday, 9 October 2023 13:08:24 CEST Santiago Vila wrote: > > Isn't that the whole point of line 76? > > Ok, yes. Sorry, I did not express it correctly. I meant that base-files > is not responsible for ensuring that /run/lock exists "at all times". > > As you rightly point out, there is indeed an attempt to ensure > that those directories exist after the very first install by debootstrap, > and this is done before /run becomes a ramdisk and before the first > reboot. I guess this is precisely your case.
Yep. > What I would like to know is exactly what changed *elsewhere* so that > this code, which apparently used to work before, is not working anymore. > > So: What is the parent directory which does not exist? It's /run ? Yes. /run is missing, therefor the creation of /run/lock fails > This directory belongs to base-files (try dpkg -L base-files). > > Should it not be created by debootstrap when unpacking base-files? I assume it's running the postinst script of base-files, which tries to create /run/lock, but fails as /run doesn't exist. Whether deboostrap or another package should be responsible for creating /run, I do not know. I think base-files is a good candidate as it already creates many top-level dirs and it also tries to create /run/lock. > BTW: I have not upgraded to trixie myself yet in my Desktop computer, > but I can use a virtual machine to test. Could you please explain exactly > how to reproduce the error? No need to post your script, only a *minimal* > case that shows the error. - 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]` See the error msg as reported in OP. Note that this image is *very* minimal to show the issue; it won't boot as it's missing all the important packages (kernel/initramfs/init/etc) *) This is similar to what I'm using, but stripped of most things which weren't relevant. I'm actually using arm64 as architecture, but I changed that to amd64 assuming that would be (even) easier. Cheers, Diederik
run-lock-issue.tar.xz
Description: application/xz-compressed-tar
signature.asc
Description: This is a digitally signed message part.
