pki-base postinst creates corrupt /etc/pki/pki.version

[Timo Aaltonen]

[Impact]

Upgrading pki-base from xenial to zesty fails, because /etc/pki/pki.versio created on xenial looks like this:

Configuration-Version: 10.2.6+git20160317

while it should just have 10.2.6. To fix the upgrade, the file should be recreated if old pki-base is older than 10.3.5-1.

[Test case]

Install pki-base on a xenial chroot, sed -i 's/xenial/zesty' /etc/apt/sources.list, apt dist-upgrade.
It should not fail.

[Regression potential]

Can't think of any.

[Brian Murray (brian-murray)]

Is this fixed in the development release of Ubuntu, Artful Aardvark?

[Timo Aaltonen (tjaalton)]

Now that 10.3.5+12-4 is synced, yes. But I heard about another upgrade bug which I'll check first, and reupload this along with other fixes if needed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dogtag-pki - 10.3.5+12-4

---------------
dogtag-pki (10.3.5+12-4) unstable; urgency=medium

  * pki-tomcatd.init: If no instance is configured, the initscript
    machinery would return error value 5 or 6. This messes up systemd, so
    just use 'exit 1' on every non-zero return value. (LP: #1664453)
  * pki-server.postinst: Clarify pki-tomcatd initial start failure
    message a bit.
  * Depend libresteasy-java << 3.1.0, because the new on doesn't work
    even after fixing the build.
  * pki-tools.links: Fix the convenience links DRMTool -> KRATool.
    (Closes: #857209)
  * pki-base.postinst: Force recreating pki.version if upgrading from
    older than 10.3.5-1. (LP: #1691655)

 -- Timo Aaltonen <email address hidden> Thu, 18 May 2017 09:10:17 +0300

[Timo Aaltonen (tjaalton)]

zesty is EOL