[00:32] <kyrofa> I'm getting 407 proxy auth issues in my snap builders: https://launchpadlibrarian.net/298271931/buildlog_snap_ubuntu_xenial_arm64_nextcloud-edge_BUILDING.txt.gz
[00:33] <wgrant> kyrofa: Hm, it took a rather long time, so the token probably expired.
[00:33] <wgrant> kyrofa: Does it normally take that long?
[00:33] <wgrant> It's possible it's running into the prodstack network issue.
[00:34] <kyrofa> wgrant, hmm, no, indeed
[00:35] <kyrofa> wgrant, but I just hit it with arm64, ppc64el, and armhf
[00:38] <wgrant> kyrofa: Ah, so all the US architectures. So two network performance problems. Are you blocked, or could you wait a couple of hours and try again to see if it's magically resolved?
[00:38] <kyrofa> wgrant, definitely not blocked, just wanted to report the issue :)
[00:39] <kyrofa> wgrant, daily builds not happening for a day won't hurt anyone
[00:39] <wgrant> kyrofa: Great. Let me know if it's still a problem later -- the main transatlantic link occasionally runs into some trouble.
[00:39] <kyrofa> wgrant, will do, thanks!
[03:46] <austin987> I assume this channel is just for launchpad code development? is there any irc launchpad support, or only on a browser?
[03:47] <wgrant> austin987: This is the support channel.
[03:48] <austin987> wgrant, oh, great!
[03:49] <austin987> wgrant, so, for context, I maintain winetricks, and a user filed a bug asking to fix the launchpad code link from google code to github
[03:50] <wgrant> I see you've registered a new import.
[03:50] <austin987> the previous maintainer set that up, he gave me access to LP. I updated what I could, but I can't seem to figure out how to a branch that pulls from github master (previously it was svn on googlecode, with a trunk master)
[03:51] <austin987> it feels a bit like git-svn, where I'm not sure when I should use git or bzr/lp branches/repos
[03:51] <austin987> yes, tried a few things
[03:52] <wgrant> https://code.launchpad.net/winetricks looks right -- it shows the imported repository. What it's missing is the bit linking to GitHub, which you can't see unless you drill down the repository itself. Does that match your understanding?
[03:53] <austin987> what do you mean by drill down the repository?
[03:54] <austin987> that does look right to me, looks like last try I got it right :)
[03:54] <austin987> I'll have to ask user to confirm still
[03:54] <wgrant> Er, drill down to it, rather. https://code.launchpad.net/winetricks displays much of the same information that https://code.launchpad.net/~winetricks-team/winetricks/+git/winetricks does, but not all of it -- notably the link to the source on GitHub is missing.
[03:54] <austin987> thanks for response / trying anyway
[03:54] <austin987> should there be a link generated by lp?
[03:54] <austin987> i.e., did I miss something to configure?
[03:56] <austin987> https://launchpad.net/winetricks/master shows no linked branch, however
[03:56] <austin987> if I click link it, it asks me to either link to one on launchpad, but if I search for 'winetricks' I get nothing, or I can import a git repo again
[03:57] <wgrant> Oh, when I say it's missing, I mean it's missing from our templates :)
[03:57] <wgrant> It's not a bug in your configuration -- you've done all you can.
[03:57] <wgrant> We just haven't totally integrated the git import details (a new feature) into the project code homepage.
[03:57] <austin987> ah, kk
[03:58] <wgrant> I don't know of an existing bug, but if you can file one at https://launchpad.net/launchpad/+filebug it'll be on the list for the next round of git UI tweaks.
[03:58] <wgrant> austin987: The https://launchpad.net/winetricks/master bug is already filed, but I forget the number. We will probably hide that section of the page for Git.
[03:58] <austin987> wgrant, okay, thanks
[03:59] <austin987> if you find it later and I'm still around, please send me the link
[04:00] <austin987> wgrant, any tags on the link bug?
[04:01] <wgrant> austin987: Not at this stage -- we'll add them.
[04:01] <austin987> wgrant, https://bugs.launchpad.net/launchpad/+bug/1650109
[04:01] <ubot5`> Ubuntu bug 1650109 in Launchpad itself "Provide a link to imported git projects original source" [Undecided,New]
[04:02] <wgrant> austin987: Thanks.
[04:03] <austin987> np
[04:03] <austin987> thank you
[13:08] <pevma> hi, I searched the net a bit but was not sure if it is possible (and how) to request to enable s390x and PowerPC processor arch pkg building? (it says: "Some architectures are restricted and may only be enabled or disabled by administrators.")
[13:09] <cjwatson> pevma: https://answers.launchpad.net/launchpad/+addquestion
[13:10] <pevma> thank you
[13:10] <cjwatson> pevma: but it's only permitted for Canonical employees
[13:10] <pevma> aha
[13:10] <pevma> ok
[13:10] <pevma> that answered my question  :)
[13:10] <cjwatson> pevma: so if you're not one then I'm afraid we have to say no, because we don't have good enough sandboxing on those architectures yet
[13:10] <pevma> understood... i am not
[13:10] <cjwatson> when we do then it will be allowed
[13:11] <pevma> ok thanks -  any ETA
[13:11] <pevma> ?
[13:11] <cjwatson> needs deployment of a new cloud first
[13:11] <cjwatson> don't have a specific ETA as yet but s390x at least will hopefully be fairly soon
[13:12] <cjwatson> powerpc will be best-effort I guess, given https://lists.ubuntu.com/archives/technical-board/2016-December/002274.html
[13:12] <cjwatson> though it may still be worth it for supporting stable releases
[13:12] <xnox> pevma, note that ppc64el should be available as self service (at least i was under impression that it has become a generally available arch)
[13:13] <pevma> understood
[13:13] <pevma> thanks cjwatson
[13:13] <cjwatson> ppc64el is self-service, yes
[13:13] <pevma> xnox: yes ppc64el i have enabled ya
[13:19] <pevma> i have one more question  :) -
[13:19] <pevma> i have a package that i need to have enabled in /etc/pbuilderrc - > "USENETWORK=yes" during build because of pip version dependencies ...
[13:19] <pevma> What is the best way to do that (if possible) in PPA. I am guessing using the rules file?
[13:19] <cjwatson> There's no way to do that
[13:19] <pevma> understood
[13:19] <pevma> thanks
[13:19] <cjwatson> You need to package the pip dependencies in question as packages you can build-depend on, or (if absolutely necessary) bundle them
[13:20] <pevma> i can try looking into that yes
[13:20] <pevma> good idea
[16:24] <tvansteenburgh> wgrant: this is still happening consistently: OOPS-bf417f9b83b1c83c27395d1e77e44b40
[16:24] <ubot5`> https://oops.canonical.com/?oopsid=OOPS-bf417f9b83b1c83c27395d1e77e44b40
[16:25] <tvansteenburgh> wgrant: should i file a bug somewhere?
[20:52] <wgrant> tvansteenburgh: Yep, please file a bug at https://launchpad.net/launchpad/+filebug, including the OOPS ID.
[21:11] <Fyre> hello?
[21:58] <cjwatson> Some cronned services will be stopped half an hour or so beforehand, so e.g. PPA publishing, builds, etc. will be delayed somewhat.
[21:59] <teward> eesh that means I only have an hour to upload nginx o.O
[22:00] <cjwatson> teward: Uploads will generally be queued, unless they hit one of the short intervals when a firewall is actually being replaced.
[22:00] <cjwatson> teward: But they'll either just obviously fail or be queued, at any rate.
[22:00] <teward> indeed.
[22:00] <DLange> gee, application not available due to firewall maintenance ... the 90s are calling, cjwatson :)
[22:01] <teward> cjwatson: though i've just got the upload in now, so hopefully it gets built :)
[22:02] <cjwatson> DLange: Only so much you can do when the route to your database goes away ;-)
[22:03] <DLange> yeah, everybody can have redundant paths ... where's the fun in doing that? :)
[22:05] <cjwatson> Not something I have any control over, I'm afraid
[22:08] <DLange> yeah, good luck with seeing your DB again in ~two hours and getting to sleep at a reasonable time!
[22:10] <cjwatson> "intermittently"
[22:10] <cjwatson> the actual outages should only be a minute or so, that's just the total slot sysadmins have allocated for the whole lot
[22:12] <teward> cjwatson: i guess I'm lucky - my upload got in, and built already it seems xD
[22:12] <cjwatson> (also, I'm just doing initial communication, I've no intention of staying up for it)
[22:13] <wgrant> I'll be here, though.
[22:16] <DLange> well, nn cjwatson and good luck wgrant then :)
[22:16]  * DLange is off for the night, too
[22:29] <sergio-br2> uh, wily builds no more, but vivid yes?
[22:29] <dobey> sergio-br2: wily is EOL; vivid is still weird special child because of phone, but is EOL otherwise
[22:29] <dobey> sergio-br2: you should not be building stuff on vivid generally
[22:30] <sergio-br2> ah, ubuntu phone
[22:30] <sergio-br2> humm
[22:30] <sergio-br2> should I disable vivid in my PPAs then?
[22:30] <dobey> yes, i would say so
[22:30] <wgrant> Yes.
[22:31] <sergio-br2> the thing is, you always find users using old ubuntu
[22:31] <dobey> doesn't mean they are supported
[22:46] <sergio-br2> there should be an option to disable a release in the ppa or recipes massively
[22:46] <sergio-br2> the libretro ppa has something like 70 or more recipes T.T
[22:48] <wgrant> sergio-br2: You can use an API script to do that easily.
[23:01] <sergio-br2> really?
[23:01] <sergio-br2> launchpadlib ?