=== matsubara is now known as matsubara-dinner
=== matsubara-dinner is now known as matsubara
[00:51] <Verterok> intellectronica: the searchTasks feature in launchpadlib looks gooood :), nice job!
[01:05] <intellectronica> thanks, Verterok!
[01:09] <wgrant> intellectronica: Good to see that issue was fixed so quickly. Thanks.
[01:09]  * intellectronica wonders if the compliments always start that late
[01:09] <intellectronica> i obviously go to sleep too early most nights :D
[01:09] <wgrant> Heh.
[01:10] <intellectronica> wgrant: thanks for the help testing it, b.t.w
[01:10] <wgrant> intellectronica: Um, sure.
[01:11] <intellectronica> and now ...
[01:11]  * intellectronica --> zzz
[01:11] <wgrant> Night.
[03:40] <Peng_> jml: Ping?
[03:40] <jml> Peng_: howdy
[03:41] <Peng_> jml: Hi. :D
[03:41] <jml> ('Peng: pong' would have been simply too much fun.)
[03:41] <Peng_> :)
[03:42] <Peng_> Hm
[03:43] <Peng_> jml: So...I have a knit branch, lp:~mnordhoff/pytz/pytz-2008f. LP was finally able to mirror it over bzr+http, and then... it complains about a missing revision. Any idea?
[03:44] <Peng_> "bzr check" reports a ghost and "1 revisions missing parents in ancestry", but the revision in question is present.
[03:44] <jml> Peng_: well, the idea that's bouncing around in my head like a pinball is that it's a bzr bug.
[03:45] <jml> Peng_: also, I've seen other cases where that error shows up when it shouldn't.
[03:45] <Peng_> Huh.
[03:46] <Peng_> Hmm, when did "AssertionError: <bzrlib.bzrdir.BzrDirMeta1 object at 0x95c4a0c> is not a RemoteBzrDir" happen? That's on one of my older branches that hasn't been mirrored in ages.
[03:46] <Peng_> Oh, 2008-08-01.
[03:46] <jml> yay logs :)
[03:47] <jml> Peng_: can you request another mirror?
[03:47] <Peng_> Yeah, I am.
[03:47] <Peng_> Wait, another mirror of which branch?
[03:48] <jml> the one with the AssertionError.
[03:48] <Peng_> OK. Yeah, I am then.
[03:48] <Peng_> It's going now.
[03:51] <Peng_> Ooh, done.
[03:51] <Peng_> It's complaining about the missing revision now too. (It's lp:~mnordhoff/pytz/pytz-2008e, the parent of the other branch.)
[03:57] <Peng_> Hey, it was able to mirror one of my pack branches from another project. At least something works. :P
[04:09] <Peng_> LP has no problem mirroring a pack copy of the branch that has the revision error.
[04:10] <tgm4883_laptop> Is there something special I need to do to get the launchpad janitor to auto expire bugs in my project?
[04:12] <beuno> tgm4883_laptop, you have to specify it in your project's details
[04:12] <beuno> so, go to your projects overview page
[04:12] <beuno> and click on "Change details"
[04:12] <wgrant> Is that under bugs.lp.net yet?
[04:12] <beuno> nope
[04:13]  * wgrant imagines "X bugs can expire (!)"
[04:13] <wgrant> With the (!) being the edit icon.
[04:13] <beuno> sure, unless you really don't want them to
[04:13] <beuno> you keep on seeing that anyway
[04:13] <wgrant> Hm?
[04:14] <beuno> if you don't want bugs to expire
[04:14] <beuno> you would see that message all the time
[04:14] <wgrant> You do already, don't you?
[04:14] <beuno> do you?
[04:14]  * beuno looks
[04:15] <beuno> you do!
[04:15] <Peng_> Heh, "This branch may be out of date, as Launchpad has not been able to access between 2008-06-30  and 2008-07-04."
[04:15] <beuno> edit icon would be nice then  :)
[04:15] <wgrant> beuno: Good, so I wasn't going crazy.
[04:15] <beuno> wgrant, no, I am
[04:16] <tgm4883_laptop> beuno, it is
[04:16] <wgrant> Heh.
[04:17] <tgm4883_laptop> beuno, that is set, yet some bugs are way old
[04:17] <wgrant> tgm4883_laptop: Which is a bug that you think should have been expired?
[04:17] <tgm4883_laptop> sec
[04:18] <tgm4883_laptop> bug 151612
[04:18] <ubottu> Launchpad bug 151612 in mythbuntu "Remote not supported" [Wishlist,Incomplete] https://launchpad.net/bugs/151612
[04:18] <tgm4883_laptop> for instance, that one
[04:19] <tgm4883_laptop> we had one that was 262 days old that was marked for expiration, but someone marked it invalid
[04:19] <Ursinha> hey danilo[home]__, you there?
[04:19] <tgm4883_laptop> lp also lists 32 bugs that can expire
[04:21] <wgrant> beuno: Hmm, I guess that wouldn't actually work.
[04:22] <wgrant> It's not shown when there are no expirable bugs.
[04:22] <wgrant> Which happens both when there are no incomplete bugs untouched for 60 days, or if expiry is turned on.
[04:22] <wgrant> But it seems that expiry doesn't work too well.
[04:22] <beuno> BjornT, ping?  ^
[04:31] <Peng_> How many branches are mirrored at once?
[04:38] <thumper> Peng_: up to 10
[04:38]  * thumper thinks
[04:38] <thumper> maybe 4
[04:38] <thumper> can't remember
[04:40] <mwhudson> 4
[04:42] <jml> you know what would be good?
[04:42] <jml> metrics.
[04:43] <jml> lots of metrics.
[04:43] <Peng_> I just got it t ouse 8.72 Mbit of bandwidth. :)
[04:43] <Peng_> to use*
[04:44] <Peng_> Is it supposed to be able to mirror rich-root-pack branches?
[04:46] <mwhudson> yes
[04:47] <Peng_> Well it can't.
[04:47] <Peng_> "KnitPackRepository('lp-mirrored:///~mnordhoff/bzr-svn/new-style-classes/.bzr/repository') is not compatible with ..."
=== beuno_ is now known as beuno
=== thekorn_ is now known as thekorn
=== Hobbsee` is now known as Guest34533
=== Guest34533 is now known as Hobbsee
[09:28] <krokosjablik> Hello, I cannot change the project name myself, is it right? I have asked for this in Launchpad answers just now, is it the right place for such requests? Thanks.
[09:28] <wgrant> krokosjablik: That's the right place.
[09:29] <krokosjablik> wgrant: Many thanks!
=== mdz_ is now known as mdz
=== mrevell is now known as mrevell-lunch
=== salgado-afk is now known as salgado
=== mrevell-lunch is now known as mrevell
[13:41] <jjesse> good morning, i'm sure you all know about it already, but logging into launchpad this morning w/ konqueror on intrepid i get a message about the google map api key being rejected?
[13:41] <mars> salgado, ^
[13:42] <jjesse> salgado: i get the error message on both edge and launchpad
[13:43] <salgado> jjesse, bug 271613
[13:43] <ubottu> Launchpad bug 271613 in launchpad-foundations "Google Maps API Key Error" [Undecided,New] https://launchpad.net/bugs/271613
[13:43] <jjesse> ah ok, i wanted to make sure someone hadn't already reported it before i filed something
=== bac_afk is now known as bac
[13:57] <pro-rsoft> Hey, when I click Propose as goal it immediately gets marked as "Accepted for x.x.x" instead of "Proposed". How to mark something as Proposed but not Accepted?
[14:08] <pro-rsoft> or isnt that possible?
[14:10] <Hobbsee> pro-rsoft: it's not possible, as far as I know - but should you be able to set those anyway?
[14:10] <pro-rsoft> should I register an account that is not admin and propose it there? is that the only way?
[14:11] <Hobbsee> i'd sya so
[14:11] <pro-rsoft> hmm.
=== thekorn_ is now known as thekorn
[15:06] <jmota>  can anyone tell me why the icons in the top pannel(date, end session, sound...) sometimes get out of the place when i iniciate ubuntu?
=== salgado is now known as salgado-brb
=== salgado-brb is now known as salgado
=== mdz_ is now known as mdz
=== henninge_ is now known as henninge
[16:36] <andrea-bs> Hello! https://launchpad.net/launchpad says "See https://edge.launchpad.net/launchpad-project for details..."
[16:36] <andrea-bs> the problem is that the url includes "edge"
[16:38] <tgm4883_laptop> andrea-bs, that would be for launchpad beta testers
[16:39] <andrea-bs> tgm4883_laptop: I don't think so: I see non-edge links on https://launchpad.net/launchpad-project
[16:39] <tgm4883_laptop> andrea-bs, go to https://launchpad.net/ and turn off redirection
[16:40] <andrea-bs> tgm4883_laptop: the "edge" still be there
[16:41] <tgm4883_laptop> andrea-bs, if you turn off redirection, then go to https://launchpad.net/launchpad-project it should be fine
[16:42] <tgm4883_laptop> that will only last for 2 hours though, but this is just to prove that it's fine anyway
[16:42] <tgm4883_laptop> you could also log out and go to https://launchpad.net/launchpad-project
[16:44] <andrea-bs> tgm4883_laptop: sorry, I mean: the link in the page https://launchpad.net/launchpad include the "edge"; this is OK for betatesters, but not for other people
[16:44] <andrea-bs> -See https://edge.launchpad.net/launchpad-project for details on the other components that make up the project.
[16:44] <andrea-bs> +See https://launchpad.net/launchpad-project for details on the other components that make up the project.
[16:44] <rockstar> andrea-bs, why is not good for other people?
[16:45] <tgm4883_laptop> andrea-bs, the edge site only shows up for betatesters
[16:45] <tgm4883_laptop> regular users don't get the redirection
[16:45] <andrea-bs> rockstar: for example if they go to edge.lp.net/launchpad-project and click on "report a bug" they need to login an another time
[16:45] <rockstar> I mean, I see what you're saying, but it's not a huge issue.
[16:45] <andrea-bs> rockstar: sure
[16:46] <tgm4883_laptop> i'm not sure I understand
[16:48] <tgm4883_laptop> non beta testers never see the edge link
[16:48] <andrea-bs> it's just a small typo in the url: launchpad.net should be "standard", not "edge.lp.net"
[16:48] <tgm4883_laptop> it is
[16:48] <tgm4883_laptop> unless you are a beta tester
[16:48] <tgm4883_laptop> which I thought was what you were trying to say
[16:48] <andrea-bs> I'm talking about the project summary of lp.net/launchpad
[16:48] <rockstar> andrea-bs, are you on the beta testers team?
[16:48] <andrea-bs> rockstar: yes, I am
[16:49] <tgm4883_laptop> and you are worried that non beta testers will see the edge link?
[16:49] <rockstar> That's why then.  It would show the link differently if you weren't.
[16:49] <andrea-bs> tgm4883_laptop: no, of course
[16:49] <tgm4883_laptop> then......i'm confused
[16:50] <andrea-bs> rockstar: but if I log out I still see "edge" in the summary
[16:50] <andrea-bs> the link has been set in https://launchpad.net/launchpad/+edit
[16:50] <tgm4883_laptop> ah I get it now
[16:50] <andrea-bs> that's why it includes edge for everyone
[16:50] <rockstar> andrea-bs, ah, I see the link you're talking about.
[16:50] <tgm4883_laptop> so edit it and remove the edge part
[16:52] <mpt> hm
[16:52] <mpt> I've forgotten what "focus of development" means
[16:52] <mpt> Anyone know?
[16:53] <tgm4883_laptop> mpt, that would be where all of the development is focused?
[16:53] <mpt> Yes, what does that mean?
[16:53] <tgm4883_laptop> it's were most of the projects development is taking place
[16:53] <tgm4883_laptop> ie, trunk
[16:54] <tgm4883_laptop> or for ubuntu, it's intrepid
[16:54] <mpt> It can't just mean trunk, because projects have a "trunk" series by default
[16:54] <mpt> and yet it's still possible to change "development focus" to a different series
[16:55] <mpt> salgado, do you know?
[16:55] <tgm4883_laptop> I assume thats because you don't have to call it trunk
[16:55] <tgm4883_laptop> you could call it intrepid
[16:56] <tgm4883_laptop> and when you release intrepid, you could then change it to jackalope
[16:57] <salgado> mpt, isn't that just a way to define what lp:project-name will point to?
[16:57] <salgado> or does lp:project-name always point to trunk?
[16:57] <mpt> salgado, does that mean it's useful only if you use Launchpad for code hosting?
=== matsubara is now known as matsubara-lunch
[16:58] <salgado> mpt, not sure.  I have no idea what I'm talking about here.  rockstar should know, for sure
[17:01] <mpt> hm, looks like it's also used in Bugs somehow
[17:04] <rockstar> mpt, the trunk is usually considered "focus of development"
[17:05] <mpt> rockstar, in what cases would it not be?
[17:05] <rockstar> Basically, it indicates where all the development is going on, so you know where to branch from to get the most up-to-date code.
[17:06] <rockstar> mpt, in cases where the development is shifted to another branch with a LARGE feature that requires many developer's focus.
[17:07] <mpt> rockstar, so does changing the development focus change what bzr branch lp:project-name does?
[17:07] <tgm4883_laptop> i'd also think that trunk wasn't the development of focus leading up to a major release, where all development would be happening on that release
[17:08] <rockstar> Yes.
[17:09] <rockstar> Branching from lp:foo will pull the current development focus for foo
[17:09] <mpt> ok
[17:09] <mpt> rockstar, can you tell how it affects Bugs, or should I ask a Bugs person?
[17:09] <rockstar> mpt, best to ask bugs.  I didn't even know it affected them.
[17:10] <mpt> ok, thanks rockstar
[17:10] <mpt> gmb, can you unpuzzle me? :-)
[17:11] <gmb> wsfg?
[17:11] <mpt> gmb, a project's development focus affects how bugs work in some way but I can't tell what it is
[17:12] <gmb> Oh, okay.
[17:12]  * gmb looks.
[17:12] <mpt> (I'm in the middle of reporting a bug that this should be explained better)
=== salgado is now known as salgado-lunch
[17:13] <gmb> mpt: Good luck with that. It's horribly arcane in a lot of ways and is hell to describe, even in a code review.
[17:14] <gmb> mpt: Basically, though, if the project has a development focus then the bug task which is filed against that development focus is the master bug task for that bug.
[17:14] <gmb> (So you'll see things like "Tracked in foo-bar 0.2" in the slave bug tasks)
[17:15] <rockstar> gmb, wtf?
[17:15] <rockstar> I didn't understand very much of that.
[17:15] <gmb> rockstar: Heh; I work with it and I don't get it every time.
[17:15] <gmb> Erm, let me think about this.
[17:16] <rockstar> gmb, :)
[17:16] <gmb> rockstar: So, say you file a bug against the fronobulator project.
[17:16] <gmb> Someone then targets that bug to a release (not the current development focus).
[17:17] <gmb> Then someone else *also* targets it to the development focus release (well, series is the correct nomenclature here).
[17:17] <gmb> There are then two bug tasks.
[17:17] <gmb> One for fronobulator not-dev-focus
[17:17] <gmb> and one for fronobulator dev-focus.
[17:17] <rockstar> Okay, so the conjoined master is what results.
[17:17] <gmb> Correct.
[17:17] <rockstar> Ah, okay, that makes more sense.
[17:18] <mpt> So the line for "Fronobulator" will say "Tracked in <whatever the development focus is>"
[17:18] <gmb> mpt: Right.
[17:20] <mpt> gmb, what does it say before someone targets it to the development focus?
[17:20] <mpt> "Tracked in <old release>"? Or something else?
[17:25] <gmb> mpt: Let me check...
[17:26] <gmb> mpt: You just see two bug tasks. One for <Project>, one for <Series/Release>
[17:26] <gmb> mpt: https://bugs.staging.launchpad.net/bugzilla-launchpad/+bug/274186
[17:26] <ubottu> Launchpad bug 274186 in consolekit "console-kit-daemon crashed with SIGSEGV in fclose@@GLIBC_2.2.5() (dup-of: 263245)" [Undecided,New]
[17:26] <ubottu> Launchpad bug 263245 in consolekit "console-kit-daemon crashed with SIGSEGV in fclose()" [Medium,Confirmed]
[17:27] <gmb> Hush, ubuntoid, you don't know what you're on about.
[17:27] <gmb> Oh, it's ubuntoid's dumber brother, ubottu
[17:28] <mpt> gmb, ok, thank you for your investigations
[17:28] <gmb> np
[17:28] <mpt> and explanations
=== matsubara-lunch is now known as matsubara
=== salgado-lunch is now known as salgado
[18:23] <cr3> when I enqueued a branch for merging, will it be done automatically?
[18:23] <cr3> it's been enqueued for 2 hours, I'm wondering if I still need to merge manually and then LP will automatically detect the merge
[18:36] <rockstar> cr3, no, it wan't merge automatically.
[18:36] <cr3> rockstar: cheers dude, I would've waited a long time :)
[18:36] <rockstar> If you want to merge automatically, you'll need to set up a PQM instance.
[18:37] <rockstar> We'd like to make it so that enqueing it will allow an external PQM instance to see that queue and merge automatically, but we haven't gotten that far.
[19:11] <pmatulis> what is the difference between 'subscribers' and 'also notified' ?
[19:32] <siretart> the latter are implicit subscribers
[19:36] <BjornT> pmatulis: what siretart said. 'also notified' are people like assignee and people subscribed to the whole project/package. 'subscribers' are people that has explicitly subscribed to the specific bug
[19:39] <pmatulis> BjornT: thank you
=== thumper_laptop is now known as thumper
=== salgado is now known as salgado-afk