Your message dated Mon, 28 Dec 2020 17:30:25 +0100 with message-id <20201228163025.trqoeo2om2bw6xzx@crossbow> and subject line Re: linux-image-amd64: check if there is enough storage space before installing package and warn user if not has caused the Debian Bug report #976648, regarding linux-image-amd64: check if there is enough storage space before installing package and warn user if not to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 976648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976648 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-image-amd64: check if there is enough storage space before installing package and warn user if not
- From: florine forine <florine@danwin1210.me>
- Date: Sun, 6 Dec 2020 13:45:52 +0000
- Message-id: <X8gjS42UP3TanwaQ@localhost>
Package: linux-image-amd64 Version: 5.9.11-1 Severity: normal Dear Maintainer, * What led up to the situation? upgrade linux-image-amd64. * What exactly did you do (or not do) that was effective (or ineffective)? shortage of disk space on partition where modules are installed. * What was the outcome of this action? unsuccessful upgrade, kernel package remained in status "broken", couldn't install, couldn't deinstall older kernels because the broken package needed to be fixed first * What outcome did you expect instead? apt could estimate needed disk space; warn user, if there is not enough disk space available (broken down to partions) -- System Information: Debian Release: bullseye/sid Architecture: amd64 (x86_64) iu linux-image-5.9.0-4-amd64 5.9.11-1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information --Attachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: florine forine <florine@danwin1210.me>
- Cc: 976648-done@bugs.debian.org
- Subject: Re: linux-image-amd64: check if there is enough storage space before installing package and warn user if not
- From: David Kalnischkies <david@kalnischkies.de>
- Date: Mon, 28 Dec 2020 17:30:25 +0100
- Message-id: <20201228163025.trqoeo2om2bw6xzx@crossbow>
- In-reply-to: <X8gjS42UP3TanwaQ@localhost>
- References: <X8gjS42UP3TanwaQ@localhost>
On Sun, Dec 06, 2020 at 01:45:52PM +0000, florine forine wrote: > apt could estimate needed disk space; warn user, if there is not enough disk > space available (broken down to partions) APT already checks if there is enough space on the disk for storing the debs it downloads in the location it downloads them to as well as if the root partition has enough space to house the (potential) increase in diskspace needs for the packages as they advertise. APT can not check for individual partitions though as APT has no idea which file will end up on which partition or e.g. which files will be generated at installation time, with what size and where (in terms of kernel that would be e.g. initrd). I assume you have a separate /boot partition based on your bugreport. I would recommend making it large enough to house a couple kernels in parallel and consider running "apt autoremove" regularly (check the output of course!). That should take care of deinstalling older kernels as well as apt tries to keep tabs on which kernel is current, keeping some in reserve in case of boot regressions and getting rid of the rest. If you keep forgetting this, it might be a good idea to add a custom hook checking and reminding you about this. A support channel can probably help you configure something like this for you individually, but I fear apt can never have a generic solution as the possibilities for partitioning are endless. I am therefore closing as "already implemented as far as we can go without opening Pandora's box". Best regards David KalnischkiesAttachment: signature.asc
Description: PGP signature
--- End Message ---