[00:00] That might explain why I'm having such a hell of a time finding armhf binaries in general, but the board is based around Ubuntu 14.04 and 16.04 has show stoppers that prohibit a release upgrade [00:04] nacc, Fuzai: That changed a few months ago; the PPA's owner can switch on armhf builds themselves. [00:04] New uploads will then automatically build on armhf too. [00:05] Hmm [00:05] wgrant: ah ok, i guess i haven't looked since then, thanks! [00:05] (in the interim, you could create your own PPA, enable armhf, and copy the packages over to get binaries) [00:05] is there a way to clone a ppa? [00:05] Fuzai: --^ that's what i was suggested earlier [00:05] Fuzai: you'd copy the packages ppa -> ppa [00:06] Ok, letme see what Google has to say about that [00:06] Fuzai: https://help.launchpad.net/Packaging/PPA/Copying [00:06] ty [02:42] wgrant: is ppa publication particularly slow today? [02:43] have something unpublished after nearly an hour [03:31] mwhudson: Has it published yet? [03:43] wgrant: yeah [03:44] Odd. [04:19] Hello [04:20] this is a good time for australia right? [04:20] Yep, I'm here. [04:20] hey wgrant! :) [04:20] one of our builds in the PPA failed to contact localhost compalining about something proxy: https://launchpadlibrarian.net/263232324/buildlog_ubuntu-xenial-amd64.snapcraft_2.9~1_BUILDING.txt.gz [04:20] another build worked: https://launchpadlibrarian.net/263239501/buildlog_ubuntu-xenial-amd64.snapcraft_2.9~ppa1-1_BUILDING.txt.gz [04:21] it's the same code, so I'm not sure if there's something for me to fix, or there's something wrong in the first builder. [04:21] This is the error: Max retries exceeded with url: http://localhost:58220/dev/api/acl/ (Caused by ProxyError('Cannot connect to proxy.' [04:22] elopio: That's something in the snapcraft test suite. [04:22] The builders have no proxies. [04:22] I suspect the test suite uses an internal thing to emulate the SCA API. [04:22] And that failed to start, or something like that. [04:24] wgrant: yes, we start many local servers. I see no error there, but it could be hidden. [04:25] elopio: I suspect that is the case. There's no LP proxy for binary package builds, so it can't be proxy. [04:25] it sounds unlikely that all the servers failed to start in all the tests in the first branch, but they all worked in the second. Hum, I'll make more runs. [04:25] ... [04:25] so it can't be *broken* [04:27] elopio: You should probably check that you're not suppressing stderr somewhere, I guess. [06:43] hey, I accidentally pushed a build (intented for xenial) for trusty, which failed because of deps. I removed the failed build/package, however the older successful is now marked superceeded [06:44] is there a way to re-instate the old build? [06:46] pmjdebruijn: Delete the wrong one, and copy the right one back in (make sure to change the "Published" filter to "Superseded" on +copy-packages) [06:49] I already removed the wrong one [06:49] I'll try the copy action tonight, thanks === FourDollars_ is now known as FourDollars === lfaraone_ is now known as lfaraone === demonimin_ is now known as demonimin === \b is now known as benonsoftware [10:14] is there any way to unsubscribe from emails about pull requests for a specific project or team? [10:15] sorry, merge proposals === Saviq_ is now known as Saviq [10:18] Is something sad happening with the librarian? I've been getting 5xx errors when trying to run auto-sync manually. [10:22] Laney: can you paste more complete details? [10:22] cjwatson: I made it put a traceback in the log for the last one - one second [10:23] cjwatson: http://people.canonical.com/~ubuntu-archive/auto-sync/2016-06-03/10:10:24.log [10:23] The other two times were a 500 and a 502 on some other .dscs [10:23] I'm afraid I closed that tab though :( [10:29] Can't see signs of badness in the logs - must be at the haproxy level I guess [10:32] I think we just have to have auto-sync back off and retry [10:32] Let me have a go at that [10:33] Yeah I'm sure that would fix it, if such errors are to be expected [10:41] Laney: ok, try now [10:44] alright, it's running === JanC is now known as Guest27710 === JanC_ is now known as JanC [17:17] i wonder whether this is a spam account or just a boring/annoying child playing around. https://launchpad.net/~sunnohello [17:17] and https://launchpad.net/~sunnohello123 by extension- [17:23] spammy pattern but I'm at EOD, hopefully wgrant can deal with it [19:19] There's a bunch of firefox arm64 builds that all seem to be stuck [19:20] https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/9851597 [19:20] https://launchpad.net/ubuntu/+source/firefox/47.0+build1-0ubuntu1/+build/9851466 [19:20] https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/9851633 [19:21] Oh, I can cancel them all [20:45] Hi folks. Is this an appropriate place to ask about login problems? The single sign on won't allow me to log into my account (rleigh); it still thinks I have a debian email address despite having changed it. But I no longer have a debian account, so can't log in at all... [20:46] I did try filling out a support request a few months back, but never got any response.