Ubuntu
libxml-sax-perl package

libxml-perl doesn't install during upgrade

Bug #471290 reported by josh803316 on 2009-11-02

This bug report is a duplicate of: Bug #13917: CPAN's XML::SAX update conflicts with libxml-sax-perl's XML::SAX. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	libxml-sax-perl (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: libxml-sax-perl

Ubuntu: 9.10 (during upgrade)

apt-cache policy libxml-sax-perl
libxml-sax-perl:
  Installed: 0.96+dfsg-1
  Candidate: 0.96+dfsg-1
  Version table:
*** 0.96+dfsg-1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

I expected the upgrade to upgrade this package, but I got an error saying that it didn't work

ProblemType: Package
Architecture: amd64
Date: Mon Nov 2 08:21:49 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 1
Package: libxml-sax-perl 0.96+dfsg-1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: libxml-sax-perl
Title: package libxml-sax-perl 0.96+dfsg-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-14-generic x86_64

Tags:

Revision history for this message

josh803316 (josh803316-yahoo) wrote on 2009-11-02:

AptOrdering.txt Edit (404 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (724 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (48.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (3.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2009-12-05:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 13917, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.