[00:00] <fta> it's GPL/LGPL/MPL
[00:00] <kiko> updated the project
[00:00] <fta> resp, 2/2.1/1.1
[00:00] <fta> kiko, thanks
[00:01] <kiko> fta, yeah. so, now that i've updated the project, you can visit https://bugs.edge.launchpad.net/prism/+bug/205782 and put the remote bug URL inside the Prism task
[00:01] <ubotu> Launchpad bug 205782 in prism "Window icon shoud  be site favicon" [Medium,Fix committed] 
[00:01] <kiko> fta, then we have the complete information there -- when and where it was fixed upstream, and what happened to it in ubuntu
[00:01] <kiko> fta, when the project is marked "doesn't use launchpad" the task form changes, and you can put in URLs to remote bugs there
[00:02] <fta> so I just have to select the remote bug now, right?
[00:03] <kiko> fta, well, the remote bug listed there is not the same number
[00:03] <kiko> fta, you said it was fixed by bug 400164
[00:04] <kiko> now, because you cited bug 410215 in a comment, we created a bug watch for it automatically
[00:04] <kiko> that's why it's offered as an option
[00:04] <fta> oh
[00:04] <kiko> right
[00:04] <fta> ok
[00:05] <fta> btw, it would be nice to be able to drop a project from a bug instead of marking it invalid. it would avoid the spam from unrelated comments
[00:05] <fta> (like for the 3rd bug)
[00:06] <kiko> fta, well, what if we said that you wouldn't get spammer for invalid bugs?
[00:06] <kiko> err, spammed?
[00:06] <kiko> because I'm in favor of that more than outright deletion of tasks
[00:09] <fta> well, if it's really a mistake, like a modem called Prism totally unrelated to the mozilla prism application, why would I ever want to follow the discussion about the modem ?
[00:10] <kiko> fta, you wouldn't -- with that I agree. but I'm suggesting solving that by making it so that, if the task was marked invalid, you wouldn't get spammed.
[00:10] <kiko> fta, what do you think of that?
[00:10] <mpt> It might be marked Invalid by accident, so it would need to be obvious to J Random Bug Commenter how to resubmit it for consideration
[00:10] <fta> yes, that would do perfectly
[00:11] <mpt> I don't see why we should send people notifications of comments on duplicate bug reports, but not notifications of comments on Invalid bug reports
[00:13] <kiko> mpt, duplicates /are/ relevant to the project, while invalids aren't. you could argue not to send duplicate mail, but the proper solution to that is to just disallow adding comments -- you don't wanna blackhole them, do you? those are, AAR, separate concerns.
[00:14] <mpt> How are duplicates relevant to the project?
[00:15] <fta> they may bring more information
[00:16] <mpt> In both cases, duplicate and Invalid, the status might be set by accident
[00:17] <kiko> mpt, that doesn't invalidate fta's point, which was mine as well.
[00:17] <fta> then what? just send the 1st mail saying that bug has been tagged invalid for project x then stop for all subscribers of x bugmails
[00:17] <mpt> That's why we allow comments on duplicates, so people can say "Hey, I don't think this is actually a duplicate", and their comments get mailed
[00:17] <kiko> either there's something we're missing, mpt, or you're crazy. :)
[00:18] <mpt> I think you're trying to make "Invalid" mean two different things that should have two different behaviors
[00:18] <mpt> (It would be fine if it meant two different things that should have the same behavior!)
[00:19] <mpt> Some people use Invalid when a bug used to exist, but has been rendered moot by subsequent changes
[00:19] <mpt> Some people use Invalid for a bug report that requests a change, when the maintainer thinks that change would be a bad idea
[00:20] <mpt> Those two cases are subject to discussion, so I think people should get mailed about them
[00:21] <mpt> I think "Dude, this is incomprehensible gibberish" and "Dude, you've filed this against totally the wrong software" are different cases
[00:21] <fta> for the later, it would be wontfix, no ?
[00:21] <mpt> and it may be worth handling them separately.
[00:22] <mpt> fta, in theory, but in practice people seem to use Invalid and Won't Fix interchangeably.
[00:22] <mpt> (In bug reports that I'm subscribed to, at least!)
[00:22] <fta> maybe because wontfix is not accessible to everyone..
[00:23] <mpt> Yeah, that wouldn't help
[00:23] <mpt> So one possible solution is to merge Invalid into Won't Fix, and introduce a new "Delete this" or similar status, that removes your software from the bug report completely.
[00:24] <mpt> (or just a Delete button next to each context in the table)
[00:24] <fta> for me, won't fix implies the project is right
[00:25] <kiko> mpt, ah, I hadn't considered the Invalid-means-something-else angle you're pointing out.
[00:26] <mpt> We have a lot of those because of bug 59389 and bug 80902
[00:26] <ubotu> Launchpad bug 59389 in malone "The possibility of retargeting a bug should be made more obvious" [Undecided,Confirmed] https://launchpad.net/bugs/59389
[00:26] <ubotu> Launchpad bug 80902 in malone "Allow bug retargeting from project to distribution, or vice versa" [Undecided,New] https://launchpad.net/bugs/80902
[00:27] <fta> oh, 80902 was what I wanted initially :)
[00:32] <kiko> yeah
[00:32] <kiko> agreed
=== kiko is now known as kiko-afk
=== lamont` is now known as lamont
[02:33] <mpt> ... But there's another case we might want to consider
[02:33] <mpt> For bugs reported about a distribution package (e.g. Ubuntu firefox), we want to record whether they occur upstream (e.g. in mozilla.org Firefox)
[02:34] <mpt> We might do that by saying "mozilla.org Firefox: Invalid"
[03:05] <lifeless> well
[03:05] <lifeless> I was just looking at a bug in bzr
[03:05] <lifeless> actually baz1.x but ignore the specific package  :)
[03:05] <lifeless> it was for network-manager
[03:06] <lifeless> someone insane marked it for baz1x at some point
[03:06] <lifeless> and there is no way to clean it up
[03:06] <lifeless> now every change made to it forever spams the baz1x maintainers
[03:06] <lifeless> this isn't to say that 'invalid' is the wrong approach; but there are related UI considerations
[03:06] <Fujitsu> We have had a number of upstreams complaining at us about bugs with several dozen tasks.
[03:07] <Fujitsu> They don't want to be notified of the bug, even if it's open.
[03:07] <Fujitsu> Or particularly if it's fixed in that task.
[03:12] <jamesh> lifeless: you can probably reassign that task to some other package
[03:12] <jamesh> that way it will be someone else's problem
[03:13] <mpt> I think bug 204906 is a duplicate, but I can't find the original, does anyone know it?
[03:15] <Fujitsu> Bug #204906
[03:21] <lifeless> jamesh: true, but still fugly. :{
[03:21] <lifeless> jamesh: perhaps I should assign it to launchpap-bugs :}
[04:30] <ubotu> New bug: #206339 in launchpad "Can't easily access bug reports recently visited from another browser" [Undecided,New] https://launchpad.net/bugs/206339
[05:18] <ping> Hello!  Would someone be willing to help me with a newbie question?
[05:22] <Fujitsu> !ask
[05:22] <ubotu> Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-)
[05:27] <ping> Thanks.  I am trying to start a new project named Factville.  I have registered the project and a new hosted branch (see https://code.launchpad.net/factville/).  Now I want to commit the first revision of my code.  I assumed that the way to do this would be to "bzr branch lp:factville" to get an empty directory, place my code in the directory, then "bzr commit" to commit locally and "bzr push" to send my code to Launchpad.  However, "bzr
[05:29] <jamesh> ping: you'll need to associate your branch with the release series
[05:30] <jamesh> oh.  you've already done that.
[05:30] <jamesh> ping: you'll need to do the following:
[05:31] <jamesh> (1) create a branch locally with "bzr init"
[05:31] <jamesh> (2) from that branch run "bzr push lp:factville" to upload it
[05:32] <jamesh> when you register a hosted branch through the web UI, it only reserves the name: it doesn't create the initial branch on the server
[05:32] <ping> Oh, I see.  Thanks.  I'll try that now.
[05:46] <ping> Great!  I successfully pushed the first revision.  Many thanks for your help!
[07:26] <carlos> morning
=== stu1 is now known as stub
=== \sh_away is now known as \sh
[09:01] <mpt> Gooooooooooooood evening Launchpadders!
[09:30] <T-R3xX> Who from Russia? =)
[09:59] <mpt> allenap, there's a question about bug notifications from Fernando in launchpad-users@
[09:59] <allenap> mpt: I'll go an check it out.
[09:59] <mpt> thanks :-)
[10:00] <mpt> He's talking about something as an "unannounced change", and then mentioning that he uses edge
[10:01] <mpt> which makes me realize that even if release notes were useful for people who aren't beta testers (which I doubt), they're too late for people who are.
[10:02] <allenap> mpt: intellectronica was doing some stuff with emails, but I can't say if he touched on this. He's afk at the moment, but I'll talk to him when he's online.
[10:02] <mpt> ok, ta
[10:02] <allenap> mpt: That's a good point.
[10:02]  * intellectronica looking
[10:03] <mpt> That might be a further incentive to think about how to announce changes in the UI itself :-) 
[10:03] <allenap> Personally, I'd like a news feed of changes in edge that aren't in prod. A trickle as things get committed.
[10:04] <allenap> With something more explanatory than commit messages :)
[10:06] <intellectronica> looks like this may be related to bug #138696 and other bugs for including more info in the header of the mail. looks like a useful feature to me
[10:06] <ubotu> Launchpad bug 138696 in malone/1.2 "bug tags do not appear in e-mail headers" [Undecided,Fix committed] https://launchpad.net/bugs/138696 - Assigned to Graham Binns (gmb)
[10:08] <Fujitsu> I've been wondering something for a while... Do all actions performed on edge send out edge-style emails to everyone?
[10:08] <Fujitsu> Or do people not in lp-b-t get them from production?
[10:09] <mpt> I'd like a news feed of changes that are in production. :-) That way I can learn one new thing each day.
[10:13] <allenap> Fujitsu: I *think* some email are generated directly during the web request, in which case they'll come from edge, and others are generated separately, in which case they'll come from production. But I'm probably wrong :) BjornT: ^^^?
[10:13] <Fujitsu> allenap: The batched ones will *all* come from production, even to lp-b-t members?
[10:15] <allenap> Fujitsu: I guess so. I don't know of any separation of recipients into beta and non-beta for batch messages.
[10:18] <allenap> intellectronica: I don't think gmb's fix for bug 138696 would cause the changes that Fernando has seen. I'm going to look further...
[10:18] <ubotu> Launchpad bug 138696 in malone/1.2 "bug tags do not appear in e-mail headers" [Undecided,Fix committed] https://launchpad.net/bugs/138696 - Assigned to Graham Binns (gmb)
[10:20] <intellectronica> allenap: it could also be related to the one of the attachment bugs abel fixed. i must admit that i don't really know what is it that fernando is getting, so it's a bit hard to guess what caused it
[10:21] <allenap> intellectronica: Yeah, it's a bit vague. I'll look at abel's stuff now.
[10:23] <Fujitsu> I believe he's referring to the fact that emails now contain an X-Launchpad-Bug header for each task.
[10:25] <Fujitsu> Oh.
[10:25] <Fujitsu> It's done that forever.
[10:25] <Fujitsu> So maybe not.
[10:25] <allenap> :)
[10:25] <intellectronica> that's not new
[10:25] <Fujitsu> I guess I only noticed it recently, as I'm subscribed to two newish bugs with several dozen tasks.
[10:27] <intellectronica> right, and if it isn't properly documented then we should definitely correct this
[10:34] <Fujitsu> How're continous Debian bug imports coming along? They were originally targetted ~1.1.9, IIRC.
[10:41] <rexbron> jkakar: Did you get my message?
[10:43] <BjornT> Fujitsu: it's progressing quite slowly. technically seen, a lot of things have been done. but it's blocked on seeing how this works for other bug trackers, and discussion with the debian guys.
[10:47] <Fujitsu> BjornT: Aha.
[10:47] <Fujitsu> Version tracking would make it particularly useful, but I suppose that's still not planned to ever go ahead?
[10:53] <\sh> hmm...possible to disable email notifications for packages which are marked invalid in a bug report? :)
[10:53] <\sh> e.g. bug #103378
[10:53] <ubotu> Launchpad bug 103378 in ubuntu "impossible mount floppy device in /media" [Undecided,Confirmed] https://launchpad.net/bugs/103378
[10:53] <Fujitsu> \sh: There're bugs on that.
[10:53] <\sh> Fujitsu: good then :)
[10:54] <Fujitsu> Bug #204980
[10:54] <ubotu> Launchpad bug 204980 in malone "bug contacts should be able to unsubscribe from implicit subscriptions" [Medium,Confirmed] https://launchpad.net/bugs/204980
[11:27] <ubotu> New bug: #206467 in malone "Allow generation of tokens, which can be used to login to remote bug trackers" [Undecided,New] https://launchpad.net/bugs/206467
[11:27] <ubotu> New bug: #206471 in meta-lp-deps "add psycopg2 to launchpad-dependencies" [Undecided,New] https://launchpad.net/bugs/206471
[11:35] <BUGabundo> hi there
[11:35] <BUGabundo> is gavin or travis here?
[11:37] <intellectronica> BUGabundo: gavin is allenap. do you have more info for us about the change you talked about on the list?
[11:37] <allenap> BUGabundo: Hi :)
[11:38] <BUGabundo> yep
[11:38] <BUGabundo> just reporting back
[11:38] <intellectronica> excellent!
[11:38] <BUGabundo> just sent an email with an attach
[11:38] <BUGabundo> look at the bottom of the attached emai
[11:38] <BUGabundo> *email
[11:38] <BUGabundo> and you guys will know what I mean
[11:39] <BUGabundo> it doesn't bother me a bit, actually I'm trying to do exactly the same with our TRAC instalation lol
[11:39] <allenap> BUGabundo: I guess you mean where it says "Status in ..." and the bug description.
[11:40] <BUGabundo> yep
[11:40] <BUGabundo> If I recall, that wasn't sent last week
[11:40] <BUGabundo> so it's a new feature, right?
[11:40] <intellectronica> BUGabundo: i don't think that's new. we've been doing this for a while
[11:40] <intellectronica> let me try and find the relevant bug
[11:41] <BUGabundo> do worry, intellectronica
[11:41] <Fujitsu> I can't see any recent bugmail that does that. It's the first I've seen of it.
[11:41] <BUGabundo> I've seen in EVERY bug I get from LP
[11:41] <BUGabundo> [Bug 200338] Re: no sound hardy kernel 2.6.24-12 has it
[11:41] <ubotu> Launchpad bug 200338 in linux "no sound hardy kernel 2.6.24-12 " [Critical,Fix released] https://launchpad.net/bugs/200338 - Assigned to Ben Collins (ben-collins)
[11:42] <BUGabundo> [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx) too
[11:42] <ubotu> Launchpad bug 129910 in linux "Blank ttys when using vesafb (vga=xxx)" [Medium,Fix released] https://launchpad.net/bugs/129910 - Assigned to Ben Collins (ben-collins)
[11:42] <Fujitsu> Ahh.
[11:42] <Fujitsu> It's on +edit.
[11:42] <BUGabundo> every single email I get, has the bottom part
[11:42] <Fujitsu> Per-person.
[11:42] <Fujitsu> When did that feature appear!?
[11:44] <BUGabundo> Friday or thurday
[11:45] <Fujitsu> BUGabundo: Did you turn it on on your `Change details' page?
[11:45]  * Hobbsee waves to allenap
[11:45]  * Fujitsu finds a mention of it deep in 1.2.1's release notes.
[11:45]  * allenap waves at Hobbsee :)
[11:46] <Fujitsu> I would have thought it would be in the highlights. That's approximately the best thing since sliced bread.
[11:47] <Hobbsee> what is?
[11:47] <Fujitsu> The one user-configurable option that changes Launchpad behaviour noticably.
[11:47] <BUGabundo> I might, Fujitsu
[11:47] <BUGabundo> where do I see that?
[11:47] <Fujitsu> https://launchpad.net/people/+me/+edit
[11:48] <Fujitsu> Hobbsee: It shows the bug description and current statuses in the various tasks at the bottom of each piece of bugmail.
[11:49] <Fujitsu> Makes bugs that don't have the package name in their summary a little more usable over email.
[11:49] <BUGabundo> Fujitsu: don't remember have been there, last week
[11:49] <Hobbsee> oh, neat.
[11:50] <Fujitsu> I bet there's no way to do that for mail sent to a team address, though.
[11:50]  * Hobbsee again wonders why she's getting all this invalid bug mail, and how to stop it.
[11:50] <Fujitsu> Hobbsee: Hahahahaha you're trapped.
[11:50] <Fujitsu> No escape from bugmail.
[11:50] <Hobbsee> \sh: i want that too.  good luck
[11:50] <BUGabundo> I was trying to upload a new avatar, and got strange erros
[11:50] <BUGabundo> *errors
[11:50] <Hobbsee> oh, it was discussed
[11:50] <Fujitsu> A number of upstreams are quite irritated at the MBFs.
[11:51] <BUGabundo> so could it be that LP also changed that setting ?
[11:51] <ubotu> New bug: #206488 in meta-lp-deps "add libxml2-utils to launchpad-dependencies" [Undecided,New] https://launchpad.net/bugs/206488
[11:51] <BUGabundo> what is MBF?
[11:51] <Fujitsu> As they really, really don't care about the other 50 packages that FTBFS due to python-central craziness.
[11:51] <Fujitsu> BUGabundo: Mass bug filing.
[11:51] <BUGabundo> ah thanks
[11:51] <Hobbsee> funny how we have at least 3 people complaining about it in 24 hours.
[11:52] <Fujitsu> allenap: Do you know why that option isn't on the email settings page?
[11:52] <Fujitsu> That would seem to be a more sensible place to put it.
[11:53] <Fujitsu> It would be even better to have it on the Malone-specific config page that should be at https://bugs.launchpad.net/people/+me, but there are for some reason no other configuration options.
[11:53] <Hobbsee> mine is just the java bugs.
[11:53] <Hobbsee> i wonder if can filter for the text "java" plus "invalid"
[11:53] <Hobbsee> or just filter everything that's invalid to start with.
[11:53] <allenap> Fujitsu: No, does seem a bit daft. Are you happy to file a bug about it?
[11:53] <Fujitsu> allenap: Sure.
[11:54] <Fujitsu> launchpad? Or is it still malone?
[11:54] <BUGabundo> can the avatar system be better funcional?
[11:55] <Fujitsu> BUGabundo: What's dysfunctional about it?
[11:55] <BUGabundo> all those RED warnings while trying to change an image scare users
[11:55] <BUGabundo> I just gave up...
[11:55] <Fujitsu> They were probably valid warnings...
[11:55] <BUGabundo> I was trying to upload a new avatar
[11:55] <Hobbsee> BUGabundo: the avator system is more annoying than that.
[11:55] <BUGabundo> and it wouldn't let me
[11:55] <Fujitsu> So scaring the user is probably advisable.
[11:55] <BUGabundo> because of the size
[11:55] <Hobbsee> BUGabundo: if you don't get hte scale exactly right, launchpad won't scale it for you, it just barfs.
[11:55] <Fujitsu> Rightly so.
[11:56] <BUGabundo> that's the prob
[11:56] <BUGabundo> it should scale it for us...
[11:56] <Hobbsee> iirc, i filed a bug back in uds sevilla.  no response, yet.
[11:56] <BUGabundo> GD lib does that quite well
[11:56] <Hobbsee> BUGabundo: i think the problem is a lack of interest in fixing it, combined wiht other more important things to fix.
[11:57] <BUGabundo> I know
[11:57] <BUGabundo> but user interaction and personalization is something really importatnt
[11:57] <BUGabundo> makes users willing to participate...
[11:57] <BUGabundo> and we going to have a new Ubuntu release soon, so more NEW users will come to LP
[11:58] <BUGabundo> scaring them that way, for such a small feature like avatar or personalisation is a bad thing
[11:58]  * Hobbsee could justify hundreds of bug fixes with that line....it won't work.
[11:58] <BUGabundo> eheh Hobbsee
[11:58]  * Hobbsee has learnt well, and no longer complains about it.  it's just the way it is.
[12:01] <Fujitsu> Night all.
[12:01] <BUGabundo> g'night Fujitsu
[12:01] <Fujitsu> BUGabundo: Thankyou for pointing that feature out! It will be most useful to me.
[12:02] <BUGabundo> 12h00 here
[12:02] <BUGabundo> lolol
[12:02] <BUGabundo> no prob Fujitsu
[12:02] <BUGabundo> it was new to me
[12:02] <BUGabundo> but I don't recall activating it
[12:02] <BUGabundo> although I like it
[12:02] <Hobbsee> night Fujitsu 
[12:03] <Fujitsu> Night Hobbsee, BUGabundo.
[12:10] <ubotu> New bug: #206496 in malone "Setting to include descriptions in bugmail should be on +editemails, not +edit" [Undecided,New] https://launchpad.net/bugs/206496
[12:20] <BUGabundo> let me subs to that...
[12:21] <BUGabundo> humm is ubotu to perfome actions for us on irc?
[12:21] <BUGabundo> like if I wanted to subscrive bug #206496, I could instrut it too
[12:21] <ubotu> Launchpad bug 206496 in malone "Setting to include descriptions in bugmail should be on +editemails, not +edit" [Undecided,New] https://launchpad.net/bugs/206496
=== mrevell is now known as mrevell-luncheon
[12:37] <salty-horse> hi. I added a link with "Also affects project" and then it selected the original bug's project as the external bug's project name. then I changed the assigned project for the original bug, but I don't see a way of changing the external bug's project name: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/205314
[12:37] <ubotu> Launchpad bug 205314 in xorg "layout switching with both alt keys doesn't work" [Undecided,New] 
=== mrevell-luncheon is now known as mrevell
[12:55] <ubotu> New bug: #206508 in launchpad-bazaar "Associating branches with tasks" [Undecided,New] https://launchpad.net/bugs/206508
[12:56] <Hobbsee> morning mrevell 
[12:56] <mrevell> hey Hobbsee
[12:56]  * Hobbsee wonders why someone is blogging to planet ubuntu about why launchpad should become open source
[12:56] <Hobbsee> d
[12:57]  * soren wonders why Hobbsee wonders that
[12:58] <Hobbsee> soren: sounds like a bad target audience to me.  are the launcphad guys, for the most part, ubuntu people?
[12:58] <Hobbsee> as in, likely to read planet?
[13:08] <soren> Hobbsee: I certainly wouldn't be surprised if they did.
[13:08]  * Hobbsee thougth they had too much work to do for that, or something.
=== barry-away is now known as barry
[14:11] <ubotu> New bug: #206541 in malone "Bug tags should be listed in X-Launchpad-Bug-Tags instead of in each X-Launchpad-Bug header" [High,Triaged] https://launchpad.net/bugs/206541
[14:16] <ubotu> New bug: #206544 in malone "Bug feeds performance improvements" [Undecided,New] https://launchpad.net/bugs/206544
=== kiko-afk is now known as kiko
[14:43] <jkakar> rexbron: Hey!
[14:44] <jkakar> rexbron: I did get your message, but you were offline at the time.  As far as AutoPPA being useful, it's not in it's current state, but it sounds like it could be made to.  The issue is that it currently only works with projects that use Bazaar.
[14:45] <jkakar> That said, for my purposes it works very well.  It's a bit of pain to install/setup (mostly because of dependencies), but once it's there firing off builds is typically one command and then a few minutes of waiting while PPA does it's thing.
=== \sh is now known as \sh_away
=== \sh_away is now known as \sh
[15:42] <bahadunn> hello
[15:43] <qense> hi
[15:43] <bahadunn> is launchpad open?
[15:44] <qense> yes
[15:44] <qense> it should be
[15:44] <kiko> open for business!
[15:44] <LarstiQ> ding dong!
[15:44]  * kiko winks at LarstiQ 
[15:44] <LarstiQ> hai kiko :)
[15:47] <bahadunn> I mean open source?
[15:48] <qense> partially
[15:48] <bahadunn> so what part is open that anyone can contribute to?
[15:48] <kiko> bahadunn, launchpad.net/launchpad-cscvs is open
[15:49] <kiko> bahadunn, and there are storm and zope3 bugs that need fixing, if you'd like to contribute
[15:49] <bahadunn> okay thanks
[16:12] <synic> when you request translations to download, how long does it usually take to get the email?
=== matsubara is now known as matsubara-lunch
=== matsubara-lunch is now known as matsubara
=== \sh is now known as \sh_away
=== kiko is now known as kiko-fud
=== salgado is now known as salgado-lunch
=== mrevell is now known as mrevell-dinner
=== matsubara is now known as matsubara-lunch
[17:52] <synic> how do I get ppa to build for hardy?
=== javamaniac_ is now known as javamaniac
[18:04] <cgregan> Is there a way to have launchpad format a listing of bugs into a more printable format?
[18:15] <synic> where do I ask PPA questions?
[18:16] <synic> is anyone here?
=== matsubara-lunch is now known as matsubara
[18:20] <synic> kiko-fud: ?
=== salgado-lunch is now known as salgado
[18:24] <matsubara> cgregan: nope. there are tools to scrape launchpad, though
[18:28] <synic> can I ask ppa questions here? https://answers.launchpad.net/launchpad
[18:29] <matsubara> synic: https://answers.edge.launchpad.net/soyuz/
[18:29] <matsubara> or ask here in the channel and someone might answer it :-)
[18:31] <synic> crap, already asked here: https://answers.edge.launchpad.net/launchpad/+question/27968
[18:32] <synic> should I re-ask on soyuz?
[18:32] <matsubara> synic: nope, I can re-target
[18:32] <synic> k
[18:33] <synic> don't suppose you might know the answer to that question?
=== kiko-fud is now known as kiko
[18:37] <kiko> synic, what's your dput.cf?
[18:38] <synic> http://rafb.net/p/Rkzy5n36.html
=== fta_ is now known as fta
[18:50] <smagoun> Need some help from a LP admin. I uploaded a package to a PPA, deleted it from the PPA, and tried to upload a new revision with the same version number. LP says no, there's an MD5 sum mismatch with a file already in the archive. I need the old, incorrect version really gone (isn't that what 'delete' is supposed to do?)
[18:51] <smagoun> PPA is Ubuntu Mobile: https://edge.launchpad.net/~ubuntu-mobile/+archive , the package in question is samsung-q1-ultra-config-0.30-0ubuntu1~804um1
[18:55] <kiko> synic, hmmm. bigjools, do you know the answer to synic's question above? ^^
[18:55] <kiko> smagoun, yes, delete does that, but it's slightly hard to actually predict its behaviour. have you read the help tab in the delete packages page?
[18:56] <kiko> smagoun, I should say, though, that an .orig tarball's version /is/ significant
[18:58] <smagoun> kiko: I hadn't read the help tab, thanks. Didn't even know it existed until now. Can't say it solved my problem, just explained to me what happened.
[18:59] <smagoun> kiko: The md5sum on the orig tarball isn't the problem (it hasn't changed), it's the md5sum on the diff.gz.
[19:00] <smagoun> (and the .dsc, probably)
[19:00] <kiko> smagoun, oh. that's really weird.
[19:06] <timlinux> hi
=== neversfelde_ is now known as neversfelde
[19:35] <ubotu> New bug: #206739 in rosetta "Changed messages are skipped when reverting changes and saving" [Undecided,New] https://launchpad.net/bugs/206739
[19:58] <mpt> Goooooooooooood morning Launchpadders!
=== neversfelde_ is now known as neversfelde
[20:20] <kyleN> we have a private project. we want to expose some bugs to a person who is not a member of the project, either by tagging, perhaps, or "also affects" their project, or by some other means. Is there a way?
[20:30] <ubotu> New bug: #206780 in launchpad "Display the posting address of a mailing list on the team overview page" [High,Confirmed] https://launchpad.net/bugs/206780
[20:33] <synic> kiko: ok, that question was answered - thank you.  I was wondering, how can I get it to build for both gutsy and hardy?
[20:34] <kiko> synic, IIRC you need to update the changelog
[20:35] <synic> ok.  That won't override the package I just uploaded?
[20:35] <synic> er... overwrite
[20:35] <ubotu> New bug: #206782 in launchpad "Yellow bug summary should include a link to milestone" [Undecided,New] https://launchpad.net/bugs/206782
[20:40] <kyleN> sorry for the dup, but this is urgent: we have a private project. we want to expose some bugs to a person who is not a member of the project, either by tagging, perhaps, or "also affects" their project, or by some other means. Is there a way?
[20:40] <ubotu> New bug: #206783 in launchpad "mailman keys are missing from the shared confs " [Critical,Confirmed] https://launchpad.net/bugs/206783
[20:44] <kiko> synic, packages are never overwritten, but you'll also need to rev the version
[20:45] <synic> like ~hardyppa1 or something?
[21:16] <kiko> synic, I'm not 100% sure what the conventions are. I meant to ask somebody about this yesterday and forgot, will have to do so tomorrow
[21:23] <warren> https://code.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk  Hi, our tree currently doesn't support "bzr tag".  Does launchpad support --dirstate-tags?  Are there any issues in converting the format and pushing?
[21:29] <ubotu> New bug: #206811 in malone "Bug feeds for BugTargets need to ensure a sufficient number of bugs are fetched" [Undecided,New] https://launchpad.net/bugs/206811
[21:38] <kiko> warren, hmmm, are you asking if we support packs? thumper's the best guy to answer.
[21:38] <warren> kiko, I don't know what are packs?
[21:38] <warren> kiko, I want to convert my bzr repo at the above URL to --dirstate-tags so I can use bzr tag.
[21:38] <kiko> thumper,  ^^^
[21:42] <jml> warren: bzr upgrade sftp://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk 
[21:51] <RAOF> warren: The caveat would be: this means that anyone trying to branch ltsp-trunk needs to have bzr >= 0.92, which isn't in Gutsy (but is in backports, and is in the bzr PPA).
[21:52] <warren> RAOF, that's the only caveat?
[21:52] <warren> RAOF, how old is Gutsy?
[21:52]  * warren thought --dirstate-tags was older than 0.92
[21:52] <RAOF> warren: Ubuntu 7.10, the most recent stable release.
[21:52] <warren> Fedora had --dirstate-tags by default since we began shipping bzr
[21:52] <jml> RAOF: you might be thinking of packs.
[21:53] <RAOF> warren: bzr upgrade sftp://whatever will take you to... Yeah, packs-0.92, which obviously requires 0.92 :)
[21:53] <warren> --dirstate-tags == packs?
[21:53] <jml> warren: no.
[21:53] <warren> --dirstate-tags is all I need for bzr tag right?
[21:53] <jml> warren: yep :)
[21:54] <warren> OK, so what version of bzr introduced --dirstate-tags?
[21:54] <RAOF> bzr help upgrade says 0.15.
[21:55] <warren> what version of bzr does gutsy have?
[21:56] <warren> what benefits does pack-0.92 give you?
[21:57] <warren> performance?
[22:02] <RAOF> warren: Reading from the website linked to by bzr help formats, but with no real understanding of bzr internals, the answer seems to be "smaller, faster, compatible with more ftp servers".
[22:05] <ubotu> New bug: #206826 in malone "Can't switch virtual terminals from laptop to external monitor" [Undecided,New] https://launchpad.net/bugs/206826
[22:07] <warren> RAOF, any idea what version of bzr is running on launchpad itself?
[22:08] <Fujitsu> warren: I believe it's pretty much always the latest stable.
[22:09] <warren> http://bazaar-vcs.org/BazaarFormats hm.. this page needs updating?  --dirstate-tags of 0.15 is mentioned as the latest.
[22:10] <jml> warren: https://code.launchpad.net has the Bazaar version that we use.
=== salgado is now known as salgado-afk
[22:14] <Fujitsu> That tag cloud is getting fairly useless.
=== barry is now known as barry-away