[00:01] <anka-ar> hi
[00:02] <anka-ar> anyone?
[00:03] <beuno> anka-ar, always
[00:03] <anka-ar> beuno!
[00:03] <anka-ar> justo
[00:04] <anka-ar> te lo digo rapido pero lo tengo que reportar a lauchpad o no se a quien
[00:04] <anka-ar> tal vez me puedas guiar
[00:05] <anka-ar> ayer se me dio por googlearme
[00:05] <anka-ar> despues de probar varias conbinaciones se me ocurrio lauchpad+ mi nombre
[00:05] <anka-ar> andres paul
[00:06] <anka-ar> y oh sorpresa!, mi nombre y mis datos aparecian en una pagina de casino!
[00:06] <anka-ar> los datos son los que aparecen en launchpad
[00:06] <anka-ar> hoy probe con mstreetlinux
[00:06] <anka-ar> lo mismo
[00:06] <anka-ar> con meisok, lo mismo
[00:06] <anka-ar> y hay mas
[00:07] <anka-ar> no se si tengo que reportar que estan levantando info de lauchpad, si tengo que mandar algo a algun responsable del manejo de la info o que
[00:07] <beuno> anka-ar, URL?
[00:08] <anka-ar> casinocom.com
[00:08] <anka-ar> mira
[00:08] <anka-ar> http://www.google.com.ar/search?hl=es&q=mstreet+casinocom&btnG=Buscar&meta=
[00:08] <anka-ar> http://www.google.com.ar/search?hl=es&q=andres+paul+casinocom&btnG=Buscar&meta=
[00:09] <anka-ar> y sigue
[00:09] <anka-ar> es la info de lauchpad
[00:09] <anka-ar> lauchpad*
[00:09] <anka-ar> casso!
[00:09] <anka-ar> launchpad
[00:10] <beuno> anka-ar, lo reporto yo, no te preocupes, gracias
[00:10] <anka-ar> de nada
[00:10] <anka-ar> :)
[01:01] <jspiro> hi all.  I would like to file a test bug that says "this is only a test".  In which project can I file it?
[01:04] <Odd_Bloke> jspiro: Use staging.launchpad.net.
[01:04] <Odd_Bloke> It resets every so often.
[01:05] <jspiro> Odd_Bloke:  how often?
[01:05] <Odd_Bloke> jspiro: I'm not sure, but it's not live data so it probably doesn't matter?
[01:05] <stdin> jspiro: every 24 hours
[04:14] <anka-ar> bye
[06:26] <alecwh> Is there a plan for Launchpad becoming Free Software anytime soon?
[06:37] <MTecknology> kiko-zzz: Wanna ping me when you wake up?
[06:37] <MTecknology> thanks
[06:38] <Hobbsee> alecwh: it's planned for before oscon next year, iirc.  I believe that's usually july
[06:38] <alecwh> great!
[06:55] <rockstar> alecwh, we are actively working on it.
[06:56] <rockstar> Hobbsee is right.  It'll probably be July (definitely not later).
[07:01] <alecwh> rockstar: thanks a bunch, that's fantastic to hear
[10:04] <persia> Against what project should I file a bug about https://help.launchpad.net/Packaging/PPA ?
[10:04] <bigjools> mrevell, is that launchpad-doc? ^
[10:05] <mrevell> persia: Yeah launchpad-doc, or feel free to file it against launchpad and we can change it. Alternatively, if it's a small change you can make the change yourself on the wiki
[10:05] <mrevell> persia: Or we could talk about what needs changing, if that helps
[10:06] <persia> Simple text change: "myapp_1.0.1" needs to be "myapp_1.0-1" and "myapp_1.0.2" needs to be "myapp_1.0-2".
[10:07] <persia> As it stands now, some users are confused, and uploading packages with native versioning when it's not needed.
[10:07] <Hobbsee> persia: you can edit that, i believe.
[10:08] <persia> me?
[10:08]  * persia tries
[10:08] <Hobbsee> you have to log in first, at the top right, iirc.
[10:08] <persia> Oh, cool.  I don't need to file a bug after all :)
[10:08] <Hobbsee> :)
[10:11] <mrevell> Thanks persia
[10:11]  * mrevell ponders if we should make it clearer that the help wiki is (mostly) editable
[10:12] <Hobbsee> mrevell: that depends how many people you want editing it
[10:12] <persia> Having people here note "You could just fix it" is probably sufficient.  Widely advertising it may lead to confusion as much as anything.
[10:12] <Hobbsee> mrevell: and whether you think they're mostly clueful.
[10:12] <mrevell> Yeah, that's the dilemma
[10:12]  * Hobbsee has made a few "revert crack" commits on the ubuntu wiki before
[10:13] <persia> I'm somewhat amused that I could edit it though : last time I tried to edit something on help.launchpad.net, I didn't have permission (although this was some time ago).  Has it been made more publically accessible sometime in the last year or so?
[10:14] <Hobbsee> persia: that was a bug.  that happened for a while, when people should have been able to edit, but couldn't.
[10:14] <persia> Oh.  I thought I just wasn't cool enough :)
[10:49] <arnarl> hi, who do I contact to get a neta
[10:49] <arnarl> meta project?
[10:50] <al-maisan> arnarl: what's a meta project?
[10:50] <al-maisan> do you mean a project group?
[10:51] <arnarl> sorry, I was thinking of a project that is a collection of projects
[10:51] <arnarl> yeah, probably
[10:51] <al-maisan> arnarl: please see https://answers.edge.launchpad.net/launchpad/+faq/210
[10:51] <arnarl> hmm, ok
[10:52] <arnarl> I have several packages http://ztmproject.org/code/ and I sortof wanted a way to group them
[10:52] <arnarl> currently I only have registered ztm.topicmaps and ztm.navigator
[10:53] <arnarl> are there any better ways of doing this?
[10:53] <arnarl> http://launchpad.net/ztm.topicmaps and http://launchpad.net/ztm.navigator etc...
[10:54] <al-maisan> arnarl: could these be different packages of a single project?
[10:54] <arnarl> yeah, they are
[10:55] <al-maisan> in that case there's probably no need for a project group ..
[10:55] <RinTinTigger> hey guys
[10:55] <RinTinTigger> can anyone help me with my problem : (EE) intel(0): [dri] I830CheckDRIAvailable failed because of a version mismatch.
[10:55] <RinTinTigger> [dri] libDRI version is 5.0.0 but version 5.4.x is needed.
[10:55] <RinTinTigger> [dri] Disabling DRI.
[10:56] <arnarl> but I sortof wanted the ability to do bzr lp:ztm.topicmaps and bzr lp:ztm.navigator etc...
[10:56] <arnarl> Is that stil possible?
[10:56] <al-maisan> RinTinTigger: please elaborate .. where do these error messages come from?
[10:57] <RinTinTigger> al-maisan i tried to activate desktop effects
[10:57] <RinTinTigger> which was not working
[10:57] <RinTinTigger> i tried to figure out why
[10:57] <RinTinTigger> and found that error
[10:57] <Hobbsee> RinTinTigger: you probably want #ubuntu
[10:57] <RinTinTigger> i asked there Hobbsee
[10:57] <RinTinTigger> but they cant help
[10:58] <Hobbsee> RinTinTigger: well, this channel *really* can't help.  It's about a web application.
[10:59] <al-maisan> arnarl: let me check that.
[10:59] <RinTinTigger> someone at the ubuntu-forum told me to go to the lauchpad
[10:59] <arnarl> I've sortof imagined the same setup as Zope has
[10:59] <Hobbsee> RinTinTigger: so, launchpad.net - that's not this channel.
[10:59] <arnarl> (the project is based on Zope)
[10:59] <RinTinTigger> uhm ok.... Hobbsee im sorry
[10:59] <RinTinTigger> dont the have an IRC channel?
[11:00] <RinTinTigger> *they
[11:00] <Hobbsee> they do, and this is it, but it's for support about how to use launchpad itself, not problems with #ubuntu.  #ubuntu is for that, as is #ubuntuforums.
[11:01] <RinTinTigger> ok, my bad. Thank u Hobbsee
[11:01] <Hobbsee> RinTinTigger: you're welcome
[11:01] <RinTinTigger> :)
[11:01] <al-maisan> arnarl: a user may have multiple bazaar branches hosted on launchpad .. is that what you mean?
[11:02] <arnarl> not really no
[11:02] <al-maisan> each package would correspond to a bzr branch
[11:02] <arnarl> at least in my head a branch is the same code, but with some functionality changed
[11:02] <arnarl> these branches implement different kinds of functionality
[11:02] <arnarl> like zope.component and zope.interface implement different functionality but are part of the larger Zope project
[11:03] <arnarl> still they don't need to be projects of their own
[11:03] <al-maisan> arnarl: I guess it's a matter of nomenclature ..
[11:03] <arnarl> but I would like individual bug trackers and similar things for each package
[11:03] <arnarl> yeah, probably
[11:04] <al-maisan> arnarl: yeah, that's fine .. you can associate bugs with packages
[11:04] <arnarl> ok, I'll try and figure out what a package is
[11:04] <arnarl> thnx :-)
[11:04] <arnarl> s/is/is in launchpad/
[11:05] <al-maisan> arnarl: you are welcome
[11:05] <persia> al-maisan, You can associate bugs with packages for arbitrary projects, or just for distros?
[11:06] <Mez> NOOOOO
[11:06] <Mez> you've changed the openid thing
[11:06] <Mez> I cant login as me anymore :(
[11:06] <al-maisan> persia: I don't know off the top of my head
[11:06] <al-maisan> would need to ask
[11:08] <persia> al-maisan, I could be wrong, but I thought that there were two distinct classes of entity in Malone: those which had bugs directly, and those which had bugs against packages.  Further, I thought there was some links between the set of packages known to Soyuz and the set of packages against which bugs could be tracked.
[11:08] <al-maisan> persia: I'll get back to you once I know more.
[11:09] <persia> Mind you, I mostly only use Malone for distro stuff, so that should be treated at best as hearsay, and quite possibly as a waste of bytes.
[11:09] <persia> al-maisan, arnarl needs the info more than I :)
[11:09] <al-maisan> OK
[11:17] <wgrant> al-maisan, persia: There is no subdivison of a product in Launchpad.
[11:17] <wgrant> Distros are all that have subdivisions.
[11:17] <wgrant> And sort of projects, but not really.
[11:18] <al-maisan> persia, arnarl : apparently launchpad does not support the filing of bugs against packages in PPAs yet.
[11:18] <persia> wgrant, Well, the Japanese Kaizen project has bug reports on a per-package basis, but it seems related to packages known to Soyuz.
[11:19] <wgrant> persia: Huh? Link?
[11:19] <persia> al-maisan, What's the relation between a project and a PPA?  I don't understand the context of your comment, although I agree with the statement.
[11:19] <al-maisan> persia: PPAs are tied to teams/persons
[11:19] <bigjools> there is no link between projects and PPAs (yet)
[11:20] <persia> al-maisan, Right, but projects aren't.
[11:20] <thekorn> i,
[11:20] <persia> Well, they are, but by an entirely different means.
[11:20] <thekorn> hi, even :)
[11:20] <persia> wgrant, https://launchpad.net/ubuntu-jp-improvement
[11:21] <al-maisan> arnarl was looking for the capability to file bugs against packages in a PPA ..
[11:21] <thekorn> is it possible to find out who and when a tag was added to a bugreport?
[11:21] <al-maisan> .. or at least that's what I understood
[11:21] <wgrant> thekorn: Check bugmail archives.
[11:21] <thekorn> and if not, does anyone know of a open bugreport about it
[11:21] <persia> No, arnarl was looking for a means to have bugs per component of a project, and thought a meta-project was the appropriate solution.
[11:22] <persia> wgrant, Note that it is considered a feature that bugs in that project are against packages known to be in Ubuntu by Soyuz.
[11:22] <wgrant> persia: I don't see a package relationship there.
[11:22] <al-maisan> persia: fair enough .. I pointed him to project groups
[11:23] <thekorn> wgrant: ok, that does not sound like a very productive way to get this information ;)
[11:23] <persia> wgrant, Hrm.  They used to be there.  Interesting,
[11:23] <al-maisan> I understood from the project groups FAQ, however, that these are more applicable to *established* projects
[11:23] <wgrant> thekorn: Indeed. I think everyone agrees that the activity log is pretty useless... but it seems LP devs have other priorities.
[11:23] <wgrant> persia: I'm fairly sure they never could have been.
[11:24] <persia> wgrant, Hrm.  Dunno.
[11:25] <thekorn> wgrant: I really like the way additional information is added to a subscriber, having a tooltip for tags saying "added xx-yy-zzzz by abc" would perfectly fit my needs
[11:25] <wgrant> thekorn: File a bug and pray.
[11:26] <Hobbsee> wgrant: actulaly, i find it useful.
[11:26] <persia> Maybe it gets an Ubuntu task once a patch is available (which is when I see most of those bugs), and I'm just confused.
[11:26] <wgrant> persia: That's not unlikely.
[11:26] <Hobbsee> wgrant: to go down and hunt whatever nutcase has decided to assign / subscribe ~ubuntu-core-dev to a bug, before going and yelling at them.
[11:26] <thekorn> wgrant: will do
[11:26] <wgrant> Hobbsee: Right. Subscribers can now also be hovered over to see who added them.
[11:27] <Hobbsee> wgrant: or to find out who has done (insert whatever other E, B & W thing they've done)
[11:27] <Hobbsee> wow...really?
[11:27] <Hobbsee> since when?
[11:27] <wgrant> Several months ago.
[11:27] <wgrant> Another thing that the changelogs could mention.
[11:28] <wgrant> The changelogs from late '05 and early '06 were excellent.
[11:28] <Hobbsee> oh, right.  doesn't include the 'also notified' either, i note.
[11:28] <Hobbsee> indeed.
[11:29] <Hobbsee> that's...kinda cool
[11:51] <jml> leonardr: hi, you around?
[11:51] <leonardr> jml, yes
[11:52] <jml> leonardr: I'm just mucking around with launchpadlib and having some problems authenticating my "just testing" example.
[11:52] <leonardr> jml, are you using staging? because we know that doesn't work
[11:52] <jml> leonardr: I am indeed using staging :)
[11:52] <jml> leonardr: what should I use instead?
[11:52] <leonardr> jml, try edge
[11:53] <leonardr> i guess i should look into fixing staging
[11:58] <wgrant> leonardr: Given that it makes launchpadlib fairly useless, that would be nice.
[12:02] <jml> wgrant: that's a) not true and b) flat-out rude.
[12:03] <wgrant> jml: I knew that was going to happen.
[12:04] <wgrant> jml: How am I meant to use launchpadlib if I can't test my app on something where people won't murder me for altering live data?
[12:05] <jml> wgrant: well, I'm managing for the moment :)
[12:06] <wgrant> jml: How?
[12:07] <wgrant> Ah, you have a launchpad.dev!
[12:07] <jml> wgrant: experimenting with r/o operations -- the write ops are obvious extensions of those. any app I write isn't going to talk to staging for tests anyway, it'll work off the wadl or some sort of mock
[12:07] <wgrant> jml: I don't mean formal tests.
[12:08] <wgrant> I mean I want to check that my script to close off bugs meeting criteria X, Y and Z isn't going to misfire.
[12:08] <jml> wgrant: sure, it's nice to have a service for end-to-end testing.
[12:08] <jml> wgrant: but this is well beyond "useless"
[12:09] <wgrant> jml: It means that only existing applications using launchpadlib can be safely used.
[12:10] <jml> wgrant: no it doesn't.
[12:10] <Hobbsee> wgrant: not necessarily.  You can still guess, and then presumably request that the admins revert a whole lot of data (or you do it yourself) if it doesn't work.  Suboptimal, though.
[12:11] <Hobbsee> oh, safely used.  Right.
[12:13] <wgrant> jml: It does.
[12:14] <jml> wgrant: safety in software is a matter of degrees.
[12:14] <wgrant> Misclosing several hundred bugs gets users angry. It needs to be safe.
[12:14] <jml> wgrant: I'd rather use something with a whole lot of good unittests that hasn't been run against staging than something that's only been run against staging a couple of times.
[12:15]  * persia suggests that rather than arguing about safety, developers might benefit by developing, and that leonardr is likely to render the entire debate useless soon enough.
[12:15] <jml> wgrant: for a thing like that, I would want to run against staging.
[12:15] <jml> wgrant: however, I stand by my first proposition.
[12:15] <wgrant> launchpadlib appears to be largely useful for bug manipulations at this time.
[12:15] <jml> wgrant: launchpadlib is useful without staging and you were being rude without cause.
[12:15] <wgrant> We have lots of bugs.
[12:16] <wgrant> Therefore a misfiring of a launchpadlib script is likely to adversely affect hundreds of bugs.
[12:17] <wgrant> I don't see an awful lot of rudeness in my original statement.
[12:17] <Hobbsee> jml: I don't think anyone's saying that launchpadlib is *completely* useless without staging.  What wgrant's saying is that it's rather useless to anyone who wants to test their scripts on temporary data, who doesn't have a launchpad source, or another instance to test it on.
[12:18] <Hobbsee> jml: and he's also saying that people aren't wanting to guess and hope for the best, when dealing with possibly large amounts of live data.
[12:18] <jml> Hobbsee: sure. A nicer way to say this would be "launchpadlib isn't that useful for me without a service to test on, so please do look into that leonardr"
[12:19] <Hobbsee> jml: or a whole lot of other people too, who are also using launchpadlib, or looking into it.
[12:19]  * Hobbsee suspects slight terseness would be due to the length of time staging has been out of action, too....
[12:51] <jml> leonardr: is there a backwards compatibility / deprecation policy for the APIs?
[12:52] <leonardr> jml: yes, backwards incompatible changes will mean we rev the version number
[12:52] <leonardr> and old versions will stick around for a while before redirecting to new versions
[12:52] <leonardr> but, that policy only goes into effect after the beta period ends
[12:52] <jml> leonardr: *nod*
[12:52] <jml> leonardr: so old versions will be available at different URLs or in response to some sort of version header or something?
[12:53] <leonardr> version 1.0 will be available at /1.0/ even after 1.1 is released
[12:53] <leonardr> different urls
[12:53] <jml> leonardr: cool.
[13:03] <jml> leonardr: last question: is HTTP 1.1 strictly necessary?
[13:06] <leonardr> jml: i don't think so, assuming the server doesn't require a Host header
[13:06] <persia> leonardr, Once there are stable versions tracked that way, would you expect it to be possible to continue to support whichever version of launchpad lib happens to be in any supported Ubuntu releases?
[13:07] <leonardr> persia: i think that's what we decided, but i don't know for sure
[13:08] <wgrant> <!-- at least 98 queries issued in 16.50 seconds -->
[13:08] <wgrant> Hmmm.
[13:08] <wgrant> I thought it was a bit slow.
[13:09] <persia> leonardr, That's excellent to hear.  Even just support for current stable is probably a win, although a full 60 months is of course ideal.
[13:13] <jml> wgrant: which page is that?
[13:14] <wgrant> jml: /ubuntu
[13:14] <wgrant> Er, bugs.launchpad.net/ubuntu
[13:25] <thekorn> I have a question about bug nominations: for which group of users does the nomination get auto-accepted?
[13:26] <wgrant> thekorn: I believe it's the driver of the project, distro or series, or the uploaders for the distro component.
[13:29] <thekorn> wgrant: ok, thanks this makes sense, I always thought it's for bug supervisours/contacts
[13:29] <thekorn> which is not true
[13:29] <thekorn> but driver sounds right
[13:30] <wgrant> Actually, it might be uploaders for the package, but that set is identical to the package's component's set except for a couple of packages.
[13:31] <jml> wgrant: https://bugs.edge.launchpad.net/malone/+bug/294672 if you haven't already seen it.
[13:31] <wgrant> jml: I hadn't; thanks!
[14:12] <kiko> hey jml!
[14:12] <kiko> jml, have a second for me? a quick question, honest :)
[14:13] <Odd_Bloke> kiko: Don't ask to ask... ;)
[14:14] <mwhudson> kiko: i'm here, for my sins, but battery is about to run out
[14:14] <kiko> Odd_Bloke, problem is jml's shy
[14:14] <kiko> mwhudson, ah, exactly the person I wanted! wanted to ask you about some pending questions and whether I can do something about them
[14:14] <Odd_Bloke> kiko: Try putting a lump of sugar on your hand and holding it out with a flat palm. :D
[14:15] <mwhudson> kiko: link me up, i guess
[14:15] <kiko> mwhudson, vvv
[14:15] <kiko> https://answers.edge.launchpad.net/launchpad-cscvs/+question/48685
[14:15] <kiko> https://answers.edge.launchpad.net/launchpad-bazaar/+question/48252
[14:15] <kiko> https://answers.edge.launchpad.net/launchpad-bazaar/+question/45488
[14:16] <mwhudson> the gstreamer branch is odd, there doesn't seem to be an associated CodeImport
[14:16] <mwhudson> but iirc, it was killed by the 'file-created-by-merge' problem
[14:16] <mwhudson> blender, nfi
[14:16] <kiko> mwhudson, can I just nuke that branch and start it off anew, or is that not going to work
[14:17] <mwhudson> kiko: if it's still cvs it won't work, i'm fairly sure
[14:17] <mwhudson> and dunno about the salsaga import
[14:18] <kiko> the salsaga one is pending on you doing some tarball magic
[14:18] <kiko> which reminds me
[14:18] <mwhudson> for salsaga, i was going to do this https://wiki.canonical.com/InformationInfrastructure/OSA/LPHowTo/CodeImportFromLocalRepo
[14:18] <kiko> wow
[14:18] <mwhudson> you could try to trick a losa into doing it
[14:18] <kiko> mwhudson, can anybody do that?
[14:18] <mwhudson> it's not the sort of thing i'm going to do when officially on leave :)
[14:19] <mwhudson> kiko: you need to be able to log in to the slaves
[14:19] <kiko> mwhudson, okay, gotcha.
[14:25] <jml> kiko: what
[14:25] <kiko> jml, mwhudson's helped me out. when are you visiting brazil?
[14:25] <jml> kiko: when is Canonical sending me there? :P
[14:25] <kiko> jml, RSN I hear
[14:26] <jml> kiko: cool :)
[14:26] <jml> kiko: then I'll be visiting Brazil real soon.
[14:29] <kiko> jml, you not making it out to UDS right?
[14:30] <jml> kiko: not unless it's *really* necessary. I'm speaking at OSDC in Sydney which is almost the same time.
[14:30] <kiko> jml, nah, just that it would be fun to have you there
[14:30] <kiko> next year maybe
[14:30] <jml> kiko: it would be fun to be there :)
[14:31]  * Mez cries
[14:31] <jml> but I can't deprive the people of Sydney of my wisdom
[14:31] <Mez> kiko: who removed the delegation on lp,net/~foo
[14:33] <kiko> Mez, how about you repeat that differently for the non-phd crowd out here
[14:34] <Mez> kiko: Before the last release of launchpad, when you went to a user's Launchpad page, it had headers that would say "this is an openid page, for this identity" - now it's been removed... breaking my logins :( I thought, seeing as you have access to the changelog, you might be able to tell me who I can blame :d
[14:35] <kiko> flacoste, bac: did that actually change in 2.1.10?
[14:38]  * Odd_Bloke used his user page for OpenID just the other day.
[14:38] <Odd_Bloke> Or am I missing the point?
[14:42] <Mez> Odd_Bloke: it's now changed, it actually just forwards you to the id.launchpad.net instead of allowing the ~user as an id
[14:43] <juliux> hi
[14:43]  * kiko pokes flacoste and bac agen
[14:43] <juliux> why isn't it possible to add a junk branch for a team?
[14:43] <bac> kiko:  you'll need to ask sinzui1
[14:43] <kiko> sinzui1 then?
[14:43] <kiko> juliux, history, I swear, it's all history
[14:43] <bac> i'm looking though
[14:45] <juliux> kiko: if i want to add a branch for a team it is optional to choose a project;)
[14:45] <juliux> kiko: but if you try to add it a project is required
[14:47] <papasmile> \p launchpad
[14:48] <kiko> juliux, yeah, it's one of these oddities in our model. might be worth asking a question on a.l.n to kick off a discussion
[14:50] <sinzui> Mez: Yes, we removed the ~name because it is mutable. You can change your name, and someone else can take your. That is not permanent, and could lead to scary/confusing situations when logging. So we removed it
[14:51] <Mez> sinzui: ah, well - I dont like it ... I've now lost my login to around 10 sites
[14:52] <Mez> sinzui: I didnt know you could actually change your name - I remember I never used to be able to (and had to get mark to do it for me!)
[14:53] <kiko> Mez, yeah, but you can, and that's a bit of a nasty exploit too
[14:53] <kiko> Mez, it was beta for a reason!! :)
[14:54] <Mez> kiko: indeed... but... *cries*
[14:54] <kiko> Mez, we hadn't considered the exploit originally, so my apologies for the short-sightedness
[14:55] <kiko> we try hard but sometimes reality is hard to change
[14:55] <Mez> kiko: I can see the point for changing it... but I don't like it - it'd be nice to have an option to switch it on... "I know there are security risks, but do it anyway"
[14:56] <Mez> kiko: a month and  a halfs work down the drain :(
[14:57] <Odd_Bloke> Could it not just be disabled when an account _is_ renamed?
[14:57] <flacoste> Mez: there is another reason why we removed ~username as an openID identifier, we plan on running id.launchpad.net on a separate server for high availability reason, using launchpad.net as the identifty domain prevents that
[14:58] <Mez> flacoste: how?
[14:58] <flacoste> Mez: and this has always been an undocumented feature because we did intend to remove it
[14:58] <Mez> flacoste: if it's just delegating to id.lp.net
[14:58] <sinzui> Mez: your profile page (~/mez) does work for OpenID 2.0 I believe. Launchpad return the URL to id.launchpad.net when an auth request it made to the profile page. OpenID 1.0 must use the new URL
[14:59] <flacoste> Mez: because the domain would be unavailable (during upgrade, which wouldn't happen with id.launchpad.net)
[14:59] <Mez> sinzui: it doesnt get accepted as the ID though - so It comes back as the new URL, rather than allowing the old one. Which means the URL I was using is no longer valid
[15:00] <sinzui> Mez: understood. I am mistaken
[15:00] <Mez> twas a nasty surprise...
[15:01] <soren> Mez: I'm surprised the sites you're having trouble with don't provide alternative means for logging in.
[15:01] <Mez> soren: openid only
[15:02] <flacoste> Mez: i am very sorry for the inconvenience, but where did you get the idea of using ~Mez as your openid identifier, it's not documented anywhere
[15:02] <kiko> flacoste, it's kinda the natural thing and most beautiful fwiw
[15:02] <flacoste> well
[15:02] <flacoste> we have pages explaining how to use the beta OpenID service, and none of them mention that one
[15:03] <kiko> kinda not my point :)
[15:03] <Mez> flacoste: I assumed... generally, an openid is "a web page that identifies a user"
[15:03] <flacoste> and we had a bug open saying that this was to be removed
[15:03] <Mez> which would be my LP page....
[15:03] <Mez> not some randomly generated URL
[15:03] <kiko> flacoste, still, you gotta understand that people don't always walk on the sidewalk..
[15:04] <flacoste> hey, i'm all for that, Montreal is the capital of jay-walkers
[15:04] <flacoste> but still, we kind of look before crossing the streets
[15:04] <Mez> infact https://id.launchpad.net/793/mez - doesnt even identify me.
[15:04] <Mez> It is not a web identity
[15:05] <flacoste> that's not how OpenID work btw
[15:05] <kiko> flacoste, well, it does take a URL..
[15:06] <Mez> flacoste: technically, no - but on a social aspect... yes.
[15:07] <Mez> an openid *should* be something that is an identity for a user, say their blog, their facebook page, something like that. A random URL is Not an identiy
[15:08] <Mez> "OpenID takes advantage of already existing internet technology (URI, HTTP, SSL, Diffie-Hellman) and realizes that people are already creating identities for themselves whether it be at their blog, photostream, profile page, etc. With OpenID you can easily transform one of these existing URIs into an account which can be used at sites which support OpenID logins."
[15:08] <Mez> I dont see the URL given as an identity for me :(
[15:10] <flacoste> we can easily fix that by redirecting to your launchpad profile, i'll file a bug about this
[15:11] <kiko-afk> cool
[15:12] <Mez> it's still not an identity IMO - just a random URL
[15:17]  * Mez starts sending begging emails
[15:17] <juliux> kiko-afk: now i have a very good solution :)
[15:32] <juliux> kiko-afk: so how it is possible to use lp branches without having a project? or is it in your interest that we register for everything a project?
[15:33] <gmb> juliux: If you push the branch to ~$you/+junk it won't be associated with any project.
[15:34] <gmb> e.g. bzr push lp:~juliux/+junk/some-branch
[15:34] <kiko-afk> juliux, well.. that's what junk branches are for!
[15:37] <juliux> gmb: we want to use it for a team
[15:38] <gmb> juliux: bzr push lp:~team-name/+junk should work, IIRC.
[15:39] <juliux> gmb: thanks
[15:39] <gmb> np
[15:40] <thekorn_> gmb, hmm I get  """ bzr: ERROR: Generic bzr smart protocol error: Permission denied: "Cannot create team-owned junk branches." """
[15:40] <gmb> thekorn_, juliux, so I guess IDNRC. Hmm.
[15:41] <gmb> That's a pain. I wonder why we do that.
[15:41] <gmb> In that case I'm not sure there's a nice way to do what you want to do.
[15:42] <thekorn_> juliux, create a project called "junk" ;)
[15:43] <gmb> Hang on, I'll ask someone who'll  know more than me..
[15:43] <gmb> (Not hard)
[15:43] <thekorn_> hehe, ok
[15:44] <juliux> thekorn_: but then i have to ask everybody who created some stuff for our locoteam about the license this stuff is;)
[15:44] <juliux> thekorn_: and doing this for stuff from three years need a lot of time
[15:47] <gmb> thekorn_, juliux: Okay, the person I was going to ask doesn't seem to be available atm. Best to file a question at http://answers.launchpad.net/launchpad-bazaar; someone from the Code team will help you.
[15:48] <thekorn_> gmb, thanks gmb
[15:53] <juliux> thekorn_: you or i?
[15:53] <thekorn_> juliux, mach du mal
[15:53] <thekorn_> ups wrong window
[15:54] <juliux> thekorn_: hehe
[16:49] <dilinger> hi, how do i get myself off a bug notification list?
[16:49] <dilinger> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/294527
[16:49] <dilinger> i was automatically added to that bug because i one did openafs stuff, but i don't work it it anymore.. and i see no way to unsubscribe myself
[17:03] <kiko-fud> fucking impatient users
[17:05] <persia> Well, if they don't want help, they don't get any.  Seems simple, although I would like a plugin for my IRC client to remove comments by anyone who joins a channel, says something ,and departs without anyone else commenting.  It's usually spam or impatience.
[17:11] <kiko> man needs lunch you know :)
[17:18] <MTecknology> sabdfl: Hi
[17:18] <MTecknology> sabdfl: Just wanted to say something to you at some point in my life. ;)
[19:20] <persia> I'm trying to link bug #249815 to Debian bug #504200.  Malone is telling me "u'Package recite not published in Debian'"  Any suggestions?
[19:20] <persia> Err, bug #294815
[19:41] <yarko> I'm getting an error on launchpad I don't understand - medium has reached its concurrent request limit.  .... anyone know what this is? anything _I_ can do about it?
[21:05] <newz2000> Hi, in case anyone else has fought with filtering launchpad bug email in gmail: www.bearfruit.org/blog/2008/11/06/gmail-filters-for-launchpad-bug-email
[21:25] <RainCT> Hi
[21:26] <RainCT> LP is rejecting my uploads with   "Could not find person '<launchpad-id>'".  Any idea what the problem could be?
[21:27] <lifeless> package uploads?
[21:30] <RainCT> lifeless: yep
[21:31] <lifeless> RainCT: signed the changes files?
[21:31] <RainCT> lifeless: if it may have anything to do with it: my GPG key expired recently, but I changed the expiration date and send it to keyserver.ubuntu.com again
[21:31] <RainCT> lifeless: of course :)
[21:31] <lifeless> check your key in the lp ui
[21:32] <lifeless> how recently did it expire?
[21:32] <RainCT> lifeless: just a few days ago
[21:32] <lifeless> right
[21:32] <lifeless> thats probably it
[21:32] <lifeless> each appserver builds a little cache of keys (because it uses gpg, and thats what gpg does)
[21:32] <lifeless> I'm fairly sure it doesn't poll the key server on every operation
[21:32] <lifeless> uhm
[21:32] <lifeless> file a question on this
[21:33] <RainCT> lifeless: Okay, thanks
[21:33] <lifeless> we need a losa to login to the app servers and refresh your key (and clearly there is an associated bug that an expired key should trigger a check on the keyserver or something)
[21:33] <RainCT> lifeless: against which project should I file it, launchpad or soyuz?
[21:34] <lifeless> launchpad
[21:39] <RainCT> Done. Thx.
[22:16] <lifeless> spm: ^
[22:17] <spm> lifeless: ta, adding to todo list. :-)
[22:42] <fta> no eta for PPA /w jaunty ?
[22:44] <persia> fta, None yet declared.
[22:46] <fta> persia, ok, thanks