Bug#1035941: linux-image-amd64: too much space needed to build

[Diederik de Haas]

Control: reassign -1 debian-kernel-handbook 1.0.21
Control: severity -1 wishlist
Control: retitle -1 debian-kernel-handbook: Paragraph 4.5.1.1. Disk space 
requirements needs an update (from 2018 numbers)?

On Thursday, 11 May 2023 14:33:40 CEST Claude Heiland-Allen wrote:
> I freed up more space, but even with 53GB available it ran out.
> 
>* What outcome did you expect instead?
> 
> The build process to use a reasonable amount of space,
> perhaps by cleaning up artifacts after each output deb
> before starting to build the next output deb.
> 
> Documentation of the required amount of disk space would be nice.

The kernel is a big package and if you don't restrict what's getting build via
f.e. build profiles then it will need a lot of space. Especially debug packages
can get rather large. But it could be that the numbers mentioned in the 
debian-kernel-handbook are a bit too optimistic.

"Building binary packages for a single kernel flavour requires up to 15 GB 
space"
could be technically correct, but unless you're 'deep' into Debian kernel
building, you likely won't spot the importance of the chosen words.
IOW: newbies likely assume they need 15GB of disk space, while that's only
true in specific circumstances (as described in 4.5.5).


signature.asc
Description: This is a digitally signed message part.

Bug#1035941: linux-image-amd64: too much space needed to build

[Claude Heiland-Allen]

Package: linux-image-amd64
Severity: normal
X-Debbugs-Cc: cla...@mathr.co.uk

Dear Maintainer,

   * What led up to the situation?

I tried to build locally-patched kernel debs:

sudo apt build-dep linux-image-6.1.0-8-amd64-unsigned
apt source linux-image-6.1.0-8-amd64-unsigned
cd linux-6.1.25
# make changes to source code
debuild -i -us -uc -b

   * What was the outcome of this action?

I ran out of disk space.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I freed up more space, but even with 53GB available it ran out.

   * What outcome did you expect instead?

The build process to use a reasonable amount of space,
perhaps by cleaning up artifacts after each output deb
before starting to build the next output deb.

Documentation of the required amount of disk space would be nice.

Thanks for your work on this package,


Claude


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (990, 'testing-security'), (990, 'testing'), (500, 
'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-8-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
pn  linux-image-6.1.0-8-amd64  

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.