Lukas Ruf wrote:
> the problem still persists in 2.0.0-4:
>
> Setting up fp-compiler (2.0.0-4) ...
> update-alternatives: slave link name /usr/share/man/man1/pc.1.gz duplicated
I looked at reproducing this bug (not being the maintainer, merely working on
release critical bugs in general). I created four identical clean sid chroots
with
just the base system in them.
In the first chroot I installed fp-compiler 2.0.0-1 and upgraded that to 2.0.0-4
(the version currently in testing and unstable). This worked perfectly.
In the second chroot I installed fp-compiler 2.0.0-2 and upgraded that to
2.0.0-4.
This worked perfectly.
In the third chroot I installed fp-compiler 2.0.0-1, and upgraded that to
2.0.0-2.
This failed, as expected. I then removed the pc alternative
("update-alternatives
--remove pc /usr/bin/fpc"), installed 2.0.0-2 again, which now worked. The
upgrade
to 2.0.0-4 worked perfectly.
In the fourth chroot I installed fp-compiler 2.0.0-1, tried to upgrade to
2.0.0-2
(which failed) and then upgraded directly to 2.0.0-4, which worked perfectly.
I also tested the package with piuparts, both simple installation and removal,
and upgrades from sarge to etch and sid, and that worked perfectly.
Lukas, do you still have the problem? You reported the bug two months ago, so it
may be that your system has been fixed since. I suspect that you had trouble
because
of something you tried to do after installing the 2.0.0-1 or -2 versions and
that
that made things such that the problem still occurs with -4, but I couldn't find
a scenario where I could reproduce this. Any hints as to how to reproduce it
would
be most welcome.
I did not investigate how the fpc packages may interact with the gpc packages.
Lukas,
do you (or did you) have gpc packages also installed when the problem occurred?
If this bug can't be reproduced, I think it would be appropriate to at least
lower
the severity to normal, since the package does seem to be usable for most
people.
--
Good news at once. Bad news never in the evening or on Friday.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
