Bug#443334: policy: postinst abort-remove state.
Kurt Roeckx writes ("Bug#443334: policy: postinst abort-remove state."):
> I've been looking at what the different cases are when postinst is
> called. I think it makes most sense that after a succesful
> postinst it should be in installed state, even if it's an error unwind
> >from a different state.
I agree.
> It's not clearly documented in which states a package ends up after
> some failed maintainer scripts.
That's sometimes true, yes.
> I've also been looking at policy documents itself about postinst, for
> instancce it has:
> Your package should call `install-info' to update the Info `dir' file
> in its `postinst' script when called with a `configure' argument
> [...]
I agree that that seems like a mistake.
The system is designed so that most of the time you should _not check_
the $1 argument. Only in unusual situation should a maintainer script
have different behaviours depending on the situation.
> It seems to me like it shouldn't only call install-info in the
> postinst when called with configure. It seems alot of package get
> things like that wrong, including debhelper (#374467, #442079).
Oh dear.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
.
Reply to: