[16:37] <ricotz> hello, looks like the PPA publishing cycles changed quite a bit, what are they currently set to?
[16:48] <cjwatson> ricotz: They have not changed in years.
[16:49] <cjwatson> ricotz: The cron job tries to run every minute.  How often it actually manages that depends entirely on how much work it has to do.
[16:49] <cjwatson> ricotz: Er, sorry, every five minutes.
[16:49] <cjwatson> 2,7,12,17,22,27,32,37,42,47,52,57  * * * *
[16:51] <ricotz> cjwatson, I see, it feels to take approx. the double amount of time, e.g. like 1 hour to publish binaries
[16:52] <ricotz> (doubled compared to past times)
[16:52] <cjwatson> The general load may have gone up, but it's not because of cycle timing.
[16:53] <ricotz> alright, thanks
[16:53] <cjwatson> I agree it seems to be roughly two runs per hour at the moment on average.
[16:53] <cjwatson> Depending a bit on time of day.
[16:54] <cjwatson> I've done optimisation work on this in the past, but it tends to be more like "death by a thousand cuts" than any one thing.
[17:23] <chrisccoulson> What's happened to the chromium packages in https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/ ? Launchpad says they are "Pending", yet they're published in http://ppa.launchpad.net/canonical-chromium-builds/stage/ubuntu/
[17:26] <cjwatson> There was an OOPS during publication, apparently because you've managed to ask it to publish multiple different source packages with the same versions.
[17:26] <cjwatson> 2016-06-30 17:17:12 DEBUG   /srv/launchpad.net/ppa-archive/canonical-chromium-builds/stage/ubuntu/pool/main/c/chromium-browser/chromium-browser_51.0.2704.79-0ubuntu0.12.04.1.998.dsc is already in pool with the same content.
[17:26] <cjwatson> 2016-06-30 17:17:12 DEBUG   /srv/launchpad.net/ppa-archive/canonical-chromium-builds/stage/ubuntu/pool/main/c/chromium-browser/chromium-browser_51.0.2704.79-0ubuntu0.12.04.1.998.debian.tar.xz is already in pool with the same content.
[17:26] <cjwatson> 2016-06-30 17:17:16 ERROR   PoolFileOverwriteError: 875f63c4edcceadfa0b0acb4e07947344fedbc30 != 09a517d82f2942b507dc609d33cc40a888fb021f for /srv/launchpad.net/ppa-archive/canonical-chromium-builds/stage/ubuntu/pool/main/c/chromium-browse
[17:26] <cjwatson> r/chromium-browser_51.0.2704.79.orig.tar.xz, skipping. (OOPS-b6dbc439b2daac6b1a04383626f57d29)
[17:26] <cjwatson> And several other similar ones
[17:27] <chrisccoulson> oh, chad isn't in here
[17:29] <chrisccoulson> cjwatson, thanks. I'll let chad know (they're his uploads, I just want to publish them)
[17:29] <cjwatson> Hm.  I wonder if there was a truncation bug or something
[17:29] <cjwatson> Let me have a quick poke
[17:32] <cjwatson> chrisccoulson: I'll fix it later, need to go for dinner now.  Not your problem
[17:32] <chrisccoulson> cjwatson, thanks
[17:32] <cjwatson> File's truncated on disk due to a bug that's (at least in part) now fixed
[18:17] <Prottey> Hi. I'm behind a HTTP proxy, and it seems dput doesn't support proxy settings yet. Is there any alternative way to upload to PPA?
[18:37] <cjwatson> Prottey: Well, an HTTP proxy isn't going to help much with FTP
[18:37] <cjwatson> Prottey: You can use SFTP though, and you may be able to tunnel that through a proxy (e.g. using corkscrew)
[18:37] <Prottey> it has support for CONNECT method, yeah
[18:37] <cjwatson> Prottey: https://help.launchpad.net/Packaging/PPA/Uploading
[18:38] <Prottey> do I have to make SSH keys to upload via SFTP?
[18:38] <Prottey> and register them?
[18:41] <cjwatson> Yes
[18:41] <cjwatson> Should be a fairly quick job though
[18:52] <Prottey> btw I already managed to manually upload everithing over FTP via curl :P
[18:53] <Prottey> s/everi/every/
[18:53] <cjwatson> Heh, OK.
[18:53] <Prottey> they should make dput honor http_proxy though
[18:55] <cjwatson> /usr/share/doc/dput/TODO:3. Support ftp-over-http for ftp proxy users