[01:57] <exarkun> How do I stop getting a ton of bug spam from Launchpad?
[01:58] <exarkun> I don't need to hear about five status changes a day in a bug for each of the six Ubuntu releases that it affects, honest.
[02:07] <mwhudson> exarkun: are these bugs you are directly subscribed to?
[02:08] <EvilResistance> exarkun:  if they're bugs you're directly subscribed to, modify your bug subscriptions.  if they're bugs you receive updates on because a team you're part of is subscribed, just mute your bug mail.
[02:51] <dobey> man procmail
=== StevenK changed the topic of #launchpad to: Help contact: (LP team is sprinting, limited availability) | https://launchpad.net | Launchpad is Open Source | This channel is logged
=== wgrant is now known as Guest57052
=== danilo_ is now known as danilos
=== zyga_ is now known as zyga
[10:32] <lamalex> Is there a URL for seeing approved merges?
[10:32] <lamalex> I know, https://code.launchpad.net/unity/+activereviews, but if I just want to see approved (ie for rss or something) can I do that?
[10:35] <tumbleweed> lamalex: +merges
[10:40] <lamalex> oh nice
[10:40] <lamalex> thanks!
[11:13] <shodanium> hello, i can't reset my password (https://launchpad.net/~shodan), and none of the support links are any use? tried many times in the past days, checked Spam folder (mail is on Gmail), checked out Help and Answers, still totally stuck. the most amazing part is that other email notifications *do* get through! but the password reset link does not.
[11:14] <shodanium> "can't reset" == "5+ tries over past 2 or 3 days, not a single email from launchpad"
[11:15] <StevenK> shodanium: Please ask in #canonical-isd
[11:16] <shodanium> StevenK, thanks for the pointer!
[11:58] <mpt> Are there any statistics on how many changes to Ubuntu bug reports Launchpad deals with per day?
[11:59] <deryck> mpt, hmmm, I'm not sure.  I doubt it.  I can look at lpstats and see.
[12:01] <mpt> deryck, I see there's a graph of total rows in bugactivity. I guess what I'd be looking for is change in the total per day
[12:02] <deryck> mpt, right, the change in total and limited to just ubuntu bugactivity.
[12:02] <mpt> yeah
[12:02] <mpt> What's the bugnotification table for?
[12:03] <deryck> Yeah, and we just don't have anything like that.
[12:03] <deryck> mpt, holding table for the notifications we send.  I don't think it's a one for one with activity.
[12:03] <deryck> mpt, headed to lunch, back after, sorry
[12:53] <BigWhale> what's up with the build farm? It'll take nine more hours for my packages to build? :'(
[12:56] <popey> BigWhale: busy busy boxes
[13:01] <BigWhale> popey, that's because everyone is drinking^Wjamming in Budapest and nobody is running the boxes! ;)
=== wgrant_ is now known as Guest21768
[13:23] <exarkun> They're bugs in Ubuntu.  I don't think I'm an Ubuntu team member.
[13:25] <lifeless> exarkun: I missed the context; whats up?
[13:28] <exarkun> lifeless: Too much email from Launchpad, eg for changes to bugs like https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/571648
[13:28] <ubot5> Launchpad bug 571648 in twisted (Ubuntu Precise) "glib2reactor/gtk2reactor polls at 10 Hz even when unneeded" [High,Confirmed]
[13:28] <exarkun> Fixed in Twisted, still jumping around from state to state in Ubuntu
[13:29] <exarkun> Not really relevant to me anymore, but I still got like six emails about it yesterday
[13:30] <exarkun> Sorry, seven emails. ;)
[13:31] <iceroot> exarkun: you can unsuscribe from the bug
[13:31] <exarkun> iceroot: I am not directly subscribed to the bug.
[13:31] <tumbleweed> you should still be able to mute mail from it
[13:32] <exarkun> The help for the mute button suggests otherwise.
[13:32] <iceroot> exarkun: in all mails there is a link about "configuring notifications"
[13:33] <exarkun> Maybe I misunderstand it though?
[13:33] <lifeless> exarkun: ugh, yes that is a nuisance.
[13:33] <lifeless> and yes, you should be able to mute the bug - it hsould be an icon on the right hand side
=== wgrant is now known as Guest18217
[13:44] <exarkun> okay, thanks.  for some reason the mute description confused me.
=== andreas__ is now known as ahasenack
=== Quintasan_ is now known as Quintasan
[20:04] <zooko> Dear people of #launchpad: there is a thing that I like about launchpad...
[20:04] <zooko> in fact, when a random guy in a coffeeshop asked me yesterday what my launchpad t-shirt was about
[20:04] <zooko> this is the thing I explained to him.
[20:04] <zooko> But I'm not sure that it is really an intended use case, and I'm wondering if I should stop trying to use laucnhpad for this.
[20:05] <zooko> The thing is: there's a bug that affects many different open source projects.
[20:05] <zooko> If I report it to one of them, they'll reject it saying it is the fault of the other one.
[20:05] <zooko> So what I like to do is open bug reports with all of them, and then tie the reports together on a launchpad ticket, and give everyone a link to the launchpad ticket.
[20:05] <zooko> That's worked quite successfully a few times in the past.
[20:06] <zooko> e.g. https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303
[20:06] <ubot5> Launchpad bug 461303 in binutils (Fedora) "generates-bad-code regression" [Unknown,In progress]
[20:06] <zooko> and e.g. https://bugs.launchpad.net/ubuntu/+source/foolscap/+bug/782414
[20:06] <ubot5> Launchpad bug 782414 in foolscap "tahoe-lafs can't start because foolscap packaging metadata doesn't declare the fact that it supports secure_connections" [Unknown,New]
[20:07] <zooko> So, here I am wanting to do that again, about a bug which interacts with: gcc, Fedora, Crypto++, pycryptopp, and Tahoe-LAFS.
[20:07] <zooko> But, I can't figure out how to create a ticket on launchpad so that I can link the five different tickets on those five projects's trackers.
[20:07] <zooko> Because, none of those five uses launchpad as its bug tracker.
[20:07] <zooko> If any one project does, then I can link the other four.
[20:07] <zooko> IIUC.
[20:14] <lifeless> zooko: oooh thats a shiny use case.
[20:14] <lifeless> zooko: you basically need to be able to add a watch directly to a reference-only project in LP
[20:14] <lifeless> zooko: we totally want such bugs in the LP db
[20:16] <zooko> lifeless: I'm glad you like it!
[20:16] <zooko> That's encouraging.
[20:17] <zooko> I always thought lp was intended for this back when it was a gleam in your eye.
[20:17] <lifeless> as a workaround, if any of the projects are in Ubuntu, you could start with a bug on Ubuntu itself.
[20:17] <zooko> If we can unstick this a little, or at least see how to in the future, I'll edit the Google+ post that I just made containing roughly the same text as above.
[20:17] <zooko> Okay, I'll... yeah, I'll do Ubuntu's package of Crypto++.
[20:17]  * zooko tries.
[20:18] <zooko> No offense, but I often find lp UI confusing.
[20:18] <dobey> it often is confusing :-/
[20:18] <zooko> I generally muddle through, but I always think to myself "if only we could streamline this then there would be more better data flowing in from more users"...
[20:18] <zooko> I think there are some concepts in lp which are not native to my way of thinking and are also not called out very explicitly in the UI.
[20:19] <lifeless> zooko: if you are interested in helping streamline it, I'd be delighted to help you get accustomed to LP's code base
[20:19] <zooko> Such as.. what was it I kept getting tripped up by the other day..
[20:19] <zooko> There was some distinction between a team and a project that I kept mis-navigating.
[20:19] <zooko> lifeless: I'm not unwilling to write patches, but I think the need here is for a designer, which isn't my expertise, and for a stronger eye+hand than another chef thrusting his spoon in. :-)
[20:20] <zooko> Now, complaints I'm good at.
[20:20] <zooko> And I think they *might* help, maybe.
[20:20] <zooko> Anyway, the thing I'm noticing right now is that I'm never entirely sure whether I'm looking at Ubuntu's package of $X or at $X's source or at upstream-$X.
[20:20] <zooko> Where today X=gcc
[20:20] <zooko> Sorry, I mean cryptopp.
[20:21] <lifeless> zooko: someone skilled with a (constructively) critical eye would certainly be a positive contributor - we have a designer (huwshimi), product strategist (mrevell) and I can offer technical direction quite easily :)
[20:21] <lifeless> zooko: LP's problem is that it got fat somewhere along the way; a focus I have is rending that down and getting it lean again (internally)
[20:22] <zooko> lifeless: well, I'm willing to (a) shut up about my problems, (b) keep mentioning them in passing on this channel while doing other work, (c) spend, oh, I dunno, an hour writing notes?, (d) ?
[20:22] <lifeless> zooko: I do agree that a random walk isn't necessarily the best idea :)
[20:22] <zooko> (c) only if you really think it would help.
[20:22] <zooko> lifeless: yes, I approve of your focus!
[20:22] <zooko> lifeless: there's this thing - -I wonder if you've noticed.
[20:23] <lifeless> zooko: b is good, c encoded as 'file clear symptom based bug reports', d - I will get you writing patches someday
[20:23] <zooko> Of all sites that I visit in FF on Linux, LP alone takes, like 1 or 2 *seconds* to render after I switch to a tab that has already loaded it.
[20:23] <zooko> It's kind of mysterious.
[20:23] <lifeless> that is interesting
[20:23] <zooko> Yeah. Oh, I'll do a quick experiment...
[20:23] <lifeless> do you have an nvidia card ?
[20:24] <zooko> Yes.
[20:24] <zooko> But... are you serious?
[20:24] <zooko> Okay, the experiment may involve turning off my network temporarily...
[20:24] <lifeless> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/605567
[20:24] <ubot5> Launchpad bug 605567 in Mozilla Firefox "Extremely slow painting of launchpad.net bug details page with nvidia driver" [High,Confirmed]
[20:25] <lifeless> https://bugs.launchpad.net/launchpad/+bug/744808
[20:25] <ubot5> Launchpad bug 744808 in Launchpad itself "image sprite is packed very asymmetrically and triggers poor rendering performance in firefox3 and missing icons in firefox4" [High,Triaged]
[20:26] <zooko> lifeless: just from the titles that sounds plausible.
[20:26] <zooko> Okay, so back to what I was doing.
[20:26] <lifeless> zooko: its probably very shallow to fix
[20:27] <lifeless> zooko: and has nothing to do with what direction to pull in :)
[20:28] <zooko> I don't think I'll have a go at that one.
[20:28] <lifeless> :P
[20:28] <lifeless> I should make time for it
[20:28] <lifeless> butfirsttriage
[20:29] <zooko> Heh heh.
[20:32] <zooko> Oh, one more thing -- two tickets linked to from here are stuck: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303
[20:32] <ubot5> Launchpad bug 461303 in binutils (Fedora) "generates-bad-code regression" [Unknown,In progress]
[20:32] <zooko> Because auto-update isn't working for them and I don't have perms to manually fix them.
[20:32] <zooko> So I posted asking someone else to do so or to authorize me.
[20:34] <lifeless> posted where?
[20:34] <lifeless> ah, in the bug
[20:35] <lifeless> bug 605783
[20:35] <ubot5> Launchpad bug 605783 in Launchpad itself "SourceForge bugwatch updates are broken" [High,Triaged] https://launchpad.net/bugs/605783
[20:36] <lifeless> and bug 598575
[20:36] <ubot5> Launchpad bug 598575 in Launchpad itself "BugWatch updates on the Redhat Bugzilla are chronically broken" [Critical,Triaged] https://launchpad.net/bugs/598575
[20:38] <zooko> FYI: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/915018
[20:38] <ubot5> Launchpad bug 915018 in libcrypto++ (Ubuntu) "gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on" [Undecided,New]
[20:39] <zooko> I gave you credit for the idea of abusing the the tracker of bugs in Ubuntu's packages.
[20:40] <zooko> Whoops I broke it.
[20:41] <zooko> I made a link from that to Crypto++, deleted it ("marked it as no longer affecting Crypto++"), then clicked on "Also affects project", then got a 404 page.
[20:41] <zooko> Doing "Also affects project" again just now it worked.
[20:41] <zooko> So I guess there was a race condition there.
[20:42] <lifeless> your primary context had changed
[20:42] <lifeless> the delete happens via ajax and didn't update the primary context
[20:42] <lifeless> but the form is done under that context
[20:46] <zooko> Ah.
[20:46] <zooko> BTW, I just had another momentary one of those "launchpad concept moments".
[20:46] <zooko> I went to link to the Fedora ticket, and clicked on "also affects project".
[20:47] <zooko> After searching through 3 pages of projects with "Fedora" in their name I remembered that launchpad has a concept of "distributions" which are distinct from projects.
[20:47] <lifeless> yea
[20:48] <lifeless> there is a bug, can't trivially find it
[20:49] <lifeless> bug 1334
[20:49] <ubot5> Launchpad bug 1334 in Launchpad itself "Separate "also affects: " Project and Distribution links are hard to use and confusing" [Low,Triaged] https://launchpad.net/bugs/1334
[20:49] <zooko> I'll subscribe to that one and the nvidia rendering one...
[20:50] <zooko> At least, I clicked "this affects me". Not sure if that subscribes me.
[20:50] <lifeless> it does not
[20:50] <lifeless> if you want mail, click on subscribe on the right hand side
[20:51] <lifeless> we find its better not to conflate anything with subscribing, cause folk often do not want mail sent to them
[20:53] <zooko> I wonder if there could be a sufficiently unobtrusive way to offer it. Maybe I could click on the "change if this affects me" button and get options: "No, it doesn't affect me.", "Yes, this affects me." and "Yes, this affects me and subscribe to this bug.".
[20:55] <zooko> I'd like to show you my post about this on Google+, but unfortunately I can't make it publicly visible without sending it to the notice of all of my subscribers.
[20:55] <zooko> Thanks for your help! Back in  abit.
[20:55] <zooko> Oh, here: Update: Robert Collins suggested I create the ticket on launchpad by reporting a bug against Ubuntu's packaging of the software, even though technically speaking the version that Ubuntu has packaged doesn't have this problem. Here's the result:
[20:55] <zooko>  
[20:55] <zooko> https://bugs.launchpad.net/pycryptopp/+bug/915018
[20:55] <zooko>  
[20:55] <ubot5> Launchpad bug 915018 in libcrypto++ (Ubuntu) "gcc 4.7.0 fixes a bug that Crypto++ 5.6.1 relies on" [Undecided,New]
[20:55] <zooko> However, since other people are not likely to stumble upon this solution, I'm still not entirely sure what I should tell the next person who asks me about my launchpad t-shirt.
[21:03] <lifeless> well, you should file a bug about this on LP itself
[21:22] <rektide> how do i download the source for a project? https://launchpad.net/lightdm
[21:23] <rektide> ah, there's a "code" link at the top fo the page.
[22:08] <zooko> Heh, trying to report a bug on LP itself, got a timeout error.
[22:08] <zooko> (Error ID: OOPS-7c221270569053ae5b44945b9e906a19)
[22:08] <ubot5> https://lp-oops.canonical.com/oops.py/?oopsid=7c221270569053ae5b44945b9e906a19
[22:09] <zooko> And another small navigation issue: I'm having trouble finding how to report a bug on LP itself. :-}
[22:10] <zooko> There, found it.
[22:15] <zooko> lifeless: hope this helps: https://bugs.launchpad.net/launchpad/+bug/915067
[22:15] <ubot5> Launchpad bug 915067 in Launchpad itself "can't report link to bugs in projects none of which use launchpad for bug tracking" [Undecided,New]
[23:14] <peterbrett> Hey guys
[23:14] <peterbrett> My translations have been awaiting import for several days... is there a known backlog length at the moment? :-)