[08:06] <Q-FUNK> Howdy!  I haven't logged onto LP in a while. I just updated my password.
[08:07] <Q-FUNK> I noticed that there's a field to update the username as well. Would changing this propagate? Would it affect membership in various Ubuntu groups?
[08:10] <Q-FUNK> oh, and @ubuntu.com e-mail?
[08:37] <SpecialK|Canon> Q-FUNK: Howdy! Good call. Updating username should generally be fine and won't impact membership etc. - @ubuntu.com email I don't know how that's controlled - you might need to check with the folks who manage that, but I'll take a look and see what I can find
[08:38] <Q-FUNK> SpecialK|Canon: Thanks. Let's see what you can find. :)
[08:40] <SpecialK|Canon> Q-FUNK: https://wiki.ubuntu.com/UbuntuEmail - it will affect your address, do take note of the warnings;
[08:43] <Q-FUNK> SpecialK|Canon: thanks. Connection to that times out.
[08:44] <Q-FUNK> SpecialK|Canon: ok, it finally resolved. Right, so @ubuntu.com e-mail affected, but will be transparently updated. Fair enough.
[08:45] <Q-FUNK> SpecialK|Canon: and GPG keys would need the new address added too, I guess.
[08:50] <SpecialK|Canon> Q-FUNK: Anywhere you've explicitly referenced the old username/address will need manually updating, yes
[08:51] <SpecialK|Canon> Q-FUNK: Things internal to Launchpad should generally refer to your user by internal id, so from Launchpad's perspective it's a cosmetic change
[08:51] <SpecialK|Canon> (i.e. group memberships etc.)
[15:14] <zyga> hello, I'm looking at https://code.launchpad.net/~niemeyer/snapd/+git/snapd and I see "repository scan failed"
[15:14] <zyga> I tried clicking the rescan button but it seems I don't have permissions for that
[15:14] <zyga> what does the error mean?
[15:29] <cjwatson> zyga: I don't see an error.
[15:29] <zyga> it's gone now
[15:29] <zyga> sorry, I should have said so
[15:30] <cjwatson> Any time a repository is pushed to LP, LP looks at the tip of all its branches; this is used for stuff like detecting changes to merge proposals
[15:30] <cjwatson> That's the scan that I guess must have failed
[15:30] <zyga> ah, I see
[15:37] <cjwatson> zyga: If it happens again then we should be able to fix it, but as you observed it can often clear up by itself
[15:40] <cjwatson> zyga: Though it's also sort of weird that that import is owned by an individual rather than a team, and if it's part of any important process then it might be a good idea to fix that
[15:42] <zyga> mmm, that's a good point, I'll raise that at my next standup
[19:54] <raigl> Where do I find how to change the syntax used in code display? I have created my own language, and the coloring is misleading.
[20:23] <cjwatson> raigl: We only update it somewhat irregularly so it may take a while, but the best long-term approach is to get a syntax definition into https://pygments.org/
[20:27] <raigl> Thanks, thats the long term solution. Is there any option to disable it until then?
[20:34] <cjwatson> Not IIRC, but sorry, it's my evening and I'm also dealing with having been paged about an emergency
[20:35] <cjwatson> So if you want a more considered answer it would be best to use the support link in the topic