=== ilasc changed the topic of #launchpad to: Help contact: ilasc (05:00-14:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [07:17] wow lots of disabled builders today... [07:17] and cleaning/stuck... [07:28] heya - what's the process to get a new remote bug tracker added to launchpad? === ilasc changed the topic of #launchpad to: Help contact: ilasc - Builders stuck, we're investigating (05:00-14:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad === ilasc changed the topic of #launchpad to: Help contact: ilasc (05:00-14:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [09:23] LocutusOfBorg: should be fixed now [09:23] icey: does this help https://help.launchpad.net/Bugs/InterBugTracking#lp-plugins ? === ilasc changed the topic of #launchpad to: Help contact: ilasc - away (lunch) (05:00-14:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [09:27] ilasc: well, it confirms for me that storyboard isn't supported, but doesn't suggest an approach to add that support (eg: https://storyboard.openstack.org/#!/story/2008116) [09:33] icey: One writes a bunch of code; not sure what more to say than that :) [09:34] cjwatson: any guidance on that? example? wiki page? [09:35] cjwatson: not sure I'll ever get the time to do it but more and more OpenStack projects are moving their bug tracking from Launchpad to storyboard so it would be quite nice to get that integrated at some point [09:35] icey: The existing support is in lib/lp/bugs/externalbugtracker/ [09:35] what does "binaries conflicting with the existing ones" mean when copying? I was trying to demote haveged in groovy and resurrect the previous version but I can't do the copy-back because of that error [09:35] maybe I need to actually remove from groovy-proposed completely [09:36] icey: (mostly; there are some bits of bug tracker support elsewhere under lib/lp/bugs/) [09:37] cjwatson: i'll take a look [09:37] Laney: Did you remember --include-binaries? [09:37] (and try to figure out how to launchpad dev :-P ) [09:37] cjwatson: yeah [09:38] Laney: Deleting won't help [09:38] https://paste.ubuntu.com/p/mfVyRpxnbh/ [09:40] Laney: Did you really mean 1.9.1-6ubuntu1 and not 1.9.8-4ubuntu1? [09:40] cjwatson: I did, that's the version that was previously in groovy [09:40] we discovered that 1.9.8 is broken [09:42] It's possible this is one of the cases where there's confusion due to changes in the set of architectures to be published [09:45] cjwatson: Oho, --from-suite=focal worked [09:48] That's stranger than I was expecting. But OK [09:51] I thought that I'd try a suite where the binaries are still published, but I still don't understand what the message means :) [10:01] Generally speaking it means that the copy doesn't include all the architectures for which binaries already exist in that archive, so when you do the copy it would result in creating fresh builds for those architectures which would conflict with the binaries that already exist. I don't understand why it's saying that in this case though [10:03] icey: in practice, were I doing it, I'd start by using one of the more recently-written external bug trackers as an example (github is the most recent IIRC) and go from there. Hopefully storyboard has some kind of decent API [10:06] cjwatson: storyboard seems to be 100% fancy modern APi based frontend thingy, so I'm hopeful :-P [10:21] ilasc or cjwatson: is https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4212/+build/19921256 interesting to you or should I just mash the button? [10:23] Laney: libreoffice is libreoffice so it may have killed the builder or something (e.g. ENOSPC). But in such cases, as long as the build farm generally looks operational, there's not much harm in retrying other than using some resources; it won't lose any information that hasn't already been lost [10:24] alright, thanks, I'll bear that in mind === ilasc changed the topic of #launchpad to: Help contact: ilasc (05:00-14:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad === ilasc changed the topic of #launchpad to: Help contact: ilasc - EOD (05:00-14:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad [14:48] would it be possible to increase the size of my libreoffice ppa? it's such a monster and it would be ideal if this ppa could hold like 5 different builds: https://launchpad.net/~hellsworth/+archive/ubuntu/libreoffice/+packages [14:48] I am requesting 50G [14:51] hellsworth: could you please request it using the support link in the topic? [14:51] ah perfect thank you [14:51] 50G may be a problem; we have somewhat limited space at the moment and that's a substantial fraction of it [14:51] topics are so often ignored.. [14:52] hmm my ppa is currently 10G.. maybe i could get that to 20G then instead of 50 [14:52] but request link it is [14:52] 50G is about 8% of our remaining space [14:52] Hopefully that'll be fixed soonish, but for now ... [14:52] when is soonish? :) [14:52] Out of our hands, depends on IS [14:52] a week? a month? [14:52] ok [14:52] I expect we can bump your PPA a bit though [14:54] hellsworth: It's https://portal.admin.canonical.com/C126718 if you want a peek at the internet ticket [14:54] *internal ticket [14:55] (Some space has been freed so the situation is a bit less dire than indicated in the latest reply to that ticket) [14:57] cjwatson: ok i posted a question to answers.launchpad.net. thanks [14:59] cheers [15:09] hellsworth: Hm, that PPA seems to be 20G already? Unless I'm racing with one of my colleagues ... [15:09] ah shoot my bad it is 20G.. can i have just a tad bit more please :) [15:10] what's an extra 10G between friends :) [15:10] hellsworth: Bumped to 32G [15:10] :D [15:10] thank you so much cjwatson [15:10] no trouble [15:11] just wanted to make sure I was looking at the right one :) [15:12] you were.. i should have looked rather than going off memory [15:12] how long does it take to delete things from a ppa? [15:12] last i asked it was 10hr. is that still the case? [15:14] it sort of depends what you mean; do you mean for purposes of quota calculation? [15:15] (deletions from the published archive on disk are much faster than that) [15:16] IIRC quota calculation relies on a six-hourly cron job, so it could be anything from minutes to six hours or so depending on where you fall in the cycle [15:16] oh for PS5 when we might be able to revamp this ... [15:17] oh i mean for deleting build artifacts and tarballs from a ppa.. how long until that space is free for me to push new tarballs and launch a new build to use that newly freed space [15:18] hellsworth: if memory serves that's the six-hourly cron job [15:19] okey dokey thanks