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

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)?
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).