On 09.07.2012 11:21, Teodor MICU wrote: > 2012/7/9 Tollef Fog Heen <[email protected]>: >> I think what might have happened is an aborted upgrade, which I don't >> think we currently handle correctly. I'll have to take a look at the >> code in question, though.
I think we handle the pam-auth-update bits as suggested by the pam documentation. We run pam-auth-update --package in postinst, at that point the package should be fully installed/unpacked. I'm still unsure about the sequence of events that happened that led to this situation. Especially in what state the libpam-systemd package was in. Or were you talking about the removal of the lsb hook diversion? > My guess is that this problem was caused by a deadlock in the upgrade. > The packages were upgraded and started to execute the post-install > configuration. But one of these packages (clamav-freshclam) has failed > to configure (due to missing init-functions script) and the process > was aborted, thus systemd packages didn't get configured either. > > To conclude, I see two problems to get fixed: > - make sure as early as possible on package install/upgrade that the > diversion is removed (probably pre-inst) > - make sure on package removal that the diversion is removed (probably > pre-rm). The /lib/lsb/init-scripts diversion is gone and has been replaced by the /lib/lsb/init-functions.d/40-systemd snippet. So all problems regarding diversions should be fixed. Unless there is a problem how we handle the removal of the old diversion in systemd.preinst? But this looks fine to me. That said, if there is a problem wrt /lib/lsb/init-functions, then this is a different issue, even if those two issues might be related. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
