Hi,
I think this is the wrong approach. The postrm hook is called
twice, one for remove, and once for purge. The better option is to
detect when we are being called on purge, and take no action.
I do not like testing to see the initrd exists, since it assumes
much about the naming if the initrd, which might be different through
configuration.
So I thought about why is it important for us to abort whern
removing the metadata about initramfs fails? This is a convenience
function only, and arguably we can just ignore errors. So what about
update-initramfs ... || true
to just ignore the error?
manoj
--
Never call a man a fool; borrow from him.
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
