doc-base post-installation script breaks do-release-upgrade from 16.04 to 18.04

[Rene Schickbauer]

On one of my computers, do-release-upgrade from 16.04 LTS to 18.04 LTS broke mid-update.

Logfile seems to indicate that the "doc-base" package is to blame:

2018-08-16 14:02:43,476 INFO cache.commit()
2018-08-16 14:02:43,476 DEBUG failed to SystemUnLock() (E:Not locked)
2018-08-16 14:12:31,145 ERROR got an error from dpkg for pkg: 'doc-base': 'installed doc-base package post-installation script subprocess returned error exit status 10'
2018-08-16 14:12:31,146 DEBUG running apport_pkgfailure() doc-base: installed doc-base package post-installation script subprocess returned error exit status 10
2018-08-16 14:12:32,550 ERROR Exception during pm.DoInstall()
Traceback (most recent call last):
  File "/tmp/ubuntu-release-upgrader-7ytclj_8/DistUpgrade/DistUpgradeView.py", line 220, in run
    res = pm.do_install(self.writefd)
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
2018-08-16 14:12:32,580 ERROR SystemError from cache.commit(): installArchives() failed
2018-08-16 14:12:32,581 ERROR found exception: 'E:Sub-process /usr/bin/dpkg returned an error code (1)'
2018-08-16 14:12:51,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=639239a3-685e-4265-abf9-da9db3964d42
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f184485-213c-4467-b6d1-3bf9fa0c69c8 ro
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic N/A
 linux-firmware 1.173.1
RfKill:

Tags: bionic
Uname: Linux 4.15.0-32-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-08-16 (0 days ago)
UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers wireshark
_MarkForUpload: True
dmi.bios.date: 02/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.70
dmi.board.name: X79 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd02/13/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX79Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1787411

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

apport information

[Rene Schickbauer (rene-schickbauer)]

Yes, i had to fiddle around quite a lot with the package manager to get everything going again and it all works now (the apport information above is from after the upgrade).

That doesn't change the fact that a do-release-upgrade shouldn't just fail in the middle and give up. In my opinion, it should try to upgrade/install as much as possible and then print the couple of missing/broken packages at the end.

At the very least, do-release-upgrade shouldn't just die without giving the user at least some basic information of what to try next.