[07:40] <acheronuk> git push webhooks look to be stalled again
[08:35] <cjwatson> acheronuk: Thanks; should be recovering now
[11:32] <oSoMoN> how much disk space do builders have at their disposal when building debs?
[11:39] <wgrant> oSoMoN: The instances have 60GB root volumes, and all but a couple of gigabytes should be usable by the build
[11:41] <oSoMoN> wgrant, thanks! was this increased in the last few years by any chance? I'm asking because the libreoffice package was artificially separated into two source packages because of a disk space limitation, and I'm wondering whether we could get rid of this workaround now
[11:41] <oSoMoN> 60GB should be enough for that purpose
[11:42] <oSoMoN> but I'd like to understand what the limitation was previously
[11:54] <wgrant> oSoMoN: It's slowly increased over the years. The -l10n split was back in the Xen days.
[11:54] <wgrant> I really don't remember what things were set to back then
[11:54] <wgrant> Probably 40GB, but not sure
[11:56] <mIk3_08> Many Thanks to David Callé. God Bless you always. Happy Ubuntu.
[11:58] <wgrant> oSoMoN: Hmm, the split actually predates virtualised builders at all, so there's really no way to tell unless you can find IRC logs from 12 years ago
[12:17] <oSoMoN> wgrant, ack, in any case it looks like it's worth trying to reconcile the two source packages now, there's a good chance it will work
[12:18] <wgrant> oSoMoN: Worth a try indeed
[12:29] <cjwatson> Until a few years ago builders weren't particularly clean, either.
[12:30] <oSoMoN> cjwatson, so less disk space available due to leftovers?
[12:30] <cjwatson> Certainly in the pre-virtualised days you could very well end up with piles of junk left around from old kernels, previous builds, etc.
[12:30] <cjwatson> And it wouldn't have been consistent across builders.
[12:33] <oSoMoN> wgrant, cjwatson: thanks, I filed bug #1791943 to track attempts at merging the two source packages
[12:35] <ricotz> (old) virtual builders were affected too ;) I even made a list of working builders for libreoffice back in the days
[12:36] <wgrant> Yeah, the original virtual builders were deliberately extremely diverse hardware
[12:36] <wgrant> Often extremely bad hardware too :/
[13:20] <brainwash> the ubuntuBSD project seems to be dead https://launchpad.net/ubuntubsd
[13:21] <brainwash> the homepage links leads to some ad website, and there has not been any project activity in a long time also
[13:21] <brainwash> homepage link
[14:40] <oSoMoN> I'm seeing a snap build fail because the builder fails to clone the git repository, which is hosted on LP (it's a mirror of a github repo): https://code.launchpad.net/~ubuntu-desktop/+snap/gtk-common-themes/+build/330380
[14:41] <oSoMoN> it wasn't doing that 15min ago, is it affecting only https://git.launchpad.net/~ubuntu-desktop/gtk-common-themes/+git/master or could it be a more general issue?
[14:41] <oSoMoN> (trying to clone locally hangs, too)
[14:41] <acheronuk> yep. git clone of a LP repo is kaput
[14:42] <oSoMoN> darn
[14:42] <acheronuk> cjwatson: ^^ issue you are ware of?
[14:42] <acheronuk> *aware
[14:43] <oSoMoN> ah, a local cloning operation just completed, after seemingly hanging for 5+ mins
[14:44] <acheronuk> Cloning into 'git'...
[14:44] <acheronuk> fatal: Could not read from remote repository.
[14:44] <acheronuk> another is cloning at less than 56k modem rate
[14:45] <oSoMoN> is git.launchpad.net being DDoSed?
[14:52] <cjwatson> No, just scales badly
[14:52] <cjwatson> It's apparently recovering
[14:53] <cjwatson> (Well, I mean possibly, but more likely just normal activity ...)
[14:54] <acheronuk> Not me. I was admittedly about to clone 336 repos, but it never got started as it hung on number 1!
[23:27] <guiverc_d> suggested to try here:  If I `ubuntu-bug evince`to report an issue, apport window appears ("Collecting..") then "Send problem report to devs" (with details) with send/don't-send, but on send it closes and nothing appears to be sent..  (not via my https://errors.ubuntu.com/user/ceaac5c412433...  --- am i missing something? or issues currently?
[23:41] <wgrant> guiverc_d: ubuntu-bug questions are probably better in #ubuntu
[23:41] <guiverc_d> thanks wgrant
[23:41] <wgrant> ubuntu-bug can use the Launchpad API for some of its work, but it's not something that we have much to do with.
[23:41] <wxl> except that seems like a launchpad error?
[23:42] <wgrant> Which error?
[23:42] <wxl> oh maybe i'm wrong, actually. that's errors.u.c.
[23:42] <guiverc_d> i've ubuntu-bug reported; but none appear in errors.ubuntu.com/user/.. for my box
[23:44] <wgrant> Right, errors.u.c is not related to LP
[23:45] <guiverc_d> no issues with lp currently? or someone I can monitor in future?
[23:45] <guiverc_d> sorry somwhere (not someone)(
[23:46] <wgrant> guiverc_d: Here is the best place for Launchpad issues. But there's nothing awry at present.
[23:46] <guiverc_d> thanks again ~
[23:46] <guiverc_d> s/~/!]