[Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal

[Łukasz Zemczak]

Thanks for all the testing Brian! As with any python3 upload, this also
seems to come with quite a lot reported autopkgtest regressions. Could
you take a look at those and see if they're related to the changes or
not (both bionic and artful)?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python3-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1768379

Title:
  python3-minimal should predepend on versioned version of
  python3-minimal

Status in python3-defaults package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in python3-defaults source package in Artful:
  Fix Committed
Status in ubuntu-release-upgrader source package in Artful:
  Invalid
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in python3-defaults package in Debian:
  Fix Released

Bug description:
  [Impact]
  Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found".

  [Test Case]
  1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt
  2) dpkg --unpack python3-minimal...
  3) dpkg --unpack python3-apt...

  Observe the following Traceback:

  Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ...
  /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found
  dpkg: warning: subprocess old pre-removal script returned error exit status 127
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
  dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack):
   subprocess new pre-removal script returned error exit status 127
  /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 127

  With the deb python3-minimal from -proposed you won't be able to
  unpack python3-minimal without first installing python3.6-minimal.
  While that may qualify as verification it'd still be good to test
  unpacking python3-apt. To do that you'll need to install
  python3.6-minimal from the target release by editing you
  /etc/apt/sources.list to the new release, running 'apt-get update',
  and then 'apt-get install python3.6-minimal'. After that's all done
  you can try steps 2 and 3 from the test case again and you should not
  receive a Traceback.

  [Regression Potential]
  Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done.

  
  [A Portion of the Original Description (it was a huge blob of failure)]
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install failure:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+subscriptions