** Changed in: friendly-recovery (Ubuntu)
Status: Triaged => Invalid
** Changed in: friendly-recovery (Ubuntu Bionic)
Status: New => Invalid
** Changed in: friendly-recovery (Ubuntu Cosmic)
Status: New => Invalid
--
You received this bug notification because you are a membe
This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.11.1
---
ubuntu-release-upgrader (1:18.10.11.1) cosmic; urgency=medium
* DistUpgrade/DistUpgradeController.py: check all the python symlinks and
versions instead of the python one. Thanks to juliank for the assi
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.28
---
ubuntu-release-upgrader (1:18.04.28) bionic; urgency=medium
* DistUpgrade/DistUpgradeController.py: check all the python symlinks and
versions instead of the python one. Thanks to juliank for the assistan
I tested this on Ubuntu 18.04 and while the original test case did not
fail, the version of ubuntu-release-upgrader from -proposed also works.
I think it is worth installing this update as it is an improvement and
checks both python and python3 and we don't know what kind of crazy
things people do
I installed the version of ubuntu-release-upgrader from -proposed on an
Ubuntu 18.10 system then rebooted into recovery mode and was able to
successfully launch "repair broken packages".
** Attachment added: "Screenshot from 2018-11-05 09-25-27.png"
https://bugs.launchpad.net/ubuntu/+source/fr
Hello Brian, or anyone else affected,
Accepted ubuntu-release-upgrader into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:18.04.28 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Brian, or anyone else affected,
Accepted ubuntu-release-upgrader into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:18.10.11.1 in a few hours, and then in the
-proposed repository.
Please help us by testing th
** Also affects: friendly-recovery (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: friendly-recovery (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Al
This bug was fixed in the package ubuntu-release-upgrader - 1:19.04.1
---
ubuntu-release-upgrader (1:19.04.1) disco; urgency=medium
* DistUpgrade/{EOL,Devel}ReleaseAnnouncement,
DistUpgrade/window_main.ui,
data/gtkbuilder/DistUpgrade.ui,
data/DistUpgrade.cfg,
pre-bui
** Branch linked: lp:~ubuntu-core-dev/ubuntu-release-upgrader/cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799839
Title:
not possible to use "Repair broken packages"
To manage notification
I think that's actually the same bug as the one I just opened: bug
1800823, but as mentioned, the solution should cover all python symlinks
and not just python3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
To further expand on the "all symlinks":
> [Regression Potential]
> The code is just being updated to use python3 instead of python so there
> isn't any change of a regression.
That's wrong. You can now clearly symlink python to python3 (or 2.6) and
you'd get a ton of errors from postinsts.
--
We probably should sanity check all of python, python2, python3; not
just the most recent one. The python sanity checking exists to make sure
pyclean and friends work and don't cause a ton of upgrade failure
reports.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Branch linked: lp:ubuntu-release-upgrader
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799839
Title:
not possible to use "Repair broken packages"
To manage notifications about this bug go to:
** Description changed:
[Impact]
It is not possible to use "Repair broken packages" in friendly recovery as it
calls dist-upgrade.py and that fails as it checks to see if the python symlink,
not python3 symlink is good.
[Test Case]
Run the following as root:
env RELEASE_UPGRADER_
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Description changed:
+ [Impact]
+ It is not possible to use "Repair broken packages" in friendly recovery as it
calls dist-upgrade.py and that fails as it checks to see if the python symlink,
not python3 symlink is good.
+
+ [Test Case]
+ Run the following as root:
+
+ env RELEASE_UPGRADER_
** Changed in: friendly-recovery (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799839
Title:
not possible to use "Repair broken packages"
To manage notif
** Changed in: friendly-recovery (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799839
Title:
not possible to use "Repair broken packages"
To manage notif
See also the following ubuntu-release-upgrader bug LP: #1798872.
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importan
20 matches
Mail list logo
