Bug#821043: wesnoth-1.13-core: fails to upgrade: update-alternatives: error: alternative link /usr/share/man/de/man6/wesnoth.6.gz is already managed by wesnoth.de.6.gz (slave of wesnoth)

[Vincent Cheng]

Control: tag -1 + moreinfo unreproducible

On Thu, Apr 14, 2016 at 3:10 PM, Axel Beckert <abe at debian.org> wrote:
> Package: wesnoth-1.13-core
> Version: 1:1.13.4-1
> Severity: serious
>
> Hi,
>
> trying to upgrade wesnoth-1.13-core from 1:1.13.2-1 to 1:1.13.4-1 fails
> as follows:
>
> Setting up wesnoth-1.13-core (1:1.13.4-1) ...
> update-alternatives: error: alternative link /usr/share/man/de/man6/wesnoth.6.gz is already managed by wesnoth.de.6.gz (slave of wesnoth)
> dpkg: error processing package wesnoth-1.13-core (--configure):
>  subprocess installed post-installation script returned error exit status 2
> Errors were encountered while processing:
>  wesnoth-1.13-core
>
> Accordingly all packages depending on wesnoth-1.13-core fail as well.
>
> Please note that wesnoth-1.12 is also installed. Current state of all
> wesnoth-related packages on this system:

I can't reproduce this error at all. I had no issues upgrading from
wesnoth-1.13 1.13.2-1 to 1.13.4-1 on my own system, with wesnoth-1.12
installed at the same time. I also can't reproduce this in a clean
pbuilder chroot, i.e.:

# pbuilder --create --distribution sid --mirror http://ftp.ca.debian.org/debian
# pbuilder login
# apt-get install wesnoth-1.12
# echo "deb http://snapshot.debian.org/archive/debian/20160331T221016Z/
experimental main" > /etc/apt/sources.list.d/exp.list
# apt-get -o Acquire::Check-Valid-Until=false update
# apt-get install wesnoth-1.13 # installs 1.13.2-1 from snapshot.d.o
# echo "deb http://ftp.ca.debian.org/debian experimental main" >
/etc/apt/sources.list.d/exp.list
# apt-get update
# apt-get dist-upgrade # installs 1.13.4-1 successfully

And piuparts doesn't report any installation errors either [1],
although I suppose the piuparts.d.o reports don't mean much since it's
just testing clean installs of 1.13.4-1, not upgrades from 1.13.2-1 to
1.13.4-1.

I didn't change anything in any of the maintscripts when I updated the
packaging for wesnoth-1.13 1.13.4-1, so I'm frankly stumped as to why
you're seeing this error. Rhonda, any ideas?

Regards,
Vincent

[1] https://piuparts.debian.org/experimental/maintainer/v/vcheng@debian.org.html#wesnoth-1.13