Comment 4 for bug 897880

So this happens when perl/perl-modules are unpacked, but not configured yet, and then some dpkg trigger pokes doc-base.

I tried various scenarios with having perl 5.14 unpacked but not configured, and then unpacking, triggering and/or installing doc-base and/or nano. I do get the symbol lookup error plenty of times, but always with

         *******************************************************************
         It seems install-docs is not fully functional at the moment,
         and it will try to recover from the error next time it is called.
         Please run `install-docs --install-changed' command
         manually after the upgrade process is finished.
         "*******************************************************************

and the exit code is 0.

But right now I can't make too much sense of the log anyway:

Processing triggers for doc-base ...
/usr/bin/perl: symbol lookup error: /usr/lib/perl5/auto/UUID/UUID.so: undefined symbol: Perl_xs_apiversion_bootcheck
dpkg: error processing doc-base (--unpack):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 doc-base

The context shows that at that time perl* are at 5.14/unpacked, but doc-base hasn't been touched anywhere yet. It never said "unpacking doc-base ..." for example, so the "dpkg: error processing doc-base (--unpack)" doesn't make sense, especially since unpack doesn't run postinst scripts.

Was this an upgrade from oneiric, or an intra-precise upgrade?