On Tue, Aug 13, 2019 at 07:58:09PM +0100, Mark Hindley wrote:
> Thorsten,
>
> Thanks for this.
>
> On Tue, Aug 13, 2019 at 04:46:32PM +0200, Thorsten Glaser wrote:
> > On Sun, 11 Aug 2019, Simon McVittie wrote:
> >
> > > Found while preparing a test VM to test #923240. Please raise this to
> > > RC severity if you think it is justified - I don't want to create the
> >
> > I don’t think it’s RC in any of the involved packages (elogind,
> > systemd (shock!), apt) because it’s really a whole-system / package
> > management issue.
>
> Yes, that is my conclusion after 2 days of trying different things. Certainly
> systemd's prerm failure is pretty brutal. But this happens before any of the
> src:elogind preinsts run, so I can't see a way around it. If anything, it is a
> limitation in apt (although I am not trying to pass the buck here).
I have managed to work around this today. It requires circumventing the systemd
prerm failure. I am not recommending that as a final solution, but maybe we can
have another go at asking the systemd maintainers to review it?
What works for me on a sid VM:
1) rmdir /run/systemd/system
This is the directory that the systemd prerm checks for.
2) apt install libpam-elogind systemd-
3) Immediate reboot with shutdown -r -n
Although systemd as PID 1 no longer functions, all processes are sent
SIGTERM, filesystems are synced and unmounted.
I realise this is not graceful or elegant and I am unsure how safe it is.
Comments?
Perhaps we could ask that the systemd prerm no longer fails but instead prints a
message saying immediate reboot is required and how to achieve it?
Mark
