[01:12] <Umeaboy> Hi!
[01:13] <nazo> hi
[01:13] <Umeaboy> I was looking to translate the terminal output that appears in update-manager in Ubuntu, but I see nothing to translate in that package. Am I blind?
[01:14] <Umeaboy> It's the output you see when you in update-manager click on the small black arrow to view what's happening.
[01:14] <Umeaboy> I hope someone understands what I'm referring to.
[01:14] <wgrant> Umeaboy: That's probably output from dpkg or apt.
[01:14] <Umeaboy> OK.
[01:14] <Umeaboy> Thanks.
[01:15] <Umeaboy> I get a 503 error visiting the website.
[01:15] <wgrant> See /topic
[01:16] <Umeaboy> OK. Sorry! Missed that.
[01:24] <freshquiz> is it supposed to be back up now?
[01:24] <wgrant> Taking rather longer than expected, unfortunately.
[01:25] <wgrant> And back now.
[01:25] <freshquiz> wgrant: no worries, just checking it's not just me
[01:26] <Umeaboy> wgrant: It's not up here.
[01:26] <freshquiz> up for me at .au
[01:26] <wgrant> It's up everywhere.
[01:26] <Umeaboy> freshquiz: http://www.downforeveryoneorjustme.com/
[01:26] <Umeaboy> :)
[01:27] <freshquiz> Umeaboy: cheers
[01:27] <Umeaboy> Now it's up.
[01:27] <freshquiz> Umeaboy: but I guess I wanted some inside info too
[01:27] <Umeaboy> freshquiz: Such as?
[01:28] <freshquiz> Umeaboy: a cause
[01:28] <Umeaboy> Right.
[01:28] <Umeaboy> You can always ping the adress.
[01:31] <wgrant> That wouldn't have helped here. The frontends were up, the DB was down.
[01:33] <Umeaboy> Right.
[01:37] <Umeaboy> apt-all contains a sentence like this that follows: Note, selecting '%s' for glob '%s'
[01:37] <Umeaboy> What does the word glob represent in this sentence?
[01:37] <nacc> Umeaboy: similar to the concept in `man glob`
[01:38] <Umeaboy> Ooooooooh.
[11:54] <wkmanire> Hello, I'm trying to sign the ubuntu code of content and I've run into a strange situation.
[11:54] <wkmanire> I created and uploaded my key using seahorse, but the gpg cannot see the key even though it shows up in seahorse.
[11:55] <wkmanire> i.e. gpg --list-keys has no output. Don't seahorse and gpg read from the same directory?
[12:00] <maxb> wkmanire: What about 'gpg2 --list-keys' ?
[12:01] <wkmanire> maxb: When I do that, I realize that I am a moron.
[12:01] <wkmanire> maxb: Thank you for your help.
[12:01] <maxb> Well, it's not obvious, unless you're aware of the gpg 1 to gpg 2 transition
[12:03] <wkmanire> maxb: I certainly wasn't aware of this. Maybe some of the instructions in launchpad could make mention of this? "if gpg can't find your keys try gpg2" or something along thos elines.
[12:03] <wkmanire> I'm all setup now. Thanks again.
[12:08] <cjwatson> maxb: huh, "man gpg2" suggests that it uses the same ~/.gnupg/ directory - what am I missing here?
[12:09] <cjwatson> happy to edit docs but I'd like to understand exactly what's going on first
[12:10] <maxb> I was mostly going on speculation, but I believe gpg2 uses a different format for storing secret keys, at least
[12:10] <wkmanire> cjwatson: For transparency, I'm on Fedora 23 Workstation.
[12:10] <maxb> I'm unclear how that interacts with publick keys
[12:10] <wkmanire> it could be specific to my installation.
[12:11] <wkmanire> Looking forward to 16.04 Beta 1 :)
[12:13] <cjwatson> ah, I think somebody who uses Fedora might need to work out the details of a proposed doc change
[12:13] <cjwatson> since gpg --list-keys and gpg2 --list-keys seem to be functionally identical here on Ubuntu
[12:18] <wkmanire> cjwatson: Makes sense.
[12:19] <wkmanire> Time for bed for me. Time appropriate greetings :)
[14:59] <Saviq> hey, is there a process for renaming projects on launchpad? or is it basically something I shouldn't want to do?
[15:02] <cjwatson> Saviq: ask on https://answers.launchpad.net/launchpad and LP staff can do it
[15:03] <Saviq> thanks!
[16:16] <spotz> Is https://bugs.qastaging.launchpad.net/ permanently down?
[16:44] <cjwatson> spotz: no, probably a casualty of recent reboots for security upgrades.  looking into it
[16:45] <spotz> thanks cjwatson we're preparing documentation for a summit session and want to use it
[16:52] <teward> cjwatson: can you or someone else poke the builders on amd64/i386 and see why many look to be stuck in  'cleaning' state on lcy01?
[17:02] <cjwatson> teward: chunks of its cloud infrastructure apparently weren't happy last time it tried to reset anything.  poking
[17:09] <cjwatson> teward: not going so well, I've asked for sysadmin help as it looks like there's some kind of networking problem in that cloud
[17:10] <cjwatson> teward: don't be too surprised if this isn't fixed soon, only critical issues are receiving attention at the moment
[17:11] <cjwatson> (it only becomes critical if lgw01 goes down too; otherwise we can tolerate the slight queueing)
[17:41] <teward> cjwatson: ack, thanks for poking.
[17:50] <cjwatson> spotz: may take a while due to aforementioned sysadmin backlog.  maybe you could manage with https://bugs.staging.launchpad.net/ (main gotcha: it uses staging SSO, so anyone using two-factor auth needs a separate 2FA token)
[17:51] <spotz> cjwatson It's going to be new OpenStack contributers for the most part so we should be ok. Thank for the help
[18:10] <teward> cjwatson: would you be able to poke Canonical IS and get them to look at the wiki for Ubuntu, possibly?  "Connection Refused" errors.
[18:10] <teward> 500 INternal Server now
[18:17] <cjwatson> teward: please try #canonical-sysadmin rather than indirecting through me.  I'm about to quit for the day
[18:19] <teward> cjwatson: ack, i'll stop there, though i wasn't aware of the channel :)
[22:25] <KombuchaKip> Hey everyone. I have a commercial subscription to Launchpad. I've tried emailing several times commercial@launchpad.net, william.grant@canonical.com, and feedback@launchpad.net, but nobody seems to be checking those accounts. Is there someone else I should be asking for support queries (e.g. PPA, etc.)?
[22:26] <wgrant> KombuchaKip: Hm, I didn't see any tickets to feedback@launchpad.net, but the commercial@launchpad.net ones are in my queue for today.
[22:26] <KombuchaKip> wgrant: Hey Will. Maybe the emails are getting lost in a spam filter or something. In any case, which address would you prefer I use in the future?
[22:33] <wgrant> KombuchaKip: commercial@launchpad.net is best for issues with commercial projects.
[22:34] <wgrant> I'll see what I can find about the feedback@launchpad.net. Certainly getting lots of tickets there, sorry about that.
[22:34] <wgrant> Maybe an overzealous spam filter, as you say.
[23:02] <KombuchaKip> wgrant: Thanks. I'll resend to commercial@launchpad.net now.
[23:06] <KombuchaKip> wgrant: I see your responses. Thanks a lot.