Olly Betts wrote:
> It looks like doc-base is confused from trying to process the two identical
> files when 1.2.15-4 was installed.
>
> I've discovered that running install-docs -R before upgrading ruby-xapian and
> install-docs -I afterwards makes things run smoothly, so perhaps I should
> automate that in the maintainer scripts if they detect an upgrade from a bad
> version and install-docs is installed. Then we can just reassign this bug to
> doc-base as it shouldn't really need manual intervention in this situation.
I found a slightly cleaner (though still nasty) workaround, now
implemented in xapian-bindings 1.2.17-1. The preinst overwrites one of
the duplicate doc-base files in /usr/share/doc-base with a dummy version
with a unique "Document:" field, and then calls install-docs -i with the
filenames of the two previously identical files in /usr/share/doc-base,
which is enough to get doc-base back into a sane state. To stop
install-docs being a no-op, it temporarily sets
DPKG_MAINTSCRIPT_PACKAGE=doc-base while running it (ick).
It would be much better if doc-base handled upgrading from this
situation cleanly - currently the user either needs to intervene (and
what to do isn't obvious) or packages need to add nasty workarounds to
make upgrades work.
It may seem dumb to have created this situation in the first place, but
if you don't have doc-base installed, you don't get any error or
warning, so it's easy for the maintainer to miss. In my case I had a
template foo.docbase.in file in the source package, which got installed
by dh_installdocs (because it matches debian/package.doc-base.*).
Cheers,
Olly
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
