[03:04] <strycore> Hi, I have uploaded the 0.5.7 release of Lutris to the PPA lutris-team/lutris but it doesn't show up anywhere. All I have is the 0.5.6 release. When I try to re-upload it tells me the package has already been uploaded. Anything to get this unstuck?
[03:05] <sarnold> strycore: check your email, some classes of launchpad errors are reported via email
[03:41] <strycore> that's the thing, I usually receive an email when I upload a faulty package but here I got nothing
[03:43] <sarnold> argh. I know I've heard of this one. what was it... missing signature? expired gpg key?
[03:43] <sarnold> is the 'already been uploaded' message coming from dput? I think there's a way to modify a local file somewhere to cause dput to forget that it's already done the upload.
[03:43] <strycore> ooh, you might be on something, I did update my GPG key
[03:44] <sarnold> aha! does launchpad know the new key?
[03:47] <sarnold> time for me to bail.. well, tha was 45 minutes ago. anyway.
[03:47] <sarnold> have fun, good luck, I hope that's it :)
[03:52] <strycore> I didn't have the key in launchpad, if you have that trick to make dput forget about the upload that would be handy. Otherwise, no worry. Thanks for reminding me about the GnuPG key :D
[04:02] <wgrant> strycore: dput -f
[04:02] <wgrant> It's a purely local check
[04:03] <strycore> awesome, thanks!
[04:06] <strycore> the package is building. Thanks again!
[09:25] <mvo> hey, I am trying to push a git repo of snapd to lp and I get "git push fatal: remote error: Path translation timed out.". I found https://answers.launchpad.net/launchpad/+question/689269 that indicates this might be some sort of LP issue? or am I doing something wrong, I added a new rmote "git.launchpad.net/~mvo/snapd/+git/snapd-wip" (that does not exit yet) and tried to push to that
[09:37] <cjwatson> mvo: This is a known issue being worked on in the general case, but maybe we can patch things up a bit in this specific case
[09:40] <cjwatson> mvo: (requested on ~is on Mattermost)
[09:47] <mvo> cjwatson: thank you, not super urgent right now for me. was just a bit confused if I did something wrong
[09:50] <cjwatson> mvo: You didn't - our "clone new repository based on existing one" protocol just needs some design fixes
[09:50] <cjwatson> mvo: See https://bugs.launchpad.net/launchpad/+bug/1883510
[09:50] <mvo> ta
[13:47] <cjwatson> mvo: Try now?  Sorry for the delay
[14:13] <tomwardill> oSoMoN: if you retry your snap builds, they stand a better chance of working now
[14:13] <tomwardill> fix for the bzr issue was just deployed
[14:14] <oSoMoN> tomwardill, did I retry too soon? https://code.launchpad.net/~osomon/+snap/0ad
[14:14] <tomwardill> took a bit longer than I'd like due to an unfortunate conflict with upgrading jenkins.
[14:14] <tomwardill> oSoMoN: the fix literally just went out 5 minutes ago
[14:14] <tomwardill> oh, huh, that top one is more recent than that
[14:14] <oSoMoN> yeah
[14:15] <tomwardill> maybe give it 5 minutes and try again, if it still fails, let me know
[14:15] <oSoMoN> will do
[14:15] <tomwardill> it's entirely possible it's an unrelated problem
[14:15] <tomwardill> which would be unfortunate
[14:25] <tomwardill> oSoMoN: so.... it's related to the same update, but it's a different problem
[14:26] <tomwardill> looking at it now
[14:26] <tomwardill> sorry!
[14:26] <oSoMoN> tomwardill, no worries, and thanks for looking into it. Do you want me to file a separate bug?
[14:27] <tomwardill> I'll file one in a mo when we've got a better handle on what's going on
[14:31] <oSoMoN> ack
[14:32] <tomwardill> oSoMoN: https://bugs.launchpad.net/loggerhead/+bug/1886834 fyi
[14:44] <mvo> cjwatson: thanks, worked now