The case when u-r-u considered (then skipped) removing the running
kernel package will be fixed with LP: #1615381 getting fixed in APT.
Until this happens it is better to keep the sanity check in
tryMarkObsoleteForRemoval() and maybe extend it to cover package names
ending with the kernel version
This bug was fixed in the package ubuntu-release-upgrader - 1:19.10.9
---
ubuntu-release-upgrader (1:19.10.9) eoan; urgency=medium
* DistUpgrade/DistUpgradeCache.py, DistUpgrade/DistUpgradeController.py:
drop code which identified obsolete kernels and marked them for removal as
** 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/1828100
Title:
KernelRemoval section of DistUpgrade.cfg shouldn't require manual
updating
To manage
** Changed in: ubuntu-release-upgrader (Ubuntu Eoan)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: ubuntu-release-upgrader (Ubuntu Eoan)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It was suggested that testing upgrades from Ubuntu 18.04 should also be
done so I tested an upgrade from Ubuntu 18.04 to Ubuntu 19.04 and eoan
(which will become Ubuntu 19.10) and both of these behaved in the same
way with the removal of identifyObsoleteKernels so lets do that.
--
You received
I went ahead and disabled the identifyObsoleteKernels function and here
is the relevant part of /var/log/dist-upgrade/main.log:
2019-06-19 15:37:29,707 DEBUG Obsolete: libisl19 libpoppler85
linux-headers-5.0.0-13 linux-headers-5.0.0-13-generic
linux-image-5.0.0-13-generic
I also tested an upgrade from Ubuntu 19.04 to eoan and here we can see
identifyObsoleteKernels actually attempting to do something wrong -
suggesting to remove the kernel just installed. While this is because
Ubuntu 19.04 and eoan currently have the same kernel version it still
seems like an
Testing an upgrade from Ubuntu 18.10 to Ubuntu 19.04 I noticed that the
identifyObsoleteKernels function returns a set of linux packages which
was already identified as obsolete so dropping the functionality as
Balint suggested seems easiest.
Relevant part of /var/log/dist-upgrade/main.log:
** Tags added: id-5cd44c37cb4cfa83161e8d98
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828100
Title:
KernelRemoval section of DistUpgrade.cfg shouldn't require manual
updating
To manage
So I propose just dropping the functionality from u-r-u which would
solve the maintenance problem since the kernels are removed in other
ways.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828100
I'm wondering if we still need this functionality in u-r-u.
It offers removing removal of all autoremovable packages at the end of
the upgrade for a long time and kernels are autoremoved periodically by
unattended-upgrades and update-manager in Xenial and up.
IMO those are enough and since u-r-u
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => High
** Also affects: ubuntu-release-upgrader (Ubuntu Eoan)
Importance: High
Status: New
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: id-5cd1c9cc9dc3ea20e97b7fbd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828100
Title:
KernelRemoval section of DistUpgrade.cfg shouldn't require manual
updating
To manage
Additionally, the Version part of KernelRemoval is expected to be a
string and not a list so you can't have multiple kernel versions thereby
making it so that we can only remove the release kernel or the hwe one
which is also lame.
--
You received this bug notification because you are a member
14 matches
Mail list logo
