[02:10] <NCommander> hey wgrant
[10:51] <Accidus> Where can I find more help on the luachpadlib module, except for the API html page?
[11:01] <thekorn> Accidus: https://help.launchpad.net/API/launchpadlib and the branch also contains a docs/ directory
[11:01] <thekorn> with some usefull documentation
[11:03] <Accidus> Thank you very much, but I've already looked there. I guess I'm on my own then?
[11:06] <thekorn> Accidus: I'm not sure, but what about asking your questions here, or https://answers.edge.launchpad.net/launchpadlib or on the launchpad-users mailinglist?
[11:07] <thekorn> I think the api devs are always happy to hear where they can improve the documentation ;)
[11:08] <Accidus> thekorn: To tell you the truth, it's because I'm new to launchpadlib, so I figured messing the forums/mailing lists with newbie questions wouldn't be appropriate
[11:09] <thekorn> Accidus: launchpadlib is brand new, so every user is new to it, just ask your questions
[11:10] <Accidus> Ah, that's something I didn't know...
[14:54] <persia> I seem to have locked a branch in LP (my branch, noone else should be using it).  How can I unlock it?
[14:56] <Verterok> persia: try with: bzr break-lock <your-branch>
[14:56] <persia> Verterok: Thank you.  That worked.
[14:57] <Verterok> persia: great, glad to help :)
[15:41] <salutis> ﻿hello all, I have big problem - recently I moved my packages from my own server to ubuntu's PPA at launchpad. and now I can't build my packages anymore. I placed my log at 'http://www.salutis.sk/ppa-log.txt'. can anyone please help me? thanks!
[15:42] <cprov> salutis: can you point me to your ppa ?
[15:43] <salutis> cprov: http://ppa.launchpad.net/salutis/ubuntu
[15:43] <salutis> cprov: there are 3 source packages - all with the same build failure :(
[15:44] <salutis> cprov: right now, geser at #motu adviced me - the build target is always run as non-root on the buildds, just remove the dh_testroot from the build target and it should get farther. I will try
[15:45] <cprov> salutis: yes, I'm there too
[15:46] <cprov> salutis: btw, you have a permanent URL for you failed build -> https://edge.launchpad.net/~salutis/+archive/+build/722220
[16:53] <persia> How long should I wait after a push before the branch is available on LP?
[16:56] <Verterok> persia: the branch is available immediately, but it take some time until it's showed in the we interface (I don't know the precise mechanism, but I think it's scanned)
[16:56] <Verterok> s/we interface/web interface/ :p
[16:56] <persia> OK.  I usually find it's just a couple minutes, but I've been waiting 7, which seems long.
[18:49] <Peng_> FWIW, it might also take a few minutes for the branch to be available over http://bazaar.launchpad.net/. bzr+ssh or sftp will be instantaneous.
[18:49] <Peng_> (Right? Cough.)
[18:51] <cprov> Peng_: yes, http branch mapping takes some minutes (IIRC)
[18:52] <Peng_> :)
[18:54] <kiko> cprov, peng_: I think it's something like 3 minutes
[18:55] <cprov> kiko: thanks.
[20:25] <jdrake> When making a blueprint, I notice there is a way to set a milestone, but I am not sure how to actually setup milestones. Any ideas?
[20:31] <kiko> jdrake, sure thing. what project are we talking about?
[20:32] <jdrake> My project 'starz'
[20:33] <jdrake> I have the series 'demo1' and 'trunk', the latter obviously being there already. I am not sure I would really want trunk there, being that I am doing all current development in demo1
[20:36] <kiko> jdrake, why didn't you just rename trunk to demo1?
[20:36] <jdrake> even with demo1 already there?
[20:36] <kiko> well, now it's a bit too late (though I can fix that for you)
[20:38] <jdrake> Is it possible to delete a series?
[20:41] <nedko> why launchpad refuses to show my location on the map?
[20:43] <kiko> jdrake, I can delete it for you. should I delete trunk?
[20:43] <maco> i need a bit of help. i pushed a branch to bazaar on launchpad a bit over a week ago, and launchpad still reports that it's empty.  i've tried to push from my computer again, but it says there's nothing new to commit.  what do i do?
[20:43] <salgado> nedko, have you set your location at https://launchpad.net/people/+me/+editlocation
[20:43] <kiko> maco, oh, URL?
[20:43] <jdrake> kiko, I think that would be best, thank you.
[20:44] <maco> kiko: https://code.edge.launchpad.net/~maco.m/update-manager/update_button
[20:46] <nedko> salgado: yes, i see the correct location there, and my timezone is fine too, in fact once there was only timezone and it looks launchpad used that. I dont see the map on my page and i dont see my location in team maps
[20:48] <kiko> cprov, check out maco's failure
[20:48] <kiko> cprov, something stuck in the scanner I think
[20:48] <cprov> kiko: sure
[20:49] <salgado> nedko, what's your LP username?
[20:49] <nedko> salgado: i think i missed how to use google maps, i need to click to set it o.0
[20:49] <nedko> salgado: it is "nedko"
[20:49] <kiko> nedko, click and then update
[20:50] <cprov> maco: can you try a `push --overwrite` ?
[20:51] <nedko> salgado, kiko: thanks, now it is fine
[20:54] <cprov> maco: is it working ?
[20:58] <maco> cprov: no new revisions to push
[21:00] <maco> cprov: it also says Format <RepositoryFormatKnit1> for lp-140342092:///~maco.m/update-manager/update_button/.bzr is deprecated - please use 'bzr upgrade' to get better performance
[21:00] <cprov> maco: that's bad, then the last resource is `bzr ci --unchanged -m "go, bzr, go" && bzr push`
[21:01] <cprov> maco: this is unrelated, but if you upgrade there will be something to push, for sure.
[21:01] <maco> cprov: i tried that last night when i got that error. no change.
[21:03] <cprov> maco: when, introduce a new revision then. Let me check if the bzr guys can help
[21:03] <cprov> maco: and let's open a bug about it.
[21:03] <maco> cprov: it could have been the timing
[21:04] <maco> cprov: i first tried it last thursday a few hours after the lp update
[21:04] <cprov> maco: yes, maybe.
[21:05] <maco> cprov: and i remember there was some emergency patching happening throughout the next day... i had one branch push fine about an hour before, and then this one didn't
[21:06] <rockstar> maco, what if bzr push --force
[21:07] <rockstar> Er, bzr push --overwrite
[21:07] <maco> rockstar: didn't try that, but after adding a new reivion like cprov suggested, it pushed
[21:07] <maco> rockstar: oh, did try --overwrite. no good.
[21:07] <rockstar> But a new revision pushed?
[21:07] <maco> rockstar: yes
[21:08] <rockstar> Launchpad still doesn't see your push though.  :(
[21:08] <maco> rockstar: or at least, bzr didn't yell at me
[21:08] <rockstar> You should see the Source Code link as soon as it pushes.
[21:08] <maco> rockstar: i'm told it can take up to 5 minutes for the lp web interface to show it
[21:08] <maco> oh its been 5 minutes...
[21:08] <rockstar> maco, well, the revisions, yes, the Source Code link, no.
[21:09] <rockstar> I did that myself, so I know that code relatively well.
[21:09] <maco> :-/
[21:10] <kiko> rockstar, it seems that there's a problem with that specific branch mirrorring
[21:10] <kiko> maco, does it use something unusual such as stacking or looms?
[21:11] <maco> kiko: um, you say that and i think plates and making fabric...
[21:11] <rockstar> kiko, I'm pulling it currently, meaning it's coming from the mirror.
[21:12] <rockstar> maco, I guess that means no to looms.  :)
[21:12] <maco> rockstar: i just did bzr branch, made some changes, bzr ci, and then bzr push
[21:13] <rockstar> maco, it branched for you?
[21:14] <kiko> heh
[21:14] <maco> rockstar: yes
[21:14] <rockstar> Mine appears to be hung.  I see no hpss traffic if I sniff my connection.
[21:14] <maco> er, i dont mean just now
[21:14] <maco> i mean when i did this last thursday
[21:14] <rockstar> Oh, so branching from this branch right now isn't working for you?
[21:15] <rockstar> Oh, there it goes!  hpss traffic now!
[21:15] <maco> havent tried that
[21:15] <rockstar> I just branched it.  Maybe it just needs to be rescanned after the interruption.
[21:15] <maco> i meant "just" as in "only"
[21:15] <maco> rescanned?
[21:16] <rockstar> So the branch is intact, but Launchpad needs to look at it again.
[21:24] <rockstar> kiko, I think you're right.  Something happened in the mirroring process.  I bet we see an oops from this.
[21:25] <kiko> rockstar, yeah, I think there's something unusual about his branch
[21:25] <kiko> rockstar, does bzr info tell you anything interesting?
[21:25] <rockstar> kiko, her
[21:28] <rockstar> bzr info yields nothing unusual.  The branch is indeed intact. This concerns me a bit.
[21:41] <maco> rockstar: so um, do you guys need any other info from me?
[21:45] <rockstar> maco, no, I think I need to do some sleuthing.
[21:46] <rockstar> maco, by the way, if you find yourself in a creole country, and someone calls you maco, you should be offended.  :)
[21:47] <maco> rockstar: is that where it means "nebby"?
[21:48] <maco> wait i think that's pittsburghese.... um nosey
[21:48] <maco> someone in #linuxchix said it means that somewhere...i thought it was one of the aussies, but maybe not
[21:49] <rockstar> maco, well, that's what it means in French.  In Creole, the closest English word I know would be "Peeping Tom"
[21:49] <maco> O_o
[21:49] <rockstar> So, maybe nosy pervert?
[21:49] <maco> wow ok...
[21:49] <rockstar> I learned it by talking to someone's girlfriend, and they thought I was flirting with her.
[21:50] <maco> why'd they think that?
[21:50] <rockstar> maco, *shrug* mwen pas sais.
[21:51] <maco> rockstar: je ne parle pas francais :P
[21:51] <maco> but i can type that ç
[21:52] <rockstar> I actually speak Creole.  It's like one way French.
[21:53] <maco> like moroccans can understand middle eastern arabic, but middle easterners can't understand moroccan arabic?
[22:05] <RainCT> Hi
[22:05] <RainCT> I've just got 3 [Accepted] emails (with like 5-10 minutes between each) for a single PPA upload..
[22:05] <cprov> RainCT: uhm let me check.
[22:06] <cprov> RainCT: which source ?
[22:06] <RainCT> cprov: bsod
[22:08] <cprov> RainCT: that's weird, because it doesn't look like more than one was sent to Recipients: "Siegfried Gevatter \(RainCT\)" <siggi.gevatter@gmail.com>
[22:10] <cprov> RainCT: do they have the same content ? different msg-ids ?
[22:11] <RainCT> cprov: Ah wait, it's just two. "[PPA rainct] Accepted: bsod ... (source)" and "[PPA rainct] [ubuntu/hardy] bsod ... (Accepted)"
[22:12] <cprov> RainCT: err, PPA stamp on primary archive upload-announcements ?
[22:13] <RainCT> cprov: sorry?
[22:14] <cprov> RainCT: forward the email(s) to me, please (cprov@canonical.com)
[22:14] <cprov> RainCT: the '[ubuntu/hardy]' is weird.
[22:18] <RainCT> cprov: done
[22:18] <cprov> RainCT: thanks
[22:34] <cprov> RainCT: strange, I've just uploaded a new version of your source to my PPA and received one single email (with [ubuntu/hardy] in the subject)
[22:34] <cprov> oh, you have two emails ...
[22:36] <cprov> siggi.gevatter@gmail.com (preferred) & rainct@ubuntu.com (used in the changesfile), that might be related.
[22:38] <RainCT> yea, but both mails were send to the first address
[22:40] <maco> RainCT: what's your @ubuntu.com email address map to?
[22:42] <cprov> maco: it was sent from lp to his @gmail address.
[22:43] <RainCT> maco: siggi.gevatter@gmail.com
[22:43] <maco> so then they should both end up at that gmail address, shouldn't they?
[22:45] <cprov> maco: and they did. RainCT ?
[22:46] <maco> so what's wrong then?
[22:47] <cprov> maco: there shouldn't be 2 emails.
[22:48] <cprov> maco: only one is expected. The one with subject starting with '[PPA rainct] [ubuntu/hardy] ...'
[22:49] <cprov> RainCT: err, if we have ever checked the date (!)
[22:49] <cprov> and the version ... [PPA rainct] Accepted: bsod 0.1-0ubuntu1~ppa1 (source)
[22:49] <cprov> RainCT: that email is from 2008/6/18 :)
[22:54] <RainCT> cprov: LOL sorry
[22:55] <cprov> RainCT: np, better than having a real bug.
[22:55] <RainCT> seems like GMail was mad and it put the mail three times into the inbox or something -.-  sorry
[22:55] <RainCT> heh yea that's true