[02:12] <JesseW> So, how is the mapping made between lp:wtf and an actual URL (i.e. http://launchpad.net/wtf or something?
[02:12] <JesseW> ... in bzr.
[02:13] <RAOF> In the bazaar launchpad plugin.
[02:14] <mwhudson> JesseW: it talks to launchpad over xmlrpc
[02:16] <JesseW> mwhudson: I understand that -- I guess my question is more, what do the various parts of a launchpad URL mean.  i.e. why is https://code.launchpad.net/~kwwii/desktop-backgrounds-extra/trunk equivalent to lp:desktop-backgrounds-extra but lp:ubuntu-wallpapers is equivalent to https://code.launchpad.net/~ubuntu-art-pkg/ubuntu-wallpapers/ubuntu
[02:17] <RAOF> Because those plrojects have set their “development focus” to point at those branches.
[02:17] <JesseW> are the second directories (e.g. desktop-backgrounds-extra, ubuntu-wallpapers) unique?
[02:18] <JesseW> OK -- what's a "developement focus" and where can I find it, and where can I change it?
[02:18] <JesseW> (thank you to both of you for explaining, btw)
[02:18] <spiv> JesseW: the ones with three parts are of the form "lp:~user/project/branch-name
[02:19] <JesseW> spiv: the URLs with 3 parts?
[02:19] <persia> Where '~user' may represent either a person or a team
[02:19] <RAOF> The “development focus” is something that you specify in Launchpad.  I'm not sure if you can set it with launchpadlib, but you can find it... let me check.
[02:19] <spiv> JesseW: for the development focus, look at the "Branches" tab of your project (i.e. https://code.launchpad.net/yourproject), you should be able to see it or set it there.
[02:19] <JesseW> persia: ok, I mostly follow that part ~ means person or team (composed of people)...
[02:20] <spiv> JesseW: it's basically a way of saying "that branch is trunk for this project)
[02:20] <RAOF> JesseW: See for example, this page: https://edge.launchpad.net/pulseaudio-sharp  there's the “development focus” tab there.
[02:20] <JesseW> RAOF: checking
[02:21] <JesseW> the second line below "Developement focus", the one that says: "lp:pulseaudio-sharp" and links to https://code.edge.launchpad.net/~pa-sharp-core/pulseaudio-sharp/trunk , right?
[02:22] <RAOF> Yup.  If you hit the edit button next to that, you get to determine what the “development focus” points to.
[02:23] <JesseW> thanks.  what does "edge" in edge.launchpad.net mean?
[02:23] <RAOF> Oh, that's just the beta Launchpad.
[02:24] <JesseW> cool.  so https://launchpad.net/ubuntu-wallpapers states that it's development focus is: https://code.launchpad.net/~ubuntu-art-pkg/ubuntu-wallpapers/ubuntu
[02:25] <RAOF> Which is why lp:ubuntu-wallpapers points there.  You can actually get more funky than this; different series can have different branches - for example lp:do points to the development focus of GNOME Do, wheras lp:do/0.8 points to the branch for the 0.8 release series of GNOME Do.
[02:26] <JesseW> checking http://launchpad.net/do
[02:27] <JesseW> so, lp:ubuntu-wallpapers/trunk would point to the same place as lp:ubuntu-wallpapers?
[02:29] <JesseW> and lp:ubuntu refers to the whole of the ubuntu distribution?
[02:30] <spiv> JesseW: if ubuntu-wallpapers has a series called trunk
[02:30] <JesseW> spiv: it does.
[02:32] <JesseW> so, where is the mapping between lp:ubuntu/ubuntu-wallpapers and https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/ubuntu-wallpapers/lucid made?
[02:32] <spiv> JesseW: lp:ubuntu/* refers to packages within ubuntu
[02:33] <spiv> JesseW: so IIRC, lp:ubuntu/somepackage refers to the branch for that package in the current development ubuntu release, lp:ubuntu/somepackage/karmic would refer to it in karmic.
[02:35] <JesseW> spiv: ok, I get that. and I'm looking at https://launchpad.net/ubuntu/lucid -- but I'm not seeing where it's defined that lp:ubuntu/* links go to https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/*/lucid ... that's what I'm looking for.
[02:38] <spiv> Not sure, sorry.
[02:39] <JesseW> no worries, you all have certainly been helpful
[02:39] <JesseW> launchpad drives me nuts.
[02:40] <persia> JesseW: There'S no clear link between arbitrary projects and the packages that contain them within Ubuntu.
[02:41] <JesseW> persia: ok; but there must be somewhere that defines the semantics for lp:ubuntu/* links -- that's what I'm trying to find.
[02:41] <persia> The code for a given package is determined by a combination of what the Ubuntu developers upload and what they commit to the ubuntu branches, which may or may not be related to a given upstream branch (although it is often based on some upstream release)
[02:41] <JesseW> persia: I understand that.
[02:42] <persia> I'm not sure how the semantics are defined, but I believe the lp:ubuntu/* trees to be completely distinct from anything else (and so not pointers to other branches)
[02:43] <RAOF> I think you want james_w  for lp:ubuntu/*; it's special cased, as far as I'm aware.
[02:44] <JesseW> RAOF: ok, thanks -- I'll try to remember to ask him about it.  It's somewhat irritating that it's special cased, but -- sigh, launchpad...
[02:45] <wgrant> It's not quite special-cased.
[02:45] <mwhudson> hang on, what?
[02:45] <wgrant> lp:ubuntu/lucid/dpkg refers to the ubuntu/dpkg branch marked as official for the RELEASE pocket of lucid.
[02:45] <mwhudson> lp:ubuntu/* isn't special cased particularly
[02:45] <wgrant> lp:ubuntu/dpkg refers to the dpkg branch marked as official for the release pocket of Ubuntu's development series.
[02:46] <mwhudson> it's just different if the first part of the path is a distro rather than a project
[02:46] <RAOF> mwhudson: Ah, so it just _looks_ special cased, because I don't care about any of the other distributions that use Launchpad :)
[02:46] <persia> mwhudson: So it's linked in some way to some branch with an lp:~user/... URI ?
[02:47] <mwhudson> RAOF: well, you might care a bit about lp:debian/foo
[02:47] <mwhudson> persia: yessss
[02:47] <RAOF> That's true.
[02:47] <mwhudson> though for official branches the user is always ~ubuntu-branches i think
[02:47] <mwhudson> not a real person
[02:48] <persia> Um, "real" in what sense?  corporeal?  statutory?  Anyway ...
[02:48] <JesseW> ok, let me see if I follow this
[02:48] <mwhudson> (and the permissions are different)
[02:48] <persia> So are they different because of series?  Or can any branch be lp:~user/project/series/name ?
[02:48] <spiv> persia: real in the sense that no-one knows they are a dog on the internet ;)
[02:48] <persia> spiv: self-knowledge is the key to enlightenment :)
[02:49] <JesseW> first question: what's a pocket? ;-)
[02:52] <spiv> JesseW: that path leads to all sorts of hairy questions about exactly how apt archives of distributions work... if you follow that road you may on it for some time!
[02:52] <JesseW> spiv: argg, warning acknowledged.
[02:54] <persia> Quick'n'dirty definition of pocket that doesn't invite deeper explanation: A pocket is a place/marker/indicator applied to a collection of packages that are considered to be the same in some way (e.g. targeted for RELEASE)
[02:56] <JesseW> so, pretty much lp:ubuntu/* is defined by https://launchpad.net/ubuntu to point to https://code.launchpad.net/~ubuntu-branches/ and the /ubuntu/ part defines the distro, /lucid/ the series /ubuntu-wallpapers/ the project, and /lucid, er, what exactly? ;-)
[02:56] <JesseW> persia: ok, that makes sufficient sense
[02:57] <wgrant> ~ubuntu-branches isn't hard-coded.
[02:57] <wgrant> It could be owned by anybody.
[02:57] <wgrant>  /ubuntu means /ubuntu
[02:58] <JesseW> wgrant: not hard-coded, but defined by the distro - or is it defined further down the chain?
[02:58] <wgrant> No.
[02:58] <wgrant> It's just whatever branch is set as official.
[02:58] <wgrant> There is a mapping (distroseries, pocket, sourcepackagename) -> branch
[02:58] <wgrant> That defines the official branch for that source package in that pocket.
[02:58] <JesseW> wgrant: ok, that makes sense.
[03:00] <JesseW> and are all branches under https://code.launchpad.net/~whatever/* style links?
[03:00] <JesseW> where whatever is a person or team name, and * is arbitrary?
[03:01] <spiv> * there has to be <project>/<branch-name>
[03:02] <JesseW> spiv: ah, that's good to know.
[03:03] <wgrant> spiv: Or distro stuff.
[03:06] <JesseW> so, https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/ubuntu-wallpapers/lucid the /ubuntu/lucid/ubuntu-wallpapers/lucid is /distro/series/package/series (again?)
[03:07] <JesseW> and https://code.launchpad.net/~ubuntu-art-pkg/ubuntu-wallpapers/ubuntu the last two directories are project (ubuntu-wallpapers), and branch name (ubuntu)?
[08:22] <nad> hi
[08:23] <nad> i have a question, It is possible to install launchpad on my company server and use it for our development?
[08:25] <mneptok> nad: yes
[08:25] <nad> also for proprietary licenses?
[08:27] <tsimpson> you can use it where you like, it's open source
[08:29] <persia> I don't believe the LP code is licensed in a way that requires that anything hosted on that code has an open license.  Rather that's just terms of service for free use of Canonical's installation of launchpad.
[08:34] <nad> so i can download LP and install it to my machine, and then i can create my projects without share them?
[08:35] <persia> That's the idea, although I understand that setting up a local copy of LP is tricky at best.
[08:37] <nad> there are manual to do this?
[08:42] <tsimpson> nad: see https://dev.launchpad.net/Getting
[08:48] <nad> tsimpson: i have just finish to install LP now...but when i try to create a new project, it remind me to launchpad.net.
[08:48] <tsimpson> did you read the running section?
[08:49] <tsimpson> you should be connecting to launchpad.dev
[08:50] <nad> yes
[08:50] <nad> i'm in local in launchpad.dev
[09:02] <wgrant> Note that parts of Launchpad (in particular the branding and all of the images, but there may be other bits) are not licensed for non-development use.
[09:05] <nad> yes i fave read
[09:06] <wgrant> noodles775: Only that one failure, it looks like. Thanks for running it.
[09:06] <wgrant> Gah.
[09:06] <wgrant> Wrong button.
[09:07] <nad> but i have some problems to create new memebers
[11:34] <ChrisW> hi all, can launchpad still only host bzr repos?
[11:55] <persia> ChrisW: LP can also host release files, but I don't believe it supports any other DVCS systems
[12:03] <kwadronaut> how do i link a bug to a remote bugtracker?
[12:06] <ChrisW> persia: :-(
[12:06] <ChrisW> I still find the file browsing of bzr-hosted branches on LP totally inpenetrable
[12:06] <ChrisW> oh well, code.google.com it is
[12:07] <ChrisW> anyone know of any tools to migrate from bzr to svn?
[12:19] <adeuring> kwadronaut: if there is an external upstream project registered, you can do that on the "+editstatus" page of a bug
[16:12] <kwadronaut>  thanks adeuring
[16:13] <adeuring> kwadronaut: welcome :)
[17:00] <xteejx> hey guys, can someone place a ban/removal on user vincentowyong - reason is at bug 242276 - spamming LP with adverts, the bug report is being closed nonetheless thanks guys :)
[17:03] <mars> sinzui, ^ seen that before?  (read the thread down to comment #11)
[17:05] <sinzui> mars: I have seen that many times. Users ask us to remove the messages and suspend the user. We sometimes reactivate the user if the user demonstrates he has control of his computer and mail account again.
[17:05] <mars> sinzui, is that documented?
[17:06] <sinzui> in what way? it happens in launchpad answers every week
[17:07] <mars> sinzui, the "this happens all the time, here is what we do" aspect of it
[17:07] <sinzui> mars we have not documented what seems to work by just talking to people
[17:08] <sinzui> mars: how have you avoided CHR? we see lots of these questions, and when the suspended user contacts the feedback, we talk about it
[17:08] <mars> I shall not reveal the secret of my ignorance
[17:10] <sinzui> mars: https://answers.edge.launchpad.net/launchpad-project/+questions?field.search_text=spam&field.sort=RELEVANCY&field.sort-empty-marker=1&field.actions.search=Search&field.language=en&field.language=ja&field.language-empty-marker=1&field.status=OPEN&field.status=NEEDSINFO&field.status=ANSWERED&field.status=SOLVED&field.status-empty-marker=1
[17:11] <sinzui> mars: words other then spam may be used, but this is the most common term. We have been using answers to manage this since 2008
[17:12] <mars> sinzui, ah, I thought you meant "We see answers that are created by hijacked accounts all the time", not "we see people with hijacked accounts reported in answers all the time"
[17:12]  * sinzui nods
[17:13] <sinzui> mars: I know of two users who were unsuspended after they fixed they machines/mail provider
[17:14] <sinzui> Once the user is suspended, he gets a message to talk to a launchpad admin a feedback@launchpad.net. many ping us in IRC though.
[17:14] <mars> right.  Answer #32574 is one of those people.
[17:14] <mars> for instance
[17:15] <sinzui> marts: hey two new spams: https://edge.launchpad.net/~vicentaaguero35 and https://edge.launchpad.net/~buy-viagra-online-q
[17:16] <sinzui> mars:^
[17:16] <mars> yep
[17:16] <mars> just looking up the suspension message...
[17:18] <mars> sinzui, much easier!
[17:18] <mars> henninge, +1 for adding that CHR feature!
[17:18] <mars> kudos!
[17:19] <henninge> mars: thanks, that was really my own itch I was scratching here ... ;-)
[19:31] <j^> hi, what is the process to take over a project? i am the author of ffmpeg2theora and would like to use launchpad for bug tracking, someone else registered https://launchpad.net/ffmpeg2theora i left a message several days ago but did not get a response
[19:33] <beuno> j^, open a question against Launchpad requesting it
[19:47] <j^> You have reach your quota for direct contact of other Launchpad users. You can try again in 9 hours
[19:47] <j^> thats kind of annoying
[19:48] <j^> can i do anything about the contact user quota?
[19:48] <ScottK> Launchpad as a spam engine is even more annoying.
[19:49] <j^> sure, i understand that its there
[19:51] <j^> if people would not randomly register projects that they are not a part of, i would not have to contact them and ask to create a team or hand over the project, using the contact function on launchpad seamed the right way to do that
[19:51] <matsubara> j^, the current maintainer has the email publicly available, you might want to try that :-)
[19:51] <matsubara> j^, scratch that. I'm able to see because I'm member of some team. sorry for the confusion
[19:51] <j^> matsubara, i was going over a list of projects
[19:52] <jcastro> it was probably created because someone wanted to file a bug as "affects ffmpeg2theora" at some point and just created a dummy page
[19:57] <ScottK> There was a time when Launchpad thought it would be neat to make a dummy project for every source package in Ubuntu.  These aren't any of those are they?
[19:57] <jcastro> might be
[19:58] <jcastro> usually I have the right perms in lp to change over ownership of a project to an upstream, but the option doesn't appear on ffmpeg2theora's page
[20:01] <beuno> jcastro, ScottK, it's not a dummy project
[20:01] <ScottK> OK.
[20:01] <beuno> someone registered it
[20:01] <beuno> dummy projects are owned by "Launchpad Registry"
[20:01] <beuno> so this is a case where someone wanted the project on Launchpad
[20:02] <jcastro> ah
[20:02] <beuno> we've transferred ownership before
[20:02] <wgrant> Or where somebody didn't change the ownership to Registry.
[22:16] <magcius> eek, Launchpad doesn't render project pages correctly in the latest Firefox
[22:17] <magcius> changing .yui-main to have width: 77% fixes it
[22:27] <wgrant> magcius: I believe that's fixed on edge.
[22:27] <wgrant> magcius: Can you try that?
[22:33] <magcius> wgrant, yep, it works
[22:35] <magcius> wgrant, does Launchpad have code review yet?
[22:37] <magcius> wgrant, also, I'm trying to learn the code.
[22:38] <magcius> wgrant, you seem to use everything in Python: Twisted, paramiko, Zope, I believe I saw a Django import once
[22:38] <magcius> wgrant, what's the difference between /canonical/launchpad, /canonical/lp, and /lp?
[22:39] <poolie> magcius: yes, quite nice code review
[22:39] <magcius> poolie, where do I find it?
[22:39] <poolie> https://help.launchpad.net/Code/Review
[22:40] <magcius> poolie, err, I was thinking something a bit more like Splinter
[22:44] <wgrant> magcius: There's no Django in LP.
[22:44] <magcius> wgrant, ah, it was Storm.
[22:44] <magcius> wgrant, Storm has a "Django" package.
[22:44] <wgrant> magcius: canonical/launchpad/ is old (all stuff there should be moved to lp, but it's not done yet), lp/ is where everything should be, and canonical/lp/ is stupid
[22:45] <magcius> wgrant, heh.
[22:49] <magcius> wgrant, also, your bug tracker doesn't quite fall in line with this man's ego: http://joelonsoftware.com/articles/fog0000000029.html
[22:49] <magcius> ;)
[22:50]  * wgrant is not a Launchpad developer.
[22:51] <magcius> wgrant, oh, that's right. I thought you were.
[23:38] <RAOF> How is Launchpad's bugzilla integration?  We're pondering in #gnome-do about whether we could become a GNOME project without giving up Launchpad - can LP currently auto-forward and auto-retrieve bugs from bugzilla.gnome.org?  Is that planned?
[23:45] <thumper> RAOF: best people to ask are BjornT, deryck, gmb, allenap
[23:47] <RAOF> Ok.  Let them be summoned!