Guillem Jover writes:
> A deconfigure happens for three reasons, Configure + Depends (other
> package removal), Breaks and M-A:same instances syncing.
> That's the only problematic and tricky maintainer script case I see,
> because due to the way dpkg and apt (or other frontends) interact,
> dec
On Sun, 2012-09-23 at 10:03:29 -0700, Russ Allbery wrote:
> In prerm:
>
> if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ] ; then
> update-alternatives --remove tf /usr/bin/tf5
> fi
>
> is correct I think. The possible invocations of prerm are:
>
> prerm remove
> old-prerm upgrade new-ver
Jakub Wilk writes:
> I don't think we should be filing bugs before there's consensus _how_
> exactly to fix them.
In prerm:
if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ] ; then
update-alternatives --remove tf /usr/bin/tf5
fi
is correct I think. The possible invocations of prerm are:
* Bill Allombert , 2012-09-20, 18:50:
I've just tested 665 packages that use update-alternatives.
122 of them removed an alternative on upgrade.
Could you report bugs ?
I don't think we should be filing bugs before there's consensus _how_
exactly to fix them.
But I'll post list of affected
4 matches
Mail list logo
