[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** No longer affects: ubuntu-release-upgrader (Ubuntu) ** No longer affects: ubuntu-release-upgrader (Ubuntu Artful) ** No longer affects: ubuntu-release-upgrader (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Released Status in python3-defaults source package in Artful: Fix Released Status in python3-defaults source package in Bionic: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Changed in: python3-defaults (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Released Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
This is in cosmic-proposed, but hasn't migrated to -updates yet. python3-defaults (3.6.6-1) unstable; urgency=medium [ Matthias Klose ] * Fix the idle desktop file. Closes: #901096. * Install the policy files in the python3 package. Closes: #901486. * python3-minimal: Pre-Depend on python3.6-minimal. Closes: #901001. * Bump version to 3.6.6. [ Scott Kitterman ] * Remove myself from uploaders -- Matthias Klose Wed, 27 Jun 2018 18:18:20 +0200 ** Changed in: python3-defaults (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Fix Committed Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Released Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
This bug was fixed in the package python3-defaults - 3.6.5-3ubuntu1 --- python3-defaults (3.6.5-3ubuntu1) bionic; urgency=medium * Switch python3.x-minimal to a pre-dependency for python3-minimal so that release upgrades will be more smooth. (LP: #1768379) -- Brian Murray Thu, 21 Jun 2018 14:52:37 -0700 ** Changed in: python3-defaults (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 Released Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
This bug was fixed in the package python3-defaults - 3.6.3-0ubuntu3 --- python3-defaults (3.6.3-0ubuntu3) artful; urgency=medium * Switch python3.x-minimal to a pre-dependency for python3-minimal so that release upgrades will be more smooth. (LP: #1768379) -- Brian Murray Thu, 21 Jun 2018 15:50:41 -0700 ** Changed in: python3-defaults (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
It's not clear to me what is going on in the ubuntu-make autopkgtest for artful/s390x but the failure isn't related to my SRU. From the log: Investigating (0) autopkgtest-satdep:s390x < 0 @iU mK Nb Ib > Broken autopkgtest-satdep:s390x Depends on ubuntu-desktop:s390x < none @un H > Removing autopkgtest-satdep:s390x because I can't find ubuntu-desktop:s390x Done There is no ubuntu-desktop for s390x in artful, so the failure makes sense. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
The following tests have a history of failures and shouldn't be considered regressions: xandikos [artful/ppc64el] it regularly has autopkgtest timeouts for all arches and release meson [artful/i386] sometimes passes but sometimes fails always in simdtest network-manager [artful/arm64] almost never passes pyfai [artful/all arches] fails more often than it passes on most arches unattended-upgrades [bionic/arm64] has failed repeatedly python-docker [artful/s390x] client timeout errors on everything but armhf firewall? translate-toolkit [artful/all arches] seems unrelated given that it fails on all arches and nothing has triggered translate-toolkit in 8 or 9 months so infrastructure? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
The following tests have a history of failures and shouldn't be considered regressions: dulwich [bionic/s390x] snapcraft [bionic/all arches] python-mechanicalsoup [bionic/all arches] These LinkNotFoundErrors also occurred in cosmic and when the bionic/s390x version was triggered by pytest-mock/1.7.1-1 so its not related to my SRU. netplan.io [bionic/all arches] test_eth_dhcp6_off seems flaky to me as its failed with other triggers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
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 Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
I performed the same upgrade of an Ubuntu 16.04 lxc container but to binoic w/ -proposed enabled (after hacking DistUpgradeController.py) and there were no issues. ** Tags removed: verification-needed-artful verification-needed-bionic ** Tags added: verification-done-artful verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
Brian, thanks so much for testing these cases -- it's certainly more work than the "usual" SRU case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
I also performed an upgrade of an Ubuntu 16.04 lxc container to artful w/ -proposed enabled without issue. ubuntu@artful-upgrade:~$ grep -C10 python3-minimal /var/log/dist-upgrade/apt-term.log Unpacking python3-cryptography (1.9-1) over (1.2.3-1ubuntu0.1) ... Processing triggers for systemd (234-2ubuntu12.4) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.26-0ubuntu2.1) ... Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu13.6) ... Setting up libpython3.6-minimal:amd64 (3.6.3-1ubuntu1) ... Setting up libexpat1:amd64 (2.2.3-1) ... Setting up python3.6-minimal (3.6.3-1ubuntu1) ... Processing triggers for libc-bin (2.26-0ubuntu2.1) ... (Reading database ... 26272 files and directories currently installed.) Preparing to unpack .../python3-minimal_3.6.3-0ubuntu3_amd64.deb ... Unpacking python3-minimal (3.6.3-0ubuntu3) over (3.5.1-3) ... Setting up python3-minimal (3.6.3-0ubuntu3) ... (Reading database ... 26272 files and directories currently installed.) Preparing to unpack .../python3_3.6.3-0ubuntu3_amd64.deb ... running python pre-rtupdate hooks for python3.6... Unpacking python3 (3.6.3-0ubuntu3) over (3.5.1-3) ... Preparing to unpack .../install-info_6.4.90.dfsg.1-1build1_amd64.deb ... Unpacking install-info (6.4.90.dfsg.1-1build1) over (6.1.0.dfsg.1-5) ... Setting up install-info (6.4.90.dfsg.1-1build1) ... (Reading database ... 26272 files and directories currently installed.) Preparing to unpack .../readline-common_7.0-0ubuntu2_all.deb ... Unpacking readline-common (7.0-0ubuntu2) over (6.3-8ubuntu2) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
To verify that python3-minimal and python3-apt could unpack I had to do the same bit of editing my sources from xenial to bionic to get python3.6-minimal installed, after that the verification succeeded. bdmurray@clean-xenial-amd64:~$ sudo dpkg --unpack python3-minimal_3.6.5-3ubuntu1_amd64.deb (Reading database ... 246796 files and directories currently installed.) Preparing to unpack python3-minimal_3.6.5-3ubuntu1_amd64.deb ... Unpacking python3-minimal (3.6.5-3ubuntu1) over (3.5.1-3) ... Processing triggers for man-db (2.7.5-1) ... bdmurray@clean-xenial-amd64:~$ sudo dpkg --unpack python3-apt_1.6.1_amd64.deb (Reading database ... 246796 files and directories currently installed.) Preparing to unpack python3-apt_1.6.1_amd64.deb ... Unpacking python3-apt (1.6.1) over (1.1.0~beta1ubuntu0.16.04.1) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
I preformed and upgrade of an Ubuntu Desktop system from xenial w/ -proposed enabled to bionic (after hacking DistUpgradeController.py not to disable -proposed) so that python3-minimal from bionic-proposed would be used and the upgrade proceeded without error. bdmurray@clean-xenial-amd64:~$ grep -C10 python3-minimal /var/log/dist-upgrade/apt-term.log Selecting previously unselected package python3.6-minimal. Preparing to unpack .../python3.6-minimal_3.6.5-3_amd64.deb ... Unpacking python3.6-minimal (3.6.5-3) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Processing triggers for man-db (2.7.5-1) ... Setting up libssl1.1:amd64 (1.1.0g-2ubuntu4.1) ... locale: Cannot set LC_ALL to default locale: No such file or directory Setting up libpython3.6-minimal:amd64 (3.6.5-3) ... Setting up python3.6-minimal (3.6.5-3) ... (Reading database ... 246397 files and directories currently installed.) Preparing to unpack .../python3-minimal_3.6.5-3ubuntu1_amd64.deb ... Unpacking python3-minimal (3.6.5-3ubuntu1) over (3.5.1-3) ... Selecting previously unselected package libreadline7:amd64. Preparing to unpack .../libreadline7_7.0-3_amd64.deb ... Unpacking libreadline7:amd64 (7.0-3) ... Selecting previously unselected package libpython3.6-stdlib:amd64. Preparing to unpack .../libpython3.6-stdlib_3.6.5-3_amd64.deb ... Unpacking libpython3.6-stdlib:amd64 (3.6.5-3) ... Selecting previously unselected package python3.6. Preparing to unpack .../python3.6_3.6.5-3_amd64.deb ... Unpacking python3.6 (3.6.5-3) ... Preparing to unpack .../libpython3-stdlib_3.6.5-3ubuntu1_amd64.deb ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
I also performed an upgrade of an Ubuntu Desktop system from xenial w/ -proposed enabled to artful so that python3-minimal from artful-proposed would be used and the upgrade proceeded without error. bdmurray@clean-xenial-amd64:/tmp/ubuntu-release-upgrader-355quvv3$ grep -C10 python3-minimal /var/log/dist-upgrade/apt-term.log Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for cups (2.1.3-4) ... Updating PPD files for postscript-hp ... Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu13.6) ... Setting up libpython3.6-minimal:amd64 (3.6.3-1ubuntu1) ... Setting up libexpat1:amd64 (2.2.3-1) ... Setting up python3.6-minimal (3.6.3-1ubuntu1) ... Processing triggers for libc-bin (2.26-0ubuntu2.1) ... (Reading database ... 209379 files and directories currently installed.) Preparing to unpack .../python3-minimal_3.6.3-0ubuntu3_amd64.deb ... Unpacking python3-minimal (3.6.3-0ubuntu3) over (3.5.1-3) ... Setting up python3-minimal (3.6.3-0ubuntu3) ... (Reading database ... 209379 files and directories currently installed.) Preparing to unpack .../python3_3.6.3-0ubuntu3_amd64.deb ... running python pre-rtupdate hooks for python3.6... Unpacking python3 (3.6.3-0ubuntu3) over (3.5.1-3) ... Preparing to unpack .../mime-support_3.60ubuntu1_all.deb ... Unpacking mime-support (3.60ubuntu1) over (3.59ubuntu1) ... Selecting previously unselected package libpython3.6-stdlib:amd64. Preparing to unpack .../libpython3.6-stdlib_3.6.3-1ubuntu1_amd64.deb ... Unpacking libpython3.6-stdlib:amd64 (3.6.3-1ubuntu1) ... Selecting previously unselected package python3.6. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
To verify this I actually had to edit my sources.list from xenial to artful so I could first install python3.6-minimal which depended on libc6 before I could unpack python3-minimal and python3-apt. After that it worked though. bdmurray@clean-xenial-amd64:~$ sudo dpkg --unpack python3-minimal_3.6.3-0ubuntu3_amd64.deb (Reading database ... 209665 files and directories currently installed.) Preparing to unpack python3-minimal_3.6.3-0ubuntu3_amd64.deb ... Unpacking python3-minimal (3.6.3-0ubuntu3) over (3.5.1-3) ... Processing triggers for man-db (2.7.5-1) ... bdmurray@clean-xenial-amd64:~$ sudo dpkg --unpack python3-apt_1.4.0~beta3build2_amd64.deb (Reading database ... 209665 files and directories currently installed.) Preparing to unpack python3-apt_1.4.0~beta3build2_amd64.deb ... Unpacking python3-apt (1.4.0~beta3build2) over (1.1.0~beta1build1) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
Hello Nataly, try this, all as root (sudo before each command, or one sudo -s before them all..) apt-get update apt-get install python3.6-minimal apt-get install python3-minimal apt-get install python3 apt-get install -f Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
hello Łukasz Zemczak i am new in Ubuntu. but i have the same problem. could you help me resolve it? I have Ubuntu 18.04 and python3.6. And few apps which cant work without solving this bug. При обработке следующих пакетов произошли ошибки: python3 update-notifier-common gnome-shell update-notifier gnome-menus E: Sub-process /usr/bin/dpkg returned an error code (1) i have added -proposed repository. When i try upgrade i have this mistake: installed python3 package post-installation script subprocess returned error exit status 4 and so on. Could you help me please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
Hello Seth, or anyone else affected, Accepted python3-defaults into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.6.5-3ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: python3-defaults (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: python3-defaults (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Changed in: python3-defaults (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: In Progress Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: In Progress 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: In Progress Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: In Progress Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: New 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Description changed: - do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install - failure: + [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". - Fetched 2,320 MB in 6s (27.8 MB/s) + [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... - Upgrading - Inhibiting until Ctrl+C is pressed... - Fetched 0 B in 0s (0 B/s) - Extracting templates from packages: 100% - Preconfiguring packages ... - setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file - Extracting templates from packages: 100% - Preconfiguring packages ... - setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file - Extracting templates from packages: 100% - Preconfiguring packages ... - setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file - Extracting templates from packages: 100% - Preconfiguring packages ... - setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file - (Reading database ... 373383 files and directories currently installed.) - Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... - Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... - Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... - update-initramfs: deferring update (trigger activated) - Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... - Processing triggers for install-info (6.1.0.dfsg.1-5) ... - Processing triggers for man-db (2.7.5-1) ... - Processing triggers for initramfs-tools (0.122ubuntu8.11) ... - update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic - Setting up base-files (10.1ubuntu2) ... - Installing new version of config file /etc/debian_version ... - Installing new version of config file /etc/issue ... - Installing new version of config file /etc/issue.net ... - Installing new version of config file /etc/lsb-release ... - Updating /etc/profile to current default. - motd-news.service is a disabled or a static unit, not starting it. - Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... - update-initramfs: deferring update (trigger activated) - Processing triggers for initramfs-tools (0.122ubuntu8.11) ... - update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic - (Reading database ... 373388 files and directories currently installed.) - Preparing to unpack .../debianutils_4.8.4_amd64.deb ... - Unpacking debianutils (4.8.4) over (4.7) ... - Processing triggers for man-db (2.7.5-1) ... - Setting up debianutils (4.8.4) ... - (Reading database ... 373388 files and directories currently installed.) - Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... - Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... - Processing triggers for install-info (6.1.0.dfsg.1-5) ... - Processing triggers for man-db (2.7.5-1) ... - Setting up bash (4.4.18-2ubuntu1) ... - Installing new version of config file /etc/bash.bashrc ... - Installing new version of config file /etc/skel/.profile ... - update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode - (Reading database ... 373388 files and directories currently installed.) - Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ... - Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ... - Selecting previously unselected package libcom-err2:amd64. - Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ... - Unpacking libcom-err2:amd64 (1.44.1-1) ... - Processing triggers for libc-bin (2.23-0ubuntu10) ... - Setting up libcom-err2:amd64 (1.44.1-1) ... - Processing triggers for libc-bin (2.23-0ubuntu10) ... - (Reading database ... 373391 files and directories currently installed.) - Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ... - Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ... - Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ... - Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... - Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ... - Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... - Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ... - Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... - Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ... - Unpacking libkrb5-3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... - Preparing to unpack
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Also affects: python3-defaults (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu Artful) Status: New => Invalid ** Changed in: python3-defaults (Ubuntu Bionic) Milestone: None => ubuntu-18.04.1 ** Changed in: ubuntu-release-upgrader (Ubuntu Bionic) Status: New => Invalid ** Changed in: python3-defaults (Ubuntu Artful) Status: New => Triaged ** Changed in: python3-defaults (Ubuntu Artful) Importance: Undecided => Critical ** Changed in: python3-defaults (Ubuntu Bionic) Status: New => Triaged ** Changed in: python3-defaults (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: python3-defaults (Ubuntu) Milestone: ubuntu-18.04.1 => None ** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Triaged Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Triaged Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: New Bug description: do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: Fetched 2,320 MB in 6s (27.8 MB/s) Upgrading Inhibiting until Ctrl+C is pressed... Fetched 0 B in 0s (0 B/s) Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file (Reading database ... 373383 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic Setting up base-files (10.1ubuntu2) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Updating /etc/profile to current default. motd-news.service is a disabled or a static unit, not starting it. Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.4_amd64.deb ... Unpacking debianutils (4.8.4) over (4.7) ... Processing triggers for man-db (2.7.5-1) ... Setting up debianutils (4.8.4) ... (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Setting up bash (4.4.18-2ubuntu1) ... Installing new version of config file /etc/bash.bashrc ... Installing new version of config file /etc/skel/.profile ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ...
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Changed in: python3-defaults (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed Status in python3-defaults package in Debian: New Bug description: do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: Fetched 2,320 MB in 6s (27.8 MB/s) Upgrading Inhibiting until Ctrl+C is pressed... Fetched 0 B in 0s (0 B/s) Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file (Reading database ... 373383 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic Setting up base-files (10.1ubuntu2) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Updating /etc/profile to current default. motd-news.service is a disabled or a static unit, not starting it. Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.4_amd64.deb ... Unpacking debianutils (4.8.4) over (4.7) ... Processing triggers for man-db (2.7.5-1) ... Setting up debianutils (4.8.4) ... (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Setting up bash (4.4.18-2ubuntu1) ... Installing new version of config file /etc/bash.bashrc ... Installing new version of config file /etc/skel/.profile ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ... Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ... Selecting previously unselected package libcom-err2:amd64. Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ... Unpacking libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Setting up libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... (Reading database ... 373391 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ... Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ... Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ... Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ... Unpacking libkrb5-3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../liblzma5_5.2.2-1.3_amd64.deb ...
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Bug watch added: Debian Bug tracker #901001 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901001 ** Also affects: python3-defaults (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901001 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed Status in python3-defaults package in Debian: Unknown Bug description: do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: Fetched 2,320 MB in 6s (27.8 MB/s) Upgrading Inhibiting until Ctrl+C is pressed... Fetched 0 B in 0s (0 B/s) Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file (Reading database ... 373383 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic Setting up base-files (10.1ubuntu2) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Updating /etc/profile to current default. motd-news.service is a disabled or a static unit, not starting it. Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.4_amd64.deb ... Unpacking debianutils (4.8.4) over (4.7) ... Processing triggers for man-db (2.7.5-1) ... Setting up debianutils (4.8.4) ... (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Setting up bash (4.4.18-2ubuntu1) ... Installing new version of config file /etc/bash.bashrc ... Installing new version of config file /etc/skel/.profile ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ... Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ... Selecting previously unselected package libcom-err2:amd64. Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ... Unpacking libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Setting up libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... (Reading database ... 373391 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ... Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ... Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ... Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Summary changed: - python3-minimal should depend on versioned version of python3-minimal + python3-minimal should predepend on versioned version of python3-minimal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed Bug description: do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: Fetched 2,320 MB in 6s (27.8 MB/s) Upgrading Inhibiting until Ctrl+C is pressed... Fetched 0 B in 0s (0 B/s) Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file (Reading database ... 373383 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic Setting up base-files (10.1ubuntu2) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Updating /etc/profile to current default. motd-news.service is a disabled or a static unit, not starting it. Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.4_amd64.deb ... Unpacking debianutils (4.8.4) over (4.7) ... Processing triggers for man-db (2.7.5-1) ... Setting up debianutils (4.8.4) ... (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Setting up bash (4.4.18-2ubuntu1) ... Installing new version of config file /etc/bash.bashrc ... Installing new version of config file /etc/skel/.profile ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ... Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ... Selecting previously unselected package libcom-err2:amd64. Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ... Unpacking libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Setting up libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... (Reading database ... 373391 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ... Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ... Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ... Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ... Unpacking libkrb5-3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack
