[Bug 1807043] Re: when rewriting sources.list ubuntu-release-upgrader doesn't check to see if new release is available
Launchpad Bug Tracker
1807043 at bugs.launchpad.net
Thu Jan 31 09:20:22 UTC 2019
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.30
---------------
ubuntu-release-upgrader (1:18.04.30) bionic; urgency=medium
* data/release-upgrades: Clarify documentation regarding the behavior for
different Prompt settings. (LP: #1795024)
* do-release-upgrade: Utilize information regarding what Prompt is set to so
that a more informative error message can be displayed.
(LP: #1798618, LP: #1795024)
* DistUpgrade/DistUpgradeCache.py: When calculating free space needed for
mount points don't use a negative number as the buffer. (LP: #1786484)
* fix more typos re RELEASE_UPRADER_ALLOW_THIRD_PARTY
* DistUpgrade/DistUpgradeController.py: When rewriting sources.list entries
check to see if the source provides packages for the release to which the
upgrade is occurring. If it doesn't the entry is disabled thereby
improving upgrades with PPAs. (LP: #1807043)
* do-release-upgrade: add a parameter to allow third party mirrors and
repositories, additionally pass along the environmental variable
RELEASE_UPGRADER_ALLOW_THIRD_PARTY via pkexec and sudo. (LP: #1807032)
* DistUpgrade/DistUpgradeCache.py: improve messaging regarding failures to
calculate the upgrade and suggest using ppa-purge if PPAs are an issue.
* DistUpgrade/DistUpgradeCache.py: in the event there is a failure to
calculate the upgrade provide information about the log files in
/var/log/dist-upgrade. (LP: #1771387)
* debian/source_ubuntu-release-upgrader.py: Include xorg_fixup.log if it
exists.
* DistUpgrade/xorg_fix_proprietary.py: modify how the system is checked to
see if nvidia is being used, drop fglrx check since it has been
deprecated. (LP: #1773637)
-- Brian Murray <brian at ubuntu.com> Wed, 16 Jan 2019 15:53:58 -0800
** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1807043
Title:
when rewriting sources.list ubuntu-release-upgrader doesn't check to
see if new release is available
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
Fix Released
Status in ubuntu-release-upgrader source package in Cosmic:
Fix Released
Bug description:
[Impact]
When rewriting sources.list entries the release-upgrader doesn't check to see if the distribution to which the system is being upgraded is supported by the archive / PPA. This results in the following error message:
A problem occurred during the update. This is usually some sort of
network problem, please check your network connection and retry.
E:The repository 'http://ppa.launchpad.net/team-xbmc/ppa/ubuntu
cosmic Release' does not have a Release file.
If the release-upgrader were to actually check if the release were
supported then that specific sources entry could be disabled and the
upgrade may be able to proceed.
[Test Case]
The test case involves adding a PPA which doesn't have a release file for the release to which you are upgrading for upgrading to cosmic we can use the team-xbmc ppa.
1) sudo add-apt-repository ppa:team-xbmc/ppa
2) do-release-upgrade --frontend DistUpgradeViewText
3) Observe the error message re "does not have a Release file" and the upgrade cancel.
With the version of the release upgrader from -proposed you will
instead see the following message: "Some third party entries in your
sources.list were disabled.". Then the release upgrade will proceed to
the calculation phase, you can quit the upgrade after the calculation
and check /var/log/dist-upgrade/main.log for the following:
DEBUG entry '# deb http://ppa.launchpad.net/team-xbmc/ppa/ubuntu
bionic main' was disabled (no Release file)
[Regression Potential]
It seems like an oversight that this part of the release-upgrader never did check for Release files and that this is the right thing to do. Its possible that people who were not allowed to upgrade, because they had PPAs without support for the release to which they wanted to upgrade, are now allowed to upgrade and somehow run in to an upgrade failure e.g. a failure to calculate the upgrade. That seems better and more informative than not allowing them to upgrade at all though.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1807043/+subscriptions
More information about the foundations-bugs
mailing list