[00:14] <teward> hmm... are the builders being slow or having other network issues?  https://launchpad.net/ubuntu/+source/anki/2.1.8+dfsg-1ubuntu1/+build/17208521 has been running for 51 minutes, and that's a pure python package... not sure if it's resources or just the system not relaying me the console logs in any expedient fashion but it seems unusual for it to be sitting here for 51 minutes in the queue after upload
[00:36] <teward> either that or the builder froze up
[00:37] <teward> cjwatson: not sure if you can poke it ^ but it does look frozen from what I can see
[00:37] <teward> (i hate pinging...)
[00:40] <wgrant> teward: This time of day it's probably better to ping me
[00:40] <wgrant> Let's see.
[00:41] <sarnold> 00:37:12 ..
[00:41] <teward> wgrant: ack.  wasn't sure if you were still here (last time I saw you was... 02:40 yesterday in my logs, so...)
[00:41] <teward> wgrant: thank you either way :)
[00:41] <wgrant> teward: Well I've been to sleep in between
[00:41] <wgrant> It's nearing 11am here
[00:41] <teward> heh :p
[00:42] <teward> ahh so you're that far ahead right, makes sense.
[00:43] <teward> wgrant: it's been stuck at "Setting up python3.7-minimal (3.7.4~rc1-1) ..." for at least 20-30 minutes, which makes no sense 'cause I can't see WHY that'd take that long to set up even in the builders
[00:43] <teward> which makes me think "stuck"
[00:58] <wgrant> teward: Yeah, something was a bit stuck. Fixed.
[00:58] <wgrant> Thanks.
[01:01] <teward> wgrant: thanks for looking :)
[01:40] <tsimonq2> cjwatson: ack
[10:31] <mvo> hey, quick question - I setup a core-beta snap inhttps://code.launchpad.net/~snappy-dev/+snap/core-beta  and its setup to auto-upload to the store. however I don't see any with "snapcraft history core" and no indication in the build that the upload failed (s390x build happend >20min ago). any hints for me?
[10:34]  * mvo tries to disable/enable the build
[10:43] <cjwatson> mvo: disabling/enabling will make no difference.  let me have a quick look
[10:44] <cjwatson> mvo: I mean the s390x build failed, but I assume you've seen that
[10:48] <mvo> cjwatson: yeah, it fails with that it can't clone the core-snap repo it seems
[10:49] <mvo> cjwatson: I disabled upload and then re-enabled upload and it seems to have made a difference, I got an SSO login and then had the "upload to the store" button (might be coincidence of course)
[10:49] <cjwatson> mvo: Can you see if this snap is perhaps in a review queue in the store?  You should be able to see it somewhere on https://dashboard.snapcraft.io/snaps/
[10:49] <cjwatson> mvo: Yeah, please stop messing about with that, it's only going to confuse things :)
[10:49]  * mvo stops
[10:50] <cjwatson> Makes it harder for me to correlate current state with logs
[10:50] <mvo> this is what I see in the build log "fatal: unable to access 'https://git.launchpad.net/~snappy-dev/core-snap/': GnuTLS recv error (-110): The TLS connection was non-properly terminated."
[10:50] <cjwatson> That was probably a temporary error
[10:50] <mvo> cjwatson: sorry :( I think I messed this up then, I re-logined
[10:50] <mvo> (since, stopped doing anything now)
[10:50] <cjwatson> mvo: Do have a look at the dashboard though, since I suspect it's in a queue there
[10:51] <mvo> yeah, now its coming in
[10:51] <wgrant> Supported architectures
[10:51] <wgrant> s390x
[10:51] <wgrant> Package path
[10:51] <wgrant> Built at
[10:51] <wgrant> 2019-07-02 09:59 - 51 minutes ago
[10:51] <wgrant> Submission date
[10:51] <wgrant> 2019-07-02 10:46 - 4 minutes ago
[10:51] <mvo> yes, clicked on "upload this package to the store" in the individual build page
[10:51] <wgrant> Ah
[10:51] <mvo> again, appologies I destroyed evidence apparently
[10:51] <mvo> (sorry, wanted to get this beta out for QA and was too impatient)
[10:52] <cjwatson> Yeah, I can't work this out any more I don't think
[10:52] <cjwatson> You've done too much
[10:52] <tkamppeter> Hi,
[10:53] <cjwatson> I've asked twom to join though since some of his recent changes might be relevant
[10:53] <tkamppeter> I have cloned the LP repo of network-manager via
[10:53] <tkamppeter> git clone https://git.launchpad.net/network-manager
[10:53] <mvo> sorry! I will be more patient next time.
[10:53] <mvo> I have a vague memory though that the auth for the store-upload can expire and that setting to "not upload", save, "upload", save fixes thngs but that may be outdated info
[10:54] <tkamppeter> Then I have done changes, did "git commit -a" and then I pushed the result using
[10:54] <tkamppeter> git push git+ssh://till-kamppeter@git.launchpad.net/~till-kamppeter/+git/network-manager
[10:55] <tkamppeter> This creates a repo on my LP account.
[10:55] <cjwatson> That's the wrong path
[10:55] <cjwatson> You want /~till-kamppeter/network-manager
[10:55] <cjwatson> If you have the +git in there then it makes a personal namespace which won't be mergeable into the project one
[10:56] <tkamppeter> Now I want to propose my changes to be merged into the original, but on
[10:56] <tkamppeter> https://code.launchpad.net/~till-kamppeter/+git/network-manager/+ref/master
[10:56] <cjwatson> tkamppeter: you can stop typing and read my answer :)
[10:56] <tkamppeter> I do not see a link for a merge proposal.
[10:57] <cjwatson> mvo: The expiry problems should mostly be solved nowadays I think, and in any case I wouldn't expect expiry yet for a snap set up in March
[10:57] <tkamppeter> Thanks, will try.
[10:58] <tkamppeter> cjwatson,
[10:58] <tkamppeter> git push git+ssh://till-kamppeter@git.launchpad.net/~till-kamppeter/network-manager
[10:58] <tkamppeter> gives
[10:59] <tkamppeter> fatal: remote error: Unexpected Zope exception: TimeoutError: timeout exceeded.
[10:59] <cjwatson> That's because of a service outage at the moment.  Should be fixed shortly
[11:01] <tkamppeter> cjwatson, thanks.
[11:04] <tkamppeter> cjwatson, it is working now, thanks.
[11:13] <tkamppeter> cjwatson, merge proposal worked now, thanks. More and easier accessible documentation would be great. Or ways how it works in GitHub/GitLab.
[11:29] <cjwatson> tkamppeter: Yeah, the GitHub model is less flexible but in some ways simpler.  We do have bugs for making things a bit more obvious and I expect we'll be taking a serious look at the whole thing sometime in the next nine months or so
[11:54] <rbasak> tkamppeter: my suggestion to make that better is https://bugs.launchpad.net/launchpad/+bug/1813778
[11:54] <cjwatson> I essentially agree with that bug - we just need to sort out all the details.
[11:55] <rbasak> ack
[11:55] <rbasak> I wonder if tkamppeter would have found that sufficient, or if something further would have been needed
[11:57] <seb128> +git also seems like it's confusing as a name
[11:57] <seb128> using +personal or something instead could maybe help?
[13:50] <rbasak> seb128: AIUI, the mistake is to add +git or +anything. Usually that is not required.
[13:51] <rbasak> (except for +source to indicate the target package)
[13:53] <seb128> rbasak, yeah, I don't know how people end up with that url in use, perhaps because there is no obvious instructions and poking around they see those
[14:13] <rbasak> seb128: maybe https://help.launchpad.net/Code/Git#Repository_URLs?
[14:13] <rbasak> Though it does say "no particular connection to any project or package", perhaps what that means is not obvious to those not familiar with Launchpad's model.
[14:14] <seb128> yeah, maybe...
[21:23] <srwalter> I'm having trouble with a PPA upload.  I had a few initial errors, which I fixed, but I'm still getting rejected and with no obvious error message now, "Rejected: Further error processing not possible because of a critical previous error."  (stevenrwalter/lxk is the PPA)