[00:33] <mjog> Hey all, is something up with uploading packages to PPAs?
[00:34] <mjog> I'm trying to upload using dput to ppa:geary-team/releases and it's silent failing - no email, no change on the PPA
[00:35] <mjog> the sources seem to be getting signed okay, and the gpg key is on my account for launchpad
[00:35] <mjog> this worked at the end of last year, the only thing I know of that changed is the source release I'm trying to make
[00:47] <nacc> mjog: as in you're trying to build for zesty or artful?
[00:48] <mjog> nacc: uploading for trusty xenial and zesty, all are failing
[00:50] <nacc> mjog: a couple of weeks ok, per my logs, cjwatson said that there can be silent failures if your key has expired on the server
[00:50] <nacc> mjog: is it possible your gpg key is expired?
[00:50] <nacc> miika: was the one who hit that on sep 23
[00:51] <mjog> nacc: haha, yeah of course it has expired, thanks!
[00:51]  * mjog puts on a brown paper bag
[00:51] <nacc> mjog: np, glad that was it (well, glad that you have an easy fix)
[00:52] <nacc> mjog: it's a bug in LP that it's silent, but it sounds like a fix will be there for that eventually
[00:53] <mjog> Cool. Seahorse didn't make it very obvious it had  expired, either, so hey.
[05:51] <riking> I need to reset my 2FA devices
[05:52] <riking> The page mentions the "#isd" and "#webops" channels, but I have no clue what server that's on.
[05:53] <riking> Because it's not freenode. https://login.launchpad.net/ shows "sites you last authenticated to", top of the list is https://launchpad.net/	2016/08/09
[05:53] <riking> oh, I still have one of the ssh keys on the account.
[05:58] <riking> sent the email, then.
[06:01] <riking> I just wanted to file a bug on Transmission that it should support adding a webseed to an already-started torrent when someone didn't put it in their torrent file for their music album
[07:09] <ricotz> wgrant, hi :)
[08:41] <cjwatson> ricotz: done
[08:41] <cjwatson> ricotz: William's on holiday, please stop bugging him
[08:41] <cjwatson> nacc: where "eventually" = "next rollout"
[08:46] <ricotz> cjwatson, thanks, I assumed he is active since it status changed
[15:03] <nacc> cjwatson: ack, that's what I figured :)
[17:06] <tvansteenburgh> how does one get access to an s390x snap builder?
[17:08] <xnox> tvansteenburgh, at the moment it is not generally / publically available. There is a limited number of snaps that are built with s390x. Usually for canonical-only projects / with restricted source requirements (not much use of external / 3rd-party source code). However, launchpad is in progress to gain virtualised s390x builders, at which point building for s390x architecture will be generally available.
[17:08] <xnox> tvansteenburgh, what specific snap you want to build for s390x? where is its snapcraft.yaml file?
[17:09] <xnox> most s390x snaps in snapstore are currently build by developers and pushed to the store manually.
[17:09] <tvansteenburgh> xnox: https://code.launchpad.net/~tvansteenburgh/+snap/etcd
[17:10] <xnox> i don't think "go get -t -d github.com/coreos/etcd/cmd/etcd" will be ok yet to be run on the current s390x builders
[17:11] <xnox> tvansteenburgh, you may want to file a launchpad question requesting evaluation if devirt snap can be enabled for that snap build & ppa.
[17:11] <xnox> tvansteenburgh, https://answers.launchpad.net/launchpad/+addquestion
[17:13] <tvansteenburgh> xnox: devirt snap?
[17:13] <tvansteenburgh> xnox: what's the problem with the 'go get'? firewall/proxy restrictions?
[17:14] <xnox> tvansteenburgh, currently s390x builders in launchpad are physical machines on the internal network which build things in a row. rather than KVM virtual machines that are spinned up by openstack and destroyed when they are done.
[17:15] <xnox> tvansteenburgh, thus the same physical s390x box is reused for ubuntu package builds; ppa builds; livecd builds etc.
[17:15] <xnox> tvansteenburgh, and e..g they do not have firewall access to snap store.
[17:15] <xnox> due to security concerns that one can break out of them.
[17:16] <tsimonq2> xnox: virtualized s390x> When might that happen?
[17:16] <xnox> tvansteenburgh, your team has access to s390x machines; and it is connected to jenkins; thus you can use those instances to build your snap in that environment and upload to store.
[17:17] <xnox> tsimonq2, i wish for it to happen any day now. there is openstack region setup with it, but i have no idea when it will be enabled in launchpad. i think it is close. but not there yet.
[17:17] <xnox> tsimonq2, i guess wgrant knows more
[17:17] <tsimonq2> Ok
[17:18] <tsimonq2> It would be great if something could be said to ubuntu-devel{,-discuss,-announce} when that happens :)
[17:18] <tvansteenburgh> xnox: fair enough. i'm not in a big rush, and i know we *can* do it manually right now, but i'm still eager to get everything on lp
[17:19] <xnox> tsimonq2, i'm sure it will be very public about it.
[17:19] <xnox> tvansteenburgh, right, lp is cleaner for these things
[17:20] <xnox> tvansteenburgh, you should have all the arches on lp unrestricted already: amd64 i386 armhf arm64 ppc64el -> do you have all of those enabled?
[17:20] <tsimonq2> One thing that has nabbed me before is when I don't have access to the CI Train and there's test failures *only* on s390x, and I have no way to check before uploading (and then I have to do a follow-up upload fixing the thing I missed), I'm curious why people who already have upload access to packages in the archive can't do the same in a PPA... *shrug*
[17:20] <tsimonq2> xnox: Cool cool, thanks.
[17:25] <tvansteenburgh> xnox: yeah i have everything i need except s390x