This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.12
---
ubuntu-release-upgrader (1:18.04.12) bionic; urgency=medium
[ Simon Quigley ]
* Port away from kdesudo.
[ Brian Murray ]
* Increase the size of the buffer used when calculating the free space to
es
What is the right origin? How'd you determine that? You cannot really
know whether lsb-release is wrong or something else (or nothing).
Imagine a user with artful and bionic sources, and lsb-release from
bionic - he might be running
(a) bionic
(b) artful with wrong lsb-release
(c) some artful-bio
Maybe we can just check that the lsb-release package has the right
package origin? I'm thinking of something along the lines of
https://bazaar.launchpad.net/~ubuntu-core-
dev/ubuntu/bionic/apport/ubuntu/view/head:/backends/packaging-apt-
dpkg.py#L166.
This way we could exit out of the upgrade proc
I'm not sure how we'd achieve that. Figuring out which release is the
correct one is a much harder problem than figuring out that the release
we're being told is not the same as in sources.list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
While this looks fine perhaps this should be fixed in the function
get_dist() from DistUpgrade/utils.py that way the release-upgrader
tarball for the wrong next release never gets downloaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Merge proposal: https://code.launchpad.net/~juliank/ubuntu-release-
upgrader/double-check-source-release/+merge/337258
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725359
Title:
release detection
** Branch linked: lp:~juliank/ubuntu-release-upgrader/double-check-
source-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725359
Title:
release detection relies on lsb-release
To manage not
I think we need something like that:
=== modified file 'DistUpgrade/DistUpgradeController.py'
--- DistUpgrade/DistUpgradeController.py2018-01-29 09:43:48 +
+++ DistUpgrade/DistUpgradeController.py2018-02-07 10:01:22 +
@@ -772,6 +772,17 @@
logging.debug("updateSourc
Sorry, I hit comment before finishing, anyways, I ran the following commands in
the terminal: sudo apt-get install aptitude
sudo aptitude update
sudo aptitude dist-upgrade
This upgraded me fully to 17.04 and then I was able to upgrade fully to 17.10
right after. Thanks 😀
--
You received this bu
Thanks for the guidance, I was able to upgrade after doing a couple of
things. First I changed the file names from Xenial to Zesty in
/etc/apt/sources.list. After that I tried to upgrade the dist to 17.10
but it was going to do a partial upgrade which I heard is not a good
thing to do. I cancelled
** Description changed:
- ubuntu-release-upgrader used lsb-release to determine the version of
+ ubuntu-release-upgrader uses lsb-release to determine the version of
Ubuntu the system is running, however no double checking is done. As we
can see in bug 1725176, the user installed the version
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725
** Tags added: id-59ea20b4591cda0fc786e8b6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725359
Title:
release detection relies on lsb-release
To manage notifications about this bug go to:
https:/
13 matches
Mail list logo
