On Sunday, 8 October 2023 19:40:43 CEST Santiago Vila wrote: > > So `/var/lock` points to `/run/lock` ... which doesn't exist. > > And that results in errors and a warning from aptitude with potentially > > some serious consequences. > > Thanks for the report. I think this has never happened until now.
When I put "Could not open lock file /var/lock/aptitude" into a search engine, the first result was https://askubuntu.com/a/120757 from 2012-04-10 And the presented solution was "sudo mkdir /run/lock". So it seems to me that nobody (apparently) never reported it before, but it isn't a new problem by any means. It could be that 'aptitude' is important to reveal the issue. It's also possible that another program which normally gets installed, would create that directory. I had not (yet) installed packages of priority important or normal when the issue occurred. > If yes, I believe that we should reassign this report to debootstrap. I did initially wonder to which package to file the bug against as next to debootstrap I also considered to file it against aptitude. But as the base-files package creates the symlink, I think it's therefor also its responsibility to make sure it points to an existing directory. Cheers, Diederik
signature.asc
Description: This is a digitally signed message part.
