[00:17] <cjwatson> mwhudson: afraid not - it would probably be a good thing to have, though I'd suggest ubuntu-dev-tools rather than ubuntu-archive-tools
[11:15] <Odd_Bloke> wgrant: cjwatson: Could someone bump the priority of https://launchpad.net/~daniel-thewatkins/+livefs/ubuntu/xenial/cpc/+build/48541 for me?
[11:15] <Odd_Bloke> (And could you remind me who can do that, so I can ping the right people in future?)
[11:17] <xnox> Odd_Bloke, well, looking at https://launchpad.net/builders and https://launchpad.net/ubuntu/xenial/+builds?build_text=&build_state=pending&arch_tag=s390x
[11:17] <xnox> it's simply a bunch of haskell stuff building.
[11:18] <xnox> and should be done quickly-ish. About 4 or 5 builds per builder left. Is not much.
[11:20] <Odd_Bloke> xnox: Every refresh of the build page has increased the 'Start in' time, so I suspected that something was queueing new builds which were all taking priority.  But if that's not the case, then I don't mind waiting.
[11:20] <wgrant> Odd_Bloke: Done.
[11:20] <Odd_Bloke> wgrant: Danke.
[11:21] <wgrant> Odd_Bloke: It's best to poke me or Colin, or WebOps if neither of us are around and it's critical.
[11:21] <xnox> Odd_Bloke, that "something" probably was archive auto sync =) and you can blame debian people for uploading haskell =)
[11:22] <Odd_Bloke> I would send a strongly worded complaint if I could work out how to use the IO monad to send email. ;)
[11:30] <xnox> Odd_Bloke, mark@ubuntu.com ;-)
[11:41] <Odd_Bloke> ^_^
[12:37] <xnox> Odd_Bloke, it's done \o/
[12:38] <xnox> Odd_Bloke, but there is no -lxd.tar.gz ?!
[12:38]  * xnox is downloading the lot at the moment.
[12:40] <Odd_Bloke> xnox: Ah, no, -lxd.tar.gz is produced in our build system (because it requires us to include information that is difficult to pass through to the buildds).
[12:41] <xnox> Odd_Bloke, ah, ok. So i guess copy this over to private file share, or i can do that. Whichever.
[12:41] <xnox> Odd_Bloke, but could you run the by-products through to make -lxd.tar.gz?
[12:41] <Odd_Bloke> Oh, sigh, can't download from LP directly from private-fileshare.
[12:41] <xnox> and then create simple stream, and have that all on the private file share?
[12:41] <Odd_Bloke> xnox: Creating simple streams is far from simple.
[12:42] <xnox> Odd_Bloke, >_<
[12:42] <Odd_Bloke> xnox: And private-fileshare uses OpenID, so it's pretty much impossible to use with a script.
[12:42] <xnox> horum.
[12:42] <xnox> in that case private-fileshare is no good.
[12:42] <Odd_Bloke> Well, it's fine for me pointing people at files for testing purposes.
[12:43] <Odd_Bloke> But it's no good for delivery, certainly.
[12:43] <xnox> is it really openid?! even when connected to vpn?
[12:43]  * xnox goes to try to find private file share docs
[12:43] <Odd_Bloke> Oh, hm, I'm not connected to the VPN so I don't know.
[12:44] <Odd_Bloke> xnox: Yeah, I'm connected to the VPN and attempting to access from a private session redirects to login.ubuntu.com.
[12:45] <xnox> =(
[12:47] <mgz> use lillypilly?
[12:48] <xnox> mgz, no..... we want something behind the vpn, without oauth.
[12:48] <xnox> people.canonical.com is public.
[12:51] <mgz> hm, but need better than no one is looking for the url auth?
[15:45] <DrunkenDwarf> Hi all. Hoping someone can help, im trying to clean up my packaging and distrobution so my first time working with PPAs, ive built a source package and dput it to my ppa, but in the launchpad page it still says my ppa does not contain any packages. there were no errors in pushing, the output is here: http://pastebin.com/EA92dUrP ... not quite sure why its not showing up
[15:49] <cjwatson> DrunkenDwarf: Our system sent you an automatic rejection email; can you please check for it?
[15:50] <cjwatson> (check spam folders, etc.)
[15:50] <DrunkenDwarf> ahhhh. that literally just pinged through to my phone. thanks ... hmmm
[15:52] <cjwatson> we need to know what release of Ubuntu to build this package for; current supported releases are precise, trusty, vivid, wily, and xenial.  no such release as "STABLE"
[15:53] <DrunkenDwarf> ahhhh. thats for the Ubuntu release. .. i see. thought it was the package release as many tutorials showed "UNSTABLE" being an option.... thankyou, ill fix that
[15:53] <cjwatson> It would be lower-case "unstable"; but that refers to Debian unstable
[15:54] <DrunkenDwarf> i see. that makes sense
[15:54] <cjwatson> which is the sort-of-a-release where new packages are uploaded
[17:04] <dobey> hmm, seems a lot of the x86 builders are offline. something with prodstack?
[17:06] <cjwatson> We've had a lot of reliability problems lately; poked as a temporary measure
[17:06] <cjwatson> (I should finish this enormous branch rather than digging into it)
[17:07] <dobey> ah ok
[17:07] <cjwatson> (Probably not prodstack; builders are in scalingstack, which is several separate clouds.  They do have a bit of exposure to prodstack problems but this is probably not that.)
[17:08] <dobey> oh right
[18:58] <wxl> am i reading correctly that github is not supported as a remote tracker? https://help.launchpad.net/Bugs/RemoteTrackerCoverage
[19:00] <dobey> did github even have issues yet, 7 years ago?
[19:00] <dobey> (because that's when that wiki page was last updated) :)
[19:00] <cjwatson> wxl: Afraid so.  https://bugs.launchpad.net/launchpad/+bug/848666
[19:01] <cjwatson> It needs explicit modelling of the remote issue tracker and how to slurp information from it; not ridiculously hard but a little too big a task to be just slotted in round the edges
[19:01] <dobey> cjwatson: could we get someone to update that wiki page a bit (i would but i don't know the actual statuses), as Google Code is at least no more afaik
[19:02] <wxl> right right. well i'll subscribe to the bug and see what happens in the future. i will admit that most of lxde's development has moved to github, so for lubuntu, especially with lxqt on the horizon, i'd say that's an important addition, but not like we can't work around it.
[19:03] <cjwatson> dobey: Wouldn't be a bad idea, but I really don't know the external bug tracker stuff very well myself.  wgrant might.
[19:04] <dobey> yeah, github issues will probably be even more useful when all the other git work gets finished up
[19:04] <dobey> cjwatson: sure. :)
[19:06] <cjwatson> I think it may just be a matter of removing google code; it's a while since there was much other development on external trackers ...
[19:06] <cjwatson> at least at that sort of basic level
[19:07] <cjwatson> github issues would be useful in combination with git imports, indeed
[19:07] <dobey> cjwatson: maybe add a column for github as well, with a link to the bug report?
[19:07] <cjwatson> good idea, let me do that much at least
[19:08] <dobey> cjwatson: cool, thanks. that should at least make it easier for people to see the status when they are curious and end up on that page
[19:10] <cjwatson> r8330 is a good example of how to do simple linking support, though
[19:10] <cjwatson> posting here mostly for reference in case somebody fancies trying github issue linking based on that
[19:10] <cjwatson> (there are several levels of possible support here)
[19:14] <cjwatson> added a column to the wiki
[19:17] <dobey> cool