[06:30] <nteodosio> Is there any way to override this error? I think the free 10 GB might suffice and would like to try the build.
[06:30] <nteodosio> E: Disk space is probably not sufficient for building. I: Source needs 26372388 KiB, while 36952488 KiB is free. (From https://launchpadlibrarian.net/746095192/buildlog_ubuntu-oracular-amd64.chromium-browser_2%3A130.0.6669.2-1_BUILDING.txt.gz)
[07:37] <cjwatson> nteodosio: I think the only way would be to patch launchpad-buildd to add `$check_space = 0;` to its sbuildrc - in the context of Launchpad it probably makes sense for that check to be unconditionally switched off
[07:46] <nteodosio> Thanks cjwatson, I opened bug 2077943 for that.
[07:46] -ubottu:#launchpad- Bug 2077943 in Launchpad itself "E: Disk space is probably not sufficient for building." [Undecided, New] https://launchpad.net/bugs/2077943
[07:54] <cjwatson> nteodosio: The task against Launchpad itself should be deleted / marked invalid
[07:54] <cjwatson> (but thanks)
[07:57] <nteodosio> And thank you for the quick responses!
[15:12] <jbicha> there is a chroot tarball for oracular that is used by the .deb package sbuild-launchpad-chroot. It looks like it is still pointing to a noble chroot. Could the chroot be updated?
[15:14] <guruprasad> jbicha, we had issues updating to the latest chroots because of missing deb822 support in launchpad/launchpad-buildd. So I'd guess the same is the blocker for updating the oracular chroot.
[15:15] <guruprasad> I can take this request to my team and see what we can do to unblock this.
[15:15] <guruprasad> If you need this to prioritized, please speak to Clinton.
[15:15] <guruprasad> *to be
[15:17] <guruprasad> pelpsi, FYI
[15:21] <jbicha> it's easy for me to workaround since I just manually update it once locally, but I guess the chroot would ideally be updated before 24.10 is released
[15:22] <nteodosio> I have in a PPA for repository size 11.4 GiB (100.00%) of 8.0 GiB. Is this supposed to be? I'd assume Launchpad would reject uploads that would extrapolate that limit.
[15:23] <guruprasad> nteodosio, it might have allowed it because the usage before an upload was under the quota and the upload just took it over the quota. I am not sure about how this works and will have to check.
[15:23] <cjwatson> IIRC the quota is checked on source uploads, but not on binary uploads, so there's some slop.  I'm fairly sure this is intended, on the grounds that it's worse to reject completed builds than to accept them even though they go over quota.
[15:23] <cjwatson> The quota is meant as a rough control rather than a rigid one.
[15:23] <guruprasad> TIL. Thanks cjwatson
[15:24] <guruprasad> The part about rejecting source uploads vs binary uploads from completed builds makes a lot of sense to me.
[15:24] <nteodosio> Hmm I did bring the package that overstepped the limit from another PPA via the "copy packages" button, but I chose "Rebuild the copied sources" (the build in the source PPA had failed anyway so there was nothing binary to copy).
[15:25] <cjwatson> It's also possible LP doesn't bother to check it on copies - I don't quite remember.
[15:26] <cjwatson> Copies use some extra space, but (effectively, across the whole infrastructure) about half as much as "real" uploads - because the librarian files are shared in that case.
[15:26] <cjwatson> And in principle the files could be shared on the PPA side as well, though not currently.
[15:28] <cjwatson> Yeah, not checked on copies from what I can see.
[15:30] <nteodosio> The PPA in question is for Chromium and so its tarball is quite bulky. Do I understand correctly that that orig is just a "symlink" in the target PPA? (By target PPA I meant, the PPA which was the target of the copy operation.)
[15:32] <nteodosio> Hmm but then the limit would not have been so much overstepped, so maybe I do understand wrong.
[15:32] <cjwatson> Not quite.  The file is only stored once in the librarian (Launchpad's object store), with multiple references to it; but on the PPA publishing side, it's copied.
[15:33] <nteodosio> Ack, thank you for the help.
[15:33] <cjwatson> This is https://bugs.launchpad.net/launchpad/+bug/379726 BTW
[15:33] -ubottu:#launchpad- Launchpad bug 379726 in Launchpad itself "PPA quota not checked when doing package copies" [High, Triaged]
[15:34] <cjwatson> (When I was working on Launchpad, my view was that the time involved in fine-tuning that sort of thing would be better spent working on restructuring PPA publishing so that it didn't make copies of all those files in the first place ...)
[15:36] <jbicha> nteodosio: also you can ask for a higher quota for specific PPAs if needed
[15:42] <nteodosio> Not absolutely necessary, I can delete older packages. But I do also have problems with the disk space  in the builder though... When everything is a problem, the problem is... Chromium!
=== blackboxsw is now known as blackboxsw_away