package doc-base 0.9.5ubuntu2 failed to install/upgrade: Byte order is not compatible at ../../lib/Storable.pm

[John Lenton]

Binary package hint: doc-base

Upgrading from natty to oneiric.

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: doc-base 0.9.5ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4
Uname: Linux 2.6.38-9-generic-pae i686
Architecture: i386
Date: Wed May 11 13:10:01 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1)
PackageArchitecture: all
SourcePackage: doc-base
Title: package doc-base 0.9.5ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
UpgradeStatus: Upgraded to oneiric on 2011-04-20 (21 days ago)

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

Here is the cause of the error:
Processing triggers for doc-base ...
Re-registation of all documents forced by /var/lib/doc-base/info/FORCE-REREGISTER.flag
De-registering 135, re-registering 135 doc-base files
Byte order is not compatible at ../../lib/Storable.pm (autosplit into ../../lib/auto/Storable/thaw.al) line 415, at /usr/share/perl5/MLDBM/Serializer/Storable.pm line 27
dpkg: error processing doc-base (--unpack):
 subprocess installed post-installation script returned error exit status 2

Setting to confirmed due to duplicates

[Jean-Baptiste Lallement (jibel)]

Raising to Critical. It is very common on i386 upgrades but not always reproducible.

[Michael Vogt (mvo)]

I can not reproduce this in a chroot, but I can in a full virtual machine. It turns out that doc-base does no longer use MLDBM but YAML::Tiny so once 0.10.0 is on disk it should work. But it looks this is triggered pretty early if it happens.

[Michael Vogt (mvo)]

When this happend on my box the old doc-base is still installed (0.9.5ubuntu2) and it was a trigger (probably by libxml-parser-perl).

[Michael Vogt (mvo)]

This seems to be entirely dependent on the unpack/configure ordering. I upload a new perl now that adds a break to the old doc-base that should ensure its upgraded in the right order.

[Michael Vogt (mvo)]

This is fixed for me now, the test upgrade machine I used that broke before is now happily running past the doc-base issue.