Niko Tyni a écrit :
On Tue, Sep 16, 2008 at 11:11:50PM +0200, Julien PUYDT wrote:
Niko Tyni a écrit :
On Tue, Sep 16, 2008 at 08:36:17AM +0200, Julien PUYDT wrote:
Package: perl-doc
Version: 5.10.0-14

Unpacking perl-doc (from .../perl-doc_5.10.0-14_all.deb) ...
Adding `diversion of /usr/bin/perldoc to /usr/bin/perldoc.stub by perl-doc'
dpkg-divert: rename involves overwriting `/usr/bin/perldoc.stub' with
  different file `/usr/bin/perldoc', not allowed
dpkg: error processing /var/cache/apt/archives/perl-doc_5.10.0-14_all.deb (--unpack):
 subprocess pre-installation script returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/perl-doc_5.10.0-14_all.deb

$ ls -l /usr/bin/perldoc*
-rwxr-xr-x 1 root root 125 sep 12 21:07 /usr/bin/perldoc
-rwxr-xr-x 1 root root 125 sep 16 23:01 /usr/bin/perldoc.stub

$ /usr/sbin/dpkg-divert --list /usr/bin/perldoc
(nothing)

That's broken. I take it you don't have perl-doc currently installed?
You shouldn't have perldoc.stub at all at that point.

It wasn't installed, the dist-upgrade brought it in.

Do you get the same error if you try to install perl-doc now?

Yes, it was giving the same error.

What if you manually remove /usr/bin/perldoc.stub and then install
perl-doc ?

Then it works.

Again, which architecture is this? (Please consider using reportbug
in the future for bug reporting, it includes this and much other
possibly relevant information by default.)

It's i386 -- not sure it matters.

It was a dist-upgrade.

From which version?

From unstable to unstable.

Since that seemed so strange, I did just "rm /usr/bin/perldoc.stub", then retried to dist-upgrade : it worked :-/

I mentioned perl-base because it had a problem installing too (which got fixed with dpkg --pending --configure if I remember well). Could it be that a bad interaction triggered the problem?

Hard to say, can you recall any more details?

Unfortunately no :-(

Snark on freenode&gimpnet



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to