[03:40] how long does it typically take for packages to be published to ppas after building? [04:07] teward: 5-10 minutes [08:16] Hi folks. I can't subscribe to a mailing list, because LP is timing out on me. Any pointers? Error ID: OOPS-d0ebcf5d853707cd9f623aa778b26324 [08:16] https://oops.canonical.com/?oopsid=OOPS-d0ebcf5d853707cd9f623aa778b26324 [08:36] aloha, is there a way to find out if a package has been fully published through the API? [08:38] what is "fully published" for you? [08:40] all binaries of all succesfully built builds of all published sources of all done uploads are published (available in the archive repo in question) [08:40] I actually have everything but the binary part figured out [08:41] have you checked the status field of the binary_package_publishing_history object? [08:42] yep [08:42] I can actualy show you the entire gloriously crappy code, sec ^^ [08:43] http://paste.ubuntu.com/8471508/ line 94 onwards is the intersting bits [08:44] so, I thought I could use source_pub_history.getPublishedBinaries (line 156) but as it turns out that will not cover all potential binaries that will need publishing [08:45] namely if i386 finished a bit after amd64 but not quite close enough the source_pub will be published, the build_pubs will be published and all (known) binaries will be published and programatically it is as though i386 never created any binaries at all [08:46] related output from the pasted script when exactly this happened tonight: http://paste.ubuntu.com/8471521/ [08:51] hmm, is the output still wrong when you rerun the script for that upload now? [08:54] geser: nope it's correct now [08:57] it appears to me that there is a time gap between buildstate reaching 'successfully built' and its binaries appearing in getPublishedBinaries(), that's also where line 154 comes from. there is a chance that one can have everything indicate that the build is done but getPublishedBinaries() returns nothing yet [09:03] There is a gap, yes. The web UI uses getBuildSummariesForSourceIds. [09:07] apachelogger: could you use some wait after build.datebuilt before calling source.getPublishedBinaries()? (if wgrant call tell you how big the gap is) [09:09] There's no reliable gap [09:10] For very bad historical reasons, binaries only show up in getPublishedBinaries once the publisher starts. [09:10] hm [09:11] * apachelogger takes a look at getBuildSummariesForSourceIds [09:11] getBuildSummariesForSourceIds takes the PackageUpload status into account. [09:11] It's what powers the right column on a PPA's +packages page. [09:11] Which shows when builds are in progress, or publishing, or all done. [09:16] wgrant: that sounds like what I need [09:16] geser, wgrant: thanks I'll give this a try :) [09:56] Hi guys, I get a 403 response code when I try to download a package from a VPS Server hosted on Glesys (Swedish hosting company): wget http://ppa.launchpad.net/iacobs/redis/ubuntu/pool/main/r/redis/redis-server_2.8.14-0~ppa3_amd64.deb --2014-10-01 13:55:31-- http://ppa.launchpad.net/iacobs/redis/ubuntu/pool/main/r/redis/redis-server_2.8.14-0~ppa3_amd64.deb Resolving ppa.launchpad.net (ppa.launchpad.net)... ::ffff:108.166.117.240 [09:57] is the host blacklisted or something? the provider does not filter any traffic [09:57] or how can I proceed to find out what can I go from here [09:58] florinel: Have you tried using native IPv4? === karni is now known as karni-otp [09:59] wgrant: good point, no, trying it now. [10:02] wgrant: damn, that worked. Thank you. [10:02] florinel: I'm not quite sure why what you tried didn't work. Do you have some strange networking setup? [10:09] wgrant: I am starting to look into it, why would it behave like this. === karni-otp is now known as karni === karni is now known as karni-lunch [13:07] wgrant: is it possible the builders last night were lagging with uploads? Had to wait 25 mins after building for it to publish === karni-lunch is now known as karni [14:00] Am I in the right place for a cloud-init question? [14:02] I wanted to know if fs_setup needs to be explicity set in the cloud.cfg modules list in order to declare it in my user-data [14:03] you probably want to ask in #ubuntu-server perhaps? or #juju (if that's a channel)? [14:05] ok thanks, I will give that a try [14:17] teward: there was an incident where a libvirt upgrade took out the networking on the virtualised builders, yes [14:17] don't know whether that would have affected built -> published === mpt_ is now known as mpt === lan3y is now known as Laney === Pici` is now known as Pici [16:45] cjwatson: ok, thanks for the heads up on that, was that all fixed? [16:45] so I'm told [17:01] hello [17:02] I'm getting "Sorry, there was a problem connecting to the Launchpad server." when trying to load https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/20-sm/+merge/236750 [17:02] is there a known problem? [17:02] now I get: [17:02] 504 Gateway Time-out [17:02] The server didn't respond in time. [17:02] t1mp, I have the same error [17:03] everything else works though, just the merge interface seems broken [17:08] Hello. Yes, I only call when I want something. I’m getting lots of timeouts looking at code. For example https://code.launchpad.net/~newell-jensen/maas/pxe-requests/+merge/236368 ends in “Please try again” consistently, for about 5-10 minutes now. [17:17] cprov: Hi Celso, do you look after Launchpad these days? I’m having timeout issues, and so are a few others. ^ [17:19] both those pages loaded first time for me FWIW [17:19] I expect wgrant will want the OOPS ID from the timeout [17:20] allenap: it worked for me too, temporary hiccup, maybe [17:21] cprov, cjwatson: Yes, it’s working again for me too. Sorry for the noise. Unfortunately I didn’t write down the OOPS number :-/ [17:26] allenap: it will show up in the reports, if it's working still. I will take a look later [17:26] cprov: Ta, thank you. [19:11] When I attempt to load a merge proposal at this link https://code.launchpad.net/~sethj/ubuntu-packaging-guide/lp1313053/+merge/236766 I get "Please try again Sorry, there was a problem connecting to the Launchpad server" and asking I let people know here. So here I am :) [19:11] FWIW I tried reloading the page several times, but it always terminates at the same error. [21:29] hi guys, a thing. For the debs in ubuntu, on the launchpad like https://launchpad.net/ubuntu/+source/empathy, I find a debian.tar.xz tarball under the package details, and this tarball contains the debian directory that is used by the debian packaging tools to package the software into a deb package [21:29] now, I can't find a debian.tar.xz for linux :D [21:29] where I can find it ? [21:30] *can I [21:40] someone? [21:41] mibofra: looks like the linux package in ubuntu is not using the debian source format 3.0, but the 1.0, so you don't have a debian.tar.. instead the linux package in debian does, if you want it. [21:46] thanks mapreri [21:47] yw