On Sat, Aug 05, 2017 at 06:32:47AM -, Jarno Suni wrote:
> I do not understand that why the code is used in ubuntu-release-upgrader
> only.
Because update-manager depends on python3-distupgrade and imports the size
checking code from there. It does not make sense to have two copies of this
If patch https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/1678187/comments/8 is applied, there is no need for one extra
sizeof(initramfs) in separate /boot since the new file is created in
"${TMPDIR:-/var/tmp}" and the old one is only replaced by it in /boot.
But still some other
I do not understand that why the code is used in ubuntu-release-upgrader
only. Doesn't update-manager need to check free space before installing
new kernels? At least some version of updater-manager may display a
dialog like this https://i.stack.imgur.com/DppOi.png ?
--
You received this bug
** Changed in: update-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: update-manager (Ubuntu Yakkety)
Importance: Undecided => Low
** Changed in: update-manager (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of
This bug was fixed in the package update-manager - 1:17.04.2
---
update-manager (1:17.04.2) zesty; urgency=medium
[ Jeremy Bicha ]
* Update alternate dependencies for policykit-1-gnome:
- Add virtual polkit-1-auth-agent
- Replace non-existant policykit-1-kde with
** Branch linked: lp:update-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is inaccurate and causes
refusal to upgrade
To manage
** Changed in: update-manager (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is inaccurate
** Tags removed: rls-z-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is inaccurate and causes
refusal to upgrade
To manage
This bug was fixed in the package ubuntu-release-upgrader - 1:16.10.10
---
ubuntu-release-upgrader (1:16.10.10) yakkety; urgency=medium
* DistUpgrade/DistUpgradeCache.py: import kernel initrd size estimation
code from update-manager (since u-r-u is the only consumer of it) and
Yakkety only need 111M free so I had to fill up boot some more to
generate the error message about needing to free up space in /boot. I
then installed the packages from yakkety-proposed and verified I still
saw an error with a fuller disk and then that the upgrade proceeded with
102M (less than
Hello Steve, or anyone else affected,
Accepted ubuntu-release-upgrader into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:16.10.10 in a few hours, and then in the
-proposed repository.
Please help us by testing
This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.21
---
ubuntu-release-upgrader (1:16.04.21) xenial; urgency=medium
* DistUpgrade/DistUpgradeCache.py: import kernel initrd size estimation
code from update-manager (since u-r-u is the only consumer of it) and
** Tags removed: verification-needed
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is inaccurate and
I've verified this fix for Xenial with the version of the package in
-proposed but it might be worth noting that I first verified the refusal
to upgrade with the package from -proposed by creating a 40M file on my
/boot partition. I then removed the 40M file and upgraded rather than
repeating
On Wed, Jan 25, 2017 at 03:52:06PM -, Robie Basak wrote:
> In reviewing 1:16.10.10 in the Yakkety unapproved queue, I see changes
> to data/mirrors.cfg that aren't explained in the changelog or in this
> bug. They may be sorting noise, but SRUs are supposed to be minimal. So
> is this
In reviewing 1:16.10.10 in the Yakkety unapproved queue, I see changes
to data/mirrors.cfg that aren't explained in the changelog or in this
bug. They may be sorting noise, but SRUs are supposed to be minimal. So
is this intentional?
--
You received this bug notification because you are a member
we should eventually drop the code from update-manager, but it doesn't
need to be done in SRU.
** Changed in: update-manager (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Steve, or anyone else affected,
Accepted ubuntu-release-upgrader into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:16.04.21 in a few hours, and then in the
-proposed repository.
Please help us by testing
This is fixed in zesty, but somehow the bug did not get closed when it
migrated.
ubuntu-release-upgrader (1:17.04.6) zesty; urgency=medium
* DistUpgrade/DistUpgradeCache.py: import kernel initrd size estimation
code from update-manager (since u-r-u is the only consumer of it) and
** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is
** Description changed:
- I have a /boot partition which is sized just right to accommodate 3
- kernels, plus a little bit of overhead.
+ [SRU Justification]
+ In some configurations, update-manager will refuse to upgrade kernel
packages, citing lack of space in /boot even though there is enough
This bug was fixed in the package ubuntu-release-upgrader - 1:17.04.6
---
ubuntu-release-upgrader (1:17.04.6) zesty; urgency=medium
* DistUpgrade/DistUpgradeCache.py: import kernel initrd size estimation
code from update-manager (since u-r-u is the only consumer of it) and
** 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/1646222
Title:
calculation of needed free space in /boot is inaccurate and causes
refusal to upgrade
To
** Branch linked: lp:~ubuntu-core-dev/ubuntu-release-upgrader/yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is inaccurate and causes
** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
Status: New => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The update-manager estimate_kernel_size_in_boot() function contains the
current bug, but this function also has no consumers anywhere except in
ubuntu-release-upgrader. So I'm just going to move this code into u-r-u
to avoid having to update both packages.
** Changed in: update-manager (Ubuntu)
** Changed in: update-manager (Ubuntu)
Status: New => In Progress
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Output of update-manager --debug, per request:
$ update-manager --debug
(update-manager:14909): dconf-WARNING **: failed to commit changes to dconf:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code12:
Failed to write file '/home/vorlon/.config/dconf/user.YF08RY':
** Tags added: rls-z-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646222
Title:
calculation of needed free space in /boot is inaccurate and causes
refusal to upgrade
To manage
Related bug, which led to the current behavior: bug #1173468
At the time, the decision was made to double the calculated value for
required free space. This is better than being undersized, but it's
over large; this sets the min free space value to 2 * N_kernels *
(sizeof(kernel_package_bits) +
I think part of the issue here is the function
estimate_kernel_size_in_boot, from utils.py, which does the following:
92 def estimate_kernel_size_in_boot():
93 """ estimate the amount of space that the current kernel takes in /boot
"""
94 size = 0
95 kver = os.uname()[2]
96
31 matches
Mail list logo
