On Mon, Feb 09, 2015 at 11:55:58PM +0100, Philipp Kern wrote:
> On Sat, Jan 31, 2015 at 11:15:22PM +0100, Goswin von Brederlow wrote:
> > Updating gobby from 0.4.13-1 to 0.5.0-4 fails with:
> >
> > Preparing to unpack .../gobby_0.5.0-4_amd64.deb ...
> > update-alternatives: error: no alternatives for gobby
> > dpkg: error processing archive
> > /var/cache/apt/archives/gobby_0.5.0-4_amd64.deb (--unpack):
> > subprocess new pre-installation script returned error exit status 2
>
> Did this legitimally happen upon upgrade? Because I would've expected
> gobby-0.4 and gobby-0.5 to have been around. (Of course one can force
> this to appear using dpkg -i and not satisfying dependencies, just
> wondering if that happened here.)
>
> I'll fix it anyhow, just trying to figure out if that needs to go into
> jessie.
>
> Kind regards and thanks for the report
> Philipp Kern
It was a normal update of a seldomly used (and therefore sparingly
updated) laptop running sid.
As a side node the old, unconditional removal of the alternatives
violates the idempotency of the script. The installation can fail,
which I think happened in my case due to other packages failing, or be
aborted after the preinst has run. Then when the installation is tried
again removing the alternative fails because it is already gone.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
