Avoid full rebuild after out-of-space on x1e-6.16.0-rc4-jg-0

[emezeta]

Non critical fails trying ubuntu-qcom-x1e-6.16.0-rc4-jg-0

Build stopped near the end due I ran out of partition space (not a compile error).
Is there a way to resume or avoid a full rebuild after a near-successful build?
Maybe comment dh_cleans in rebuilds.sh or next?
Would comment some dh_clean in ./rebuild.sh (and next) help here? Or is there a better way?

Short yes/no answers or quick tips are very welcome!

ps. let's see real 776m19.894s is a nice little while....

[jglathe]

no, please rebuild - it will be unclean otherwise. There are other ways of doing dev builds.

[jglathe]

Depending on machine, I get between 30m and 90m build time. 30m on AMD R9-5950X, ~45m on Snapdragon Dev Kit X1E-001-DE, ~55m on Thinkbook 16 X1P-42-100, ~90m on Windows Dev Kit 2023 SC8280XP. The most power efficient is probably the X1P-42-100.

[emezeta]

Things went better now!
all .deb files were created Ok.

dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build .
dpkg-source: info: using options from 6.16.0-rc4-jg-0/debian/source/options: --diff-ignore --tar-ignore
dpkg-buildpackage: info: binary-only upload (no source included)

real    162m31.909s
user    956m45.903s
sys     114m48.118s
snapdragon@leonidas:~/6.16.0-rc4-jg-0$ apt-get build-dep .

This is my old Dell XPS-15-9550 | Intel Core i7 CPU @ 2.60GHz | 16GiB DDR4 2133 | MHz NVMe 500G
and it's also the reason why I replace it: latitude-7455 X Elite ;)

Now I just have to figure out what to do with these rc4-jg-0 .deb files.
I might inject them into a Plucky ISO [unpack/repack] or try booting with an EFI kernel-only setup...
But that's another story :-)

Thanks for now!

[jglathe]

Mucking around with the ISOs is time consuming IMO. For the 7455, easiest would be to use /modify one of the raw images. Like used in #36. I really should add a Wiki for this.