[00:01] <matsubara> nhandler, and you followed the "also affects distribution link"?
[00:02] <nhandler> matsubara: Yeah. It gave the error I posted above when I tried to link to the upstream bug (for vzctl in Debian)
[00:02] <matsubara> nhandler, try without the package
[00:03] <matsubara> it seems to be the right thing to do (by looking at other ubuntu bugs with debian bugwatches) when it comes to upstream debian packages
[00:03] <nhandler> Yep, that did it matsubara. I just don't remember having to delete the source package when adding a bug watch in the past.
[00:15] <wgrant> matsubara: It's a bug triggered by the import of Debian into LP.
[01:11] <mohbana> hi, how do i delete my account
[01:13] <wgrant> mohbana: https://launchpad.net/people/+me/+edit, down the bottom.
[01:14] <mohbana> wgrant: if i change my email add do i get a confirmation emai;?
[01:21] <mohbana> mmm
[01:21] <mohbana> i found a bug
[01:22] <mohbana> all my previous bugs link to my old page
[01:22] <mohbana> x wrote 11 minutes ago ... clicking on x goes to my old page
[01:22] <mohbana> it seems like it's static
[01:22] <wgrant> mohbana: https://launchpad.net/people/+me/+edit, down the bottom.
[01:22] <mohbana> yes, done that
[01:23] <wgrant> Gah.
[01:23] <wgrant> Sorry, there was lots of lag.
[01:23] <mohbana> ok
[01:23] <mohbana> explains it
[01:23] <wgrant> You do get an email.
[01:23] <wgrant> What do you mean by the links go to your old page?
[01:24] <mohbana> no it doesn't sorry my mistake
[09:53] <stefanlsd> Is it possible to remove a bugwatch from LP yet?
[09:54] <persia> stefanlsd, You can render it meaningless, and stop it from watching, but you can't remove it.
[09:54] <stefanlsd> persia: mm. thanks. last i spoke to jcastro they said they were working on it.
[09:55] <persia> stefanlsd, Search for the bug for that.  subscribe.  That's the best way to find out when it's done.
[09:56] <wgrant> stefanlsd: Why do you want to remove it?
[10:04] <stefanlsd> wgrant: the added watch is actually different from the lp bug
[10:12] <wgrant> stefanlsd: Just detach it from the task.
[13:03] <bac> leonardr: thanks for swapping with me
[13:03] <leonardr> bac: just doing my bit
[14:34] <beuno> Hobbsee, kirkland, ping
[14:34] <beuno> which one of you guys would like to take a quick peak at a screenshot?
[14:37]  * persia wants to look
[14:37] <beuno> heh
[14:37] <beuno> persia, it's about bug #288147
[14:37] <beuno> still interested?
[14:38] <persia> Yep.  I made a lot of noise about that bug, which is why I wanted to see the proposed solution.
[14:38] <persia> (and I'm glad I guessed correctly : I'm still catching up on backscroll after 36 hours offline)
[14:39] <persia> Is this a temporary solution, or the malone-is-smart-enough-to-correct-context-on-the-fly solution?
[14:40] <beuno> persia, you mean redirect the user?
[14:40] <beuno> persia, http://beuno.com.ar/uploads/bug288147.png
[14:40] <persia> That, or just render the right context and rewrite the URL.  redirection is expensive for those with high latency.
[14:40] <beuno> added the bug # on the right-side again
[14:41] <beuno> no redirects for now, as some people use URL hacking to link stuff to stuff, and we sometimes have multiple contexts, so it needs a little more consideration
[14:41] <persia> As a workaround, that definitely solves the common usecase, and should get us back to seeing bug numbers pasted more instead of URLs (which is especially nice for those of us who don't log into edge).
[14:41] <beuno> cool
[14:41] <beuno> in that same branch
[14:42] <beuno> I'm also fixing bug #78565
[14:42] <beuno> which was one of the bug wins we would have from the original change
[14:43] <persia> Yeah, guessing the context isn't easy at all.  I use the url hacking workaround myself, but as previously expressed, due to various other issues pending time to address, it probably makes sense to limit that, and limit URL hacking to functions that can't change things.
[14:44] <beuno> alright,  I'll keep working a bit on the branch and see if I can get it landed today
[14:44] <beuno> it has some other changes
[14:44] <beuno> like the text when a bug is marked as a duplicate
[14:44] <persia> Right.  It's a simple URL hack to work around 78565, but users shouldn't have to do that.  The screenshot seems to address both use cases, at a cost of a little suplicate information.
[14:45] <persia> Users will have to learn to go to the top right rather than top left for the double-click copy though.  What do you think about having the new text be the link?
[14:45] <beuno> I thought of that
[14:45] <beuno> and sounded like a good idea
[14:46] <beuno> but, then we wouldn't have a fix for bug 78565
[14:46] <persia> Oh, because that doesn't appear on the bug comment page?
[14:46] <beuno> because we don't show the right-hand part on the permalink for a comment
[14:46] <beuno> yeah
[14:46]  * persia looks at a bug
[14:46] <beuno> so it wouldn't be consistent
[14:46] <beuno> and I'm a big fan of consistency
[14:47] <persia> Hrm.  The bug comment page needs a lot of other work, but I agree that putting the bare text on the right is probably the best solution for now.
[14:48] <persia> By the way, how do you determine the correct context from a URL like https://bugs.launchpad.net/malone/+bug/78565/comments/1 ?
[14:48] <beuno> yeah, we have a sprint for bugs UI in 3 weeks or so
[14:48] <beuno> persia, that's a fantastic question, for which I don't have an answer  :)
[14:49] <persia> Well, see, this new link thing must have some logic : I guess I'm asking "How are you fixing 78565?"
[14:49] <persia> Or does it just redirect to bugs/nnnnnn and then bounce from there?
[14:49] <beuno> exactly
[14:50] <persia> Ah.  That's broken in known ways then (and one's I personally find convenient), so no complaints :)
[14:50] <beuno> ha
[14:50] <persia> s/'//
[14:50] <beuno> ok
[14:50] <beuno> so +1?
[14:50] <persia> Yeah.  It's annoying because it's a change, but it no longer removes functionality, and it does reduce requirements for URL hacking for some use case.
[14:51] <beuno> super
[14:51] <persia> Since it's impossible to fix bugs without change, it's probably the best until Malone can get smarter about realtime redirects.
[14:51] <beuno> and we'll look into deeper solutions when we re-work the bug UI as a whole
[14:53] <persia> Do you think it would be possible to present the target screenshots developed at the UI sprint for general review, just in case anyone spots similar uncatalogued use cases that might be affected by the changes?
[14:54] <beuno> persia, yes, I would love to get feedback before doing big changes
[14:54] <beuno> and, I'll be at UDS
[14:54] <beuno> so I'll probably be trying to steal time from everyone to get feedback
[14:55] <persia> That sounds like excellent timing : the sprint concludes near UDS start, right?
[14:55] <beuno> yeap, 1 week in between
[14:57] <kirkland> beuno: howdy
[14:58] <beuno> hey hey kirkland
[14:58] <beuno> got a minutes to give me some input on the above ^  ?
[14:59] <kirkland> beuno: sure, let me read the scrollback
[15:01] <kirkland> beuno: screen shot looks excellent to me
[15:01] <beuno> fantastic
[15:01] <kirkland> beuno: thanks for taking care of it
[15:02] <kirkland> beuno: i look forward to it on edge ;-)
[15:02] <beuno> kirkland, my pleasure. Hopefully, I can get it through review today, so it lands tomorrow-ish
[15:29] <cyberix> Can I advertise project IRC channel in Launchpad?
[15:29] <mohbana> hello
[15:30] <mohbana> i'am slightly annoyed by launchpad, bugs are forwarded using a person's email add isntead of of say @bugs.launchpad.net
[15:30] <mohbana> see, i can't use gmail's filter now
[15:31] <stgraber> mohbana: just look at the XS- field in the mail
[15:31] <mohbana> stgraber: huh?
[15:32] <mohbana> have u tried using gmail's filters?
[15:33] <stgraber> nope but I guess a lot of other Launchpad users do
[15:46] <oubiwann> hey launchpadders, are you guys now using (or getting ready to use) windmill?
[15:46] <beuno> oubiwann, trying to
[15:47] <beuno> flacoste and mars, has been doing some work around it
[15:47] <oubiwann> beuno: how is it going?
[15:47] <beuno> oubiwann, I don't know the details, I do know "it has it's quirks"
[15:49] <oubiwann> beuno: Jamu mentioned it from the 2 week JS training he attended in the UK
[15:49] <mohbana> does anyone use gmail?
[15:49] <oubiwann> beuno: and today I noticed that there is a pycon proposal for it, so I was wondering how you guys felt about it so far
[15:49] <oubiwann> beuno: thanks for the notes :-)
[15:50] <beuno> oubiwann, yeap, we've been looking into different test frameworks for javascript
[15:50] <beuno> oubiwann, I'm sure flacoste or mars can give you some details when they're around
[15:50] <beuno> oubiwann, notes?
[15:50] <oubiwann> beuno: well, your comment
[15:51] <oubiwann> comment(s)
[15:51] <beuno> ah, :)
[15:56] <mohbana> well?
[16:01] <mohbana> hello
[16:10] <mars> oubiwann, hello.  yes, we are getting windmill ready to use for Launchpad JavaScript testing
[16:11] <oubiwann> mars: how has your experience with windmill compared to any similar experience with selenium?
[16:13] <mars> oubiwann, well, we ran a smoke test with the team recently - there was a lot of smoke, mostly resulting from the Intrepid upgrade, and people figuring out how the to run their tests.
[16:14] <rockstar> oubiwann, windmill > selenium.
[16:14] <mars> windmill also has some quirks we are looking into
[16:14] <oubiwann> rockstar: can you expand a little on that? any reasons in particular?
[16:15] <oubiwann> rockstar: API usage?
[16:15] <mars> for instance, re-running tests rapidly in succession blocks on "socket in use" errors, but that's because the UUID daemon steals the port after the Windmill server shuts down
[16:15] <oubiwann> mars: interesting
[16:16] <rockstar> oubiwann, less dependencies, less likely to fall over.  I integrated it into a Django project on my way back from London.  It was so simple.
[16:16] <mars> rockstar, our patched version with the Ubuntu Mozrunner fix? or the vanilla version?
[16:17] <oubiwann> mars: how public is the launchpad team about their use of windmill? is this something that can be shared? e.g., "Canonical's Launchpad team is currently using Windmill"
[16:17] <rockstar> mars, vanilla.  I had to write some custom stuff, but it was relatively easy.
[16:17] <oubiwann> mars: or a more couched statement like "Canonical's Launchpad team is currently considering using Windmill"
[16:17] <rockstar> oubiwann, yes, the windmill guys have been talking about it.  One of them is following my dents.
[16:18] <mars> rockstar, I'd love to see the custom stuff you wrote
[16:19] <rockstar> mars, okay.  I'm actually not working today (I'm exhausted)
[16:21] <mars> oubiwann, we're only in the early setup stages right now, integrating windmill into our own testrunners and code repositories.  But the plan is to use windmill for Launchpad JavaScript and site testing.
[16:21] <oubiwann> mars: awesome
[17:53] <jkakar> I'm having issues pushing a branch to Launchpad... any ideas?  http://paste.ubuntu.com/67421/
[17:55] <jkakar> leonardr: ^^ Any ideas?
[17:56] <leonardr> jkakar, looking
[17:56] <jkakar> leonardr: Ta.
[17:56] <leonardr> jkakar, the first two warning might herald the cause of the error. the server side uses a newer format than you're using. try bzr upgrade and see if that fixes it
[17:57] <jkakar> leonardr: I've tried Bazaar upgrade already, but maybe not in the way you mean?
[17:58] <jkakar> leonardr: I think the issue is that I'm using a rich-root repository locally and LP doesn't know how to talk to it.
[17:59] <leonardr> jkakar, that's possible. let me find someone on the code team
[17:59] <jkakar> leonardr: I'm trying to merge a branch from someone that uses rich-root format.  I might just generate a bundle and merge that if this is too hard. :)
[18:00] <leonardr> jkakar: try doing that for now, i'll ping you if i can get someone from the code team on the line
[18:01] <jkakar> leonardr: Thanks!
[18:02] <abentley> jkakar: Heya.
[18:03] <jkakar> abentley: Hey!
[18:03] <jkakar> abentley: I'm having fun with incompatible repository formats, it seems. :)
[18:04] <abentley> jkakar: I see, and I'm looking into it.
[18:04] <jkakar> abentley: Thanks.
[18:05] <abentley> jkakar: So it looks like your local branch uses rich-root and the launchpad copy does not.
[18:05] <jkakar> abentley: The issue is that I'm merging a branch from someone that uses rich-root.
[18:06] <jkakar> abentley: I've freshly branched trunk (non-rich-root), merged the branch in, and am now trying to push the changed trunk back to LP.
[18:06] <jkakar> abentley: I just tried to create a bundle and merge that but get the same kind of warning: http://paste.ubuntu.com/67428/
[18:07] <abentley> jkakar: In order to merge the branch in, you would have had to upgrade to rich-root.
[18:07] <jkakar> abentley: Will that create any problems or should I just do it?
[18:07] <jkakar> abentley: Once I upgrade to rich-root locally how will I push branches to LP?
[18:07] <abentley> jkakar: I'm not making a suggestion.  I'm trying to understand what happened.
[18:08] <jkakar> abentley: Ah, hehe. :)
[18:08] <abentley> You say you merged this person's rich root.
[18:08] <abentley> Did you upgrade in order to do that?
[18:09] <jkakar> I think so.  One sec, I'll see if I can get a full transcript of what I did so I'm not making things up.
[18:09] <abentley> I can't understand why pushing to lp would give that error otherwise.
[18:10] <jkakar> abentley: It's a bit noisy, but here's my full session thus far: http://paste.ubuntu.com/67430/
[18:10] <abentley> jkakar: bzr info -v will show your repository format.
[18:12] <abentley> jkakar: It looks like you did upgrade.
[18:12] <jkakar> abentley: Hmm, ~/tmp/visual is "Packs containing knits with rich root support" and ~/tmp/autoppa is "Knit repository format 4" (which is odd because I did upgrade).
[18:12] <abentley> So if you want to push to lp, you need to upgrade or delete the existing lp branch.
[18:13] <abentley> Knit repository format 4 is the repository format produced by "upgrade --rich-root"
[18:14] <abentley> jkakar: I prefer to avoid rich-root formats wherever possible.  They're only needed for bzr-svn.
[18:14] <jkakar> abentley: Ah, thanks.  I think I'll leave well enough alone for now and use a patch.  I don't really want to muck about with non-default formats.
[18:15] <jkakar> abentley: Yeah, the branches I'm merging are from jelmer. :)
[18:15] <abentley> jkakar: That would explain it :-)
[18:15] <jkakar> abentley: Thanks for your help.
[18:15] <abentley> jkakar: No problem.
[18:15] <jkakar> leonardr: Also, thanks.
[18:16] <leonardr> np
[20:41] <MTecknology> Hey, I'm trying to have my site use launchpad to log in. I only want users in the group to log in. afaik, that just means I need to create a single user account in my site and associate all their openid's to it. I have my login form at http://pastebin.com/m74176107. It seems to work excep that openid login always fails. I took that form from fridge.ubuntu.com...
[20:49] <fdr> please excuse me for the silly questions -- but where in launchpad can I see the list of bugs I've ever reported to ubuntu? I cant seem to find it. Thanks!
[20:51] <popey> fdr: http://bugs.launchpad.net/ and then login there is a link on the right - "reported by me"
[20:51] <fdr> under filters?
[20:51] <fdr> strange, i logged in, but i don't have that
[20:52] <fdr> (under  http://bugs.launchpad.net/ubuntu  )
[20:53] <fdr> The only filters i have are : Open, Assigned to me, Critical, New, Unassigned, All bugs ever reported
[20:56] <MTecknology> I'm guessing I'm REALLY close - I'm just missing a few things
[20:58] <cody-somerville> OOPS - 1039EC107
[20:58] <cody-somerville> OOPS 1039EC107
[20:59]  * cody-somerville pokes bot.
[21:02] <NCommander> cody-somerville, you post an oops and you get information about it?
[21:02]  * NCommander has never seen that feature before
[21:06] <cody-somerville> ugh
[21:06] <cody-somerville> i386 PPA buildds are backed up horribly :(
[21:07] <wgrant> cody-somerville: Your builds should be in front of the langpacks, I think.
[21:07] <wgrant> fdr: https://bugs.launchpad.net/people/+me/+reportedbugs
[21:08] <MTecknology> Anybody here know about using openid to log into a site w/o using their openid link?
[21:08] <fdr> wgrant, thanks very much, it works!
[21:09] <MTecknology> I know I want to pass things to https://login.launchpad.net/+decide - and I have most of the information there - idk what else to do though
[21:09] <fdr> wgrant, but is there a way to reach that page from the homepage by just following links? :)
[21:09] <wgrant> fdr: Click on your name in the top right, click on the bugs tab, click on "Reported bugs" or similar in the menu on the right.
[21:11] <fdr> wgrant, very kind, thank you!
[21:11] <wgrant> np
[21:11] <cody-somerville> wgrant, https://edge.launchpad.net/~cody-somerville/+archive/+build/756209 (estimated build start is two hours)
[21:12] <wgrant> cody-somerville: Ah, great.
[21:52] <MTecknology> AH :'(
[21:52] <MTecknology> Why does this no workie!? :'(
[21:54] <kiko> MTecknology, what doesn't work? IRC is working fine for me!
[21:54] <MTecknology> um?
[21:54] <MTecknology> h on
[21:54] <MTecknology> https://answers.edge.launchpad.net/launchpad/+question/50189
[21:55] <sawit> Identify sawit girlgeekdinners
[21:56] <MTecknology> kiko: any ideas?
[21:56] <lifeless> sawit: I think you want to tell that to 'nickserv' not a public channle
[21:56] <jbalint> hello!
[21:57] <lifeless> hmm, ubottu should learn about questions
[21:57] <MTecknology> lol
[21:57] <jbalint> i just pushed a branch, it hasnt been scanned yet after 15 minutes. normally takes 2. something slow today?
[22:01] <kiko> lifeless, leave the guy alone, he has enough problemas as it is