[01:58] <ovnicraft> hello there is any clue in your roadmap about comments in blueprints ?
[01:58] <ovnicraft> or now how i can do it ?
[01:58] <lifeless> later this year we plan to fold blueprints and bugs together into a single issue tracker
[01:59] <lifeless> that will give you a place to have discussions about specification
[01:59] <ovnicraft> i see the whiteboard but is too stupid, users can delete texts added by others
[01:59] <ovnicraft> that sounds good
[02:00] <ovnicraft> so i think that concept now is imposible in lp
[02:00] <ovnicraft> developers cant have their space
[02:00] <ovnicraft> there is any specification where i can read ?
[02:01] <lifeless> dev.launchpad.net/IssueTracker I think
[07:41] <lag> Any skilled LP people with admin rights available to help me out?
[07:42] <lag> I've given a project to the wrong person and I need it changed pronto
[07:48] <wgrant> lag: There probably won't be any admins around for another hour or so.
[07:48] <wgrant> lag: Could you ask at https://answers.launchpad.net/launchpad/+addquestion?
[07:49] <lag> wgrant: I'm fairly sure I'm going to need an admin to correct my fopar
[07:49] <wgrant> lag: Or the person you gave it to, yes.
[07:49] <wgrant> lag: Ask a question at the URL I gave, and I'll poke an admin to deal with it when they awake.
[07:53] <lag> wgrant: https://answers.launchpad.net/launchpad/+question/146667
[07:57] <wgrant> lag: I've assigned it to the LOSAs.
[07:58] <lag> wgrant: Great, thanks
[08:01] <mok0> Hm, I am suddenly in doubt... can the Vcs-Brz: field in debian/control list the url as lp:~mok0/.... ?
[08:01] <wgrant> mok0: It should ideally list the official packaging branch.
[08:01] <wgrant> But that has nothing to do with Launchpad (yet?)
[08:01] <wgrant> We don't interpret the field at all.
[08:02] <mok0> wgrant: I know
[08:02] <mok0> wgrant: I don't maintain my packages in the main ubuntu branch
[08:04] <mok0> wgrant: what I meant, do I need to expand the "lp:" to a URL?
[08:05] <wgrant> mok0: It is already a URL. It's one that's only recognised by Bazaar, but it is still a URL.
[08:05] <wgrant> You should not have to expand it.
[08:05] <wgrant> I don't know what uses it.
[08:05] <mok0> wgrant, thanks.
[08:06] <mok0> wgrant: Isn't it used in LP to cross-reference?
[08:07] <wgrant> mok0: Not yet.
[08:07] <wgrant> It may be once we are building from branches natively.
[08:07] <mok0> wgrant: ah, ok
[08:07] <wgrant> But that is a while off.
[08:09] <mok0> wgrant: are you formally involved in LP development now?
[08:09] <wgrant> mok0: Yup, I started full-time in December.
[08:09] <mok0> wgrant: congrats!!
[08:10] <wgrant> Thanks!
[08:11] <mok0> wgrant: what kind of work do you do?
[08:12] <lifeless> the shadow knows
[08:13] <wgrant> mok0: I was initially working on Soyuz, but a month ago the team was restructured.
[08:13] <wgrant> So what lifeless says holds, basically.
[08:13] <mok0> Life in the shadow... complete freedom
[08:13] <mok0> :-)
[08:32] <gnomefreak> i was adding info to a bug report using apport-collect and answered all its question than after giving Lp access to update/change my bug report it is stuck on the "Almost Finished" page its been a few minutes now and it has not added info to the bug yet. should i start the process over again? it seems its LP not apport to me
[08:42] <wgrant> gnomefreak: Is apport not asking you to click a button to say you've done that?
[08:45] <gnomefreak> wgrant: after i allow acess i get nothing. i refreshed the web page that said almost done and it gave me an OOPS
[08:46] <gnomefreak> im going to try one last time, and ill let you know if it worked
[08:47] <wgrant> gnomefreak: It's not on a web page.
[08:47] <wgrant> gnomefreak: It's somewhere in apport.
[08:48] <gnomefreak> oh. well this time it didnt even bring up the webpage, so i guess it makes sense
[08:48] <gnomefreak> i guess ill add apport to my list of bugs to report. thanks wgrant
[09:10] <gnomefreak> wgrant: thanks it does seem that apport is crashing, i filed the bug on it.
[09:33]  * smokex is busy probably writing code: Gone away for now
[11:44] <hannie> jtv, my problem with the LoCo Directory is still not fixed. Any idea what's wrong?
[11:50] <jtv> hannie: last I heard, it was still a mystery!  The error that we found only seemed to affect one or two users.  jcsackett may know more.
[11:51] <hannie> ok
[11:51] <wgrant> What's the issue?
[11:51] <wgrant> Your team memberships and username aren't showing up in the LoCo directory?
[11:52] <jtv> wgrant: no, some "can't connect to LP server" errors (no oopses) when submitting translations.
[11:52] <wgrant> Ah.
[11:52] <jtv> The crazy thing is, that shouldn't depend at all on what exactly you happen to be doing afaict
[11:52] <jtv> It's normally a systemic problem.
[11:53] <jtv> hannie: the best guess we had last night was that RawChid and you might be behind the same proxy, but that seemed unlikely… any chance that it's the same provider though, and they might be doing something weird?
[11:54] <hannie> today is a new day ;)
[11:56] <hannie> jtv, we both log in at Launchpad. I do not see a connection with our providers
[11:56] <jtv> grr
[11:57] <hannie> It is a problem, because if today it still is not working, then well will it work?
[11:57] <jtv> Yes.  :(
[11:58] <hannie> Should I contact Danilos or David Planella about this?
[11:58] <jtv> Well that's the annoying thing: this isn't even translations-specific AFAICT.  Did you try submitting other forms, e.g. searches?
[11:58] <hannie> btw this suggestion is not a lack of confidence in you
[11:58] <jtv> No worries.
[11:59] <hannie> I have nog problem at all with other packages in LP
[11:59] <jtv> So even translating worked!?
[11:59] <jtv> For other packages?
[11:59]  * smokex is busy probably writing code: Gone away for now
[11:59] <hannie> Translating works, but if I can't save it, it is a waste of time
[12:00] <jtv> Of course.  But you were able to submit your translations to another package without the same problem?
[12:00] <hannie> jtv, yes, I worked in gcalctool simultaneously and saving there was no problem
[12:01] <jtv> That's… interesting.  And what package didn't work?
[12:01] <hannie> LoCo Directory
[12:01] <hannie> https://translations.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/
[12:02] <hannie> ...doesn't or not didn't ):
[12:02] <hannie> #not
[12:03] <jtv> Okay, I'll see if I can find anything weird about that then.  (It'd have to be very weird!)
[12:05] <jtv> hannie: do you get the same problem on our staging server?  https://translations.staging.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/
[12:05] <hannie> jtv, I found something!!!!!
[12:05] <jtv> ?
[12:05] <hannie> just a sec
[12:06] <hannie> I had filtered on the word "mondiale" because it should be substituted by "wereldwijde"
[12:07] <hannie> I have removed the filter, then translated another untranslated string and guess what...
[12:07] <hannie> it is saved!!!
[12:08] <hannie> So now I am going to try and save a string with the word "mondiale" in it.
[12:09] <hannie> With filter I mean of course the Search box
[12:10] <jtv> hannie: it's know that the search filter doesn't interact well with the translated/untranslated/… filter, but this is unexpected.
[12:11] <jtv> s/know/known/
[12:12] <hannie> ok, so that may have been the problem. I am now trying a string with "Mondiale"
[12:13] <hannie> Right, as soon as I use the word "mondiale" in the search box I get the error message
[12:13] <hannie> Finally I am going to try and change the same string, but without "mondiale" in the search box
[12:16]  * smokex is busy probably writing code: Gone away for now
[12:16] <hannie> jtv, it is still not working when I change a string with the word "mondiale" in it, even
[12:16] <hannie> when I empty the Search box and show all items
[12:17] <maxb> smokex: Automatic away messages on public channels are a bit intrusive
[12:17] <jtv> hannie: so the search filter wasn't related after all?
[12:17] <hannie> No it seems to be the word "mondiale"
[12:18] <hannie> I did hear Rawchid mention something about a script that did not word in LP, so
[12:18] <hannie> I wil contact him about this this afternoon. thanks for your help so far
[12:19] <hannie> #work
[12:19] <jtv> Thanks for helping figure this out.  Do try the same thing on the staging server, to see if it breaks there.  I'll see if I can figure out anything weird about the data.
[12:19] <hannie> jtv, what is a staging server?
[12:19] <jtv> It's a copy of Launchpad for experimenting in.
[12:20] <jtv> Its equivalent of the problem page is https://translations.staging.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/
[12:20] <jtv> (note the "staging")
[12:20] <hannie> ok, I'll have a look
[12:20] <jtv> I have to go take care of something urgent now.
[12:21] <hannie> bye
[15:38] <jtv> hannie: the good news is, I may have found the errors that have been hitting you.  The bad news is, it may be complicated and I still don't understand why it didn't give you an oops id.
[15:40] <hannie> jtv, I am playing in staging server now
[15:40] <jtv> Any different?
[15:40] <hannie> yes, I am investigating
[15:40] <jtv> (By the way, bear in mind that the data on that server is disposable—don't do "real" work there)
[15:41] <jtv> (Sorry if I keep repeating that, just want to be really really sure not to waste your work :)
[15:41] <hannie> #24 could not be altered in LP, but in 24 I see the word "mondiale" has been replaced by "wereldwijde
[15:42] <hannie> jtv, I understand. I only use it for experiments
[15:42] <jtv> OK
[15:43] <jtv> It's probably not the word "mondiale" as such; none of the interesting code cares about what exactly is in the strings.  But something unusual may have happened to those strings.
[15:44] <hannie> jtv, feedback: I can save in staging.lp.net
[15:44] <jtv> whoa
[15:44] <jtv> that's interesting
[15:44] <hannie> ah, tell me
[15:44] <jtv> but maybe the old, bad translations aren't in staging yet
[15:44] <jtv> (staging runs on slightly older copies of the database)
[15:45] <hannie> I think the string I just changed in staging was new
[15:45] <jtv> So no translation for it yet, in staging?
[15:45] <hannie> Only a suggestion
[15:46] <hannie> The 'old' suggestion (mondiale) is not present in staging, but it is in LP
[15:46] <jtv> That matches what I'm seeing…
[15:47] <hannie> And in LP I cannot change mondiale to wereldwijd because I get the error message there
[15:47] <jtv> The errors I found say that probably, the code tried to make a new message the current one without disabling the old one first.
[15:47] <jtv> If there is no old one, that would probably not happen.
[15:48] <hannie> In LP: Current Dutch = Gerelateerde mondiale activiteit
[15:48] <jtv> What I think is happening is that the code does disable the old message, but the activation of the new one gets flushed out of the ORM cache before the deactivation of the old one does.
[15:48] <jtv> (By the way yes, "wereldwijd" is much better :)
[15:48] <hannie> In staging: Gerelateerde wereldwijde activiteit, I just changed it to Current Dutch
[15:49] <hannie> Troubleshooting is fun, as long as you find the answer in the end ;)
[15:49] <jtv> heh
[15:49] <jtv> it can get a bit frustrating, too :)
[15:49] <hannie> yep, like now
[15:50] <hannie> But I do appreciate your help very much
[15:51] <jtv> hannie: and vice versa…  I just confirmed: we're just not telling the ORM "when you write our changes to the database, please write this one first or there'll be trouble."
[15:51] <jtv> So I'll go and fix that, and hopefully we can have the fix in production tomorrow.
[15:51] <hannie> right
[15:52] <hannie> What is ORM?
[15:52] <jtv> hannie: Object-Relational Manager.
[15:52] <hannie> ok
[15:52] <jtv> It's a software layer that lets you do object-oriented programming with what's actually relational database items underneath.
[15:53] <hannie> I'll check again tomorrow. thanks for your time and help so far
[15:53] <jtv> Turns out this was a known problem that we never got to the bottom of!  Bug 708385
[15:55] <jtv> I'll be attaching my fix (or "branch" really) to that bug ticket.
[16:19] <jploz> Hello. Hopefully, I'm in the right channel for my question.
[16:20] <jploz> It is about how to handle bugs and fixes in different Ubuntu versions.
[16:24] <jploz> Consider following szenario: a bug was reported against a package in universe. The bug also affects the upstream project, so it was added as also affected. Then a upstream release which fixes this issue was published and uploaded to Natty.
[16:25] <micahg> jploz: #ubuntu-motu would be better for this
[16:27] <jploz> micahg: Ok, I'll try there. Many thanks and bye.
[16:33] <JFo> wgrant, lifeless any update on my oops? It is hampering my ability to approve nominations for several CVE bugs.
[16:34] <JFo> Error ID: OOPS-1880K1665
[17:02] <jtv> RawChid: fix for that translation problem you were hitting (I hope!) is in review.  See bug 708385.
[17:11] <jcsackett> JFo, that OOPS appears to be tied to bug 723999, if you want to follow along on progress there.
[17:12] <JFo> ah, thanks jcsackett :)
[17:32] <dpm> hi launchpadders. I've just pushed a +junk branch and I got some weird output: http://paste.ubuntu.com/571820/ - is the "/~sathishmanohar/junk/main at lp-85632016" message to be expected?
[17:32] <dpm> I just found it a bit confusing...
[17:33] <james_w`> dpm, that's very odd
[17:33] <dpm> that was my thought :)
[17:35] <james_w`> dpm, jcsackett should be able to tell you if you should file a bug or not
[17:35] <james_w`> dpm, but I would suggest it
[17:35] <dpm> ok, thanks james_w`
[17:36] <jcsackett> dpm: i can't think of any valid reason you're junk branch should be stacked on another junk branch.
[17:36] <jcsackett> i'm checking to see if it does that for me as well.
[17:38] <dpm> jcsackett, ok, just let me know if you need me to file a bug
[17:39] <CarlFK> Package has already been uploaded to CarlFK-ppa on ppa.launchpad.net; Nothing more to do for dvswitch_0.9~alpha-0.5ubuntu1_source.changes
[17:39] <CarlFK> but it got rejected, guessing because I capped my username: CarlFK, when it should be carlfk
[17:40] <bigjools> dput -f
[17:40] <CarlFK> bingo.  thanks
[17:40] <RawChid> jtv, great to hear that. IS there more info on what the problem was? (I'm just curious)
[17:40] <jtv> sure
[17:40] <CarlFK> "Successfully uploaded packages."  - I figured there was something like that.
[17:40] <jcsackett> dpm: just notice, you pushed a branch for the junk project, not your junk (junk, not +junk).
[17:41] <leonardr> tumbleweed, bdrung, i've now contacted all the developers i could find. i'm going to send out an email to the tech list, and then i can do some work on upgrading u-d-t
[17:41] <dpm> jcsackett, ah, yeah, I've just seen I missed the '+'
[17:41] <jcsackett> dpm: looks like you are not alone in that.
[17:41] <jtv> RawChid: each translation, including suggestions, is recorded in the database as a "translationmessage" (or TM for short).  In a given translation, for a given msgid, zero or one TMs can be "current," which means they're the current, official, actual translation.
[17:42] <jtv> RawChid: When you change an existing translation, the code does two very sensible things:
[17:42] <dpm> jcsackett, ok, I'll just delete the branch. Thanks!
[17:42] <jcsackett> dpm: you're welcome.
[17:42] <jtv> RawChid: first, it removes the flag from the old message, so that it's no longer current.  Then, it sets the flag on the new message.
[17:42] <jtv> RawChid: and it has to happen in this order, because only one message at a time can be current.
[17:42] <bdrung> leonardr: tumbeweed began some work in lp:~stefanor/ubuntu-dev-tools/launchpadlib-1.9
[17:42] <jtv> RawChid: _however_ we weren't telling the ORM that those changes had to be sent to the database in that exact order.
[17:43] <jtv> RawChid: —and so sometimes, it would start with making the new message current and then make the old message not-current later.  Which isn't allowed, because in the meantime there are 2 current messages.
[17:43] <leonardr> ok, i'll take a look once i write the mail
[17:44] <jtv> RawChid: …so I added some hints to the ORM to say that the changes need to go out to the database in the right order.  If you're interested in the actual code changes, find the part with my branch and click on the Approved link.
[17:44] <jtv> RawChid: ahem.  I mean: go to the bug, and _there_ find the part with my branch etc.
[17:49] <RawChid> Thanks for the info! Sounds interesting. I'll take a look at the code now
[17:53] <timrc> When I attempt to change a PPA from public to private, I almost always get a 402 when I call lp_save() and the one time lp_save() did succeed, the change was not reflected on the web... http://pastebin.com/DGQHzHQt -- any obvious things that I'm doing wrong?
[17:54] <bigjools> you can't change privacy
[17:54]  * timrc slaps Cody
[17:54] <timrc> (if he were here :))
[17:55] <bigjools> well, you can't change it unless a) you're an admin, and b) there are no packages in the PPA
[17:55] <timrc> bigjools: ah ok, I'm an admin, so that's not the reason, but it requires packages... that's odd that that's not a requirement for making a PPA private through the web
[17:56] <timrc> web interface^
[17:56] <bigjools> it is, actually
[17:56] <bigjools> the checks are done at a low level
[17:57] <timrc> bigjools: I've created PPAs on a private project and set them to "private" before there were any packages in them, though...
[17:57] <bigjools> yes, you're not allowed to have packages :)
[17:58] <timrc> oh misread, the ppa has to be empty to set it private and I have to be admin
[18:05] <timrc> bigjools: so what of the 502's and 503's I get pretty much every time I call lp_save()? Bad Gateway and Service Unavailable do not seem like appropriate responses if I'm failing due to permissions problems
[18:07] <timrc> it doesn't seem to matter if I'm using 'edge' or 'production'
[18:08] <bigjools> sorry I have to go now, if you think it's wrong please file a bug and someone from the maintenance teams will triage it
[18:10] <lifeless> timrc: you should not be using edge anymore
[18:11] <sinzui> timrc: projects do not have ppas. You do though
[18:12] <dpm> jcsackett, I've got another issue with lp and bzr if you've got a minute: I'm trying to check out a branch on the canonical people server, and I'm getting this: http://paste.ubuntu.com/571831/ - I had the same problem a couple of weeks ago, but after several retries it ended up working. Any ideas what could be happening here?
[18:16] <jcsackett> dpm: sadly, i have no better explanation than sometimes codehosting gets heavy load. :-/
[18:16] <dpm> jcsackett, ok, no worries, thanks anyway
[18:17] <timrc> lifeless: okay, I think it's an artifact of looking at examples on the web which use it
[18:17] <timrc> sinzui: If I try to create a PPA on myself and then set it to private and lp_save(), I get a 502/503
[18:18] <timrc> sinzui: oh but yeah, thanks for the correction... I create a ppa on behalf of a 'team' for a project :)
[18:18] <lifeless> timrc: if those examples are on a wiki; change em ;)
[18:19] <sinzui> dpm: it works for me. can you do that from another machine? is port 22 really open on that machine
[18:20] <sinzui> timrc: I believe the only people who can set a ppa private is an admin or a commercial admin. So I think you should get a 403 when calling save for a the privacy bit
[18:22] <sinzui> This may be difficult because the you do have permission to use lp_save(). The someing, maybe in lp's API infrastructure needs to identify that the property is the issue
[18:22] <lifeless> sinzui: we should allow folk with commercial entitlements to do it themselves
[18:22] <timrc> I'm a commercial subscription admin
[18:22] <sinzui> lifeless: was say that a lot. Someone just has to pay for that to happen
[18:22] <lifeless> sinzui: well, we can start small :)
[18:23] <lifeless> sinzui: is there a bug for this?
[18:23] <sinzui> lifeless: timrc does not have a commercial entitlement by the way. we only provide that for projects with proprietary licenses. So there is another chunk of work someone must pay for before we fix the other part
[18:24] <lifeless> sinzui: timrc isn't the case I thought it was then :) - but anyone in canonical could be granted commercial entitlement from ~canonical, if we wanted to.
[18:24] <lifeless> that would be fairly cheap to do, no?
[18:28] <sinzui> lifeless:  there is no bug for this feature. I think one of my emails I sent in the privacy/disclosure email would form that basis of the issue and what we could do
[18:29] <dpm> sinzui, it worked well yesterd
[18:29] <dpm> sorry, pressed return too quick
[18:30] <sinzui> lifeless: timrc one option was to allow ~canonical members entitlement by default. I gave them power to create project and teams that start with 'canonical-' last month by the way
[18:30] <dpm> sinzui, the same bzr branch command worked well yesterday from this same machine, so I'm assuming that the port did not just get closed
[18:31] <jcsackett> dpm: you were invoking this on people.canonical.com, right?
[18:31] <timrc> sinzui, lifeless: I work in oem, we're trying to automate our project creation process and one component of that is programatically creating the private ppa for the project
[18:31] <dpm> jcsackett, yeah
[18:31] <jcsackett> i was able to do it from there a moment ago, dpm, sinzui.
[18:31] <sinzui> timrc: a noble effort. I wish we could connect that ppa to the project so it was easy to find.
[18:32] <sinzui> dpm: can you pastebin your script? I want to play a fragment to reproduce the bug
[18:33] <dpm> sinzui, it's not a script, I was just invoking http://paste.ubuntu.com/571831/ on the command line
[18:33] <timrc> sinzui: yeah, as it is all ppas live with ~oem-archive
[18:34] <sinzui> oops. too many users: timrc can you pastebin your script? I want to play a fragment to reproduce the bug
[18:34] <timrc> sinzui: http://pastebin.com/DGQHzHQt
[18:39] <sinzui> wow this scripte takes some time to run. It feels like the packets are being routed though Cleaveland
[18:39] <timrc> sinzui: my script?
[18:39] <sinzui> timrc: yes. I just code the error
[18:39] <timrc> sinzui: lp_save() alwas returns 502 or 503 ror me :(
[18:39] <timrc> for^
[18:40] <sinzui> timrc: I think this may be a timeout given the time it took to get the error
[18:40] <sinzui> timrc: I am going to toggle the ppa's privacy through the UI to see the difference
[18:41] <timrc> sinzui: if I comment out the ppa.private = True and call lp_save() it's instantaneous
[18:41] <sinzui> the UI is wicked fast
[18:41] <timrc> sinzui: doing ppa.private = True makes LP scratch its head :)
[18:42]  * sinzui looks at the impl
[18:42] <timrc> I can set ppa's private via the web ui, so I can't reconcile the difference
[18:48] <sinzui> timrc: I recall cases where field validation is not performed correctly over the API. I have seen name and date validation fail, so the bad value continues until something throws a wobbly. I wonder if this is the case here
[18:48]  * smokex_ is busy probably writing code: Gone away for now
[18:48]  * smokex_ is busy probably writing code: Gone away for now
[18:49] <sinzui> timrc: I see the field is guarded by  validator, and I wonder if the act off assignment is wrong
[18:49] <timrc> sinzui: ah, you mean, ppa.private = True would be an illegal assignment?
[18:50] <timrc> e.g. it's read-only?
[18:50] <sinzui> timrc: no we can assign, and we know from using the UI that the value is correct, but that does not mean the publisher is converting the values and doing the assignment correct
[18:57] <sinzui> timrc: I think I may need to wait for oops reports to arrive since I am not seeing an id at the moment. I am reporting a bug now
[18:57] <timrc> sinzui: excellent
[18:59] <timrc> sinzui: thanks for looking into this for me - it's greatly appreciated
[19:02] <sinzui> timrc: this issue may be bug 380504 or bug 702134. Since neither of us have seen it work. I cannot say the issue in intermittent.
[19:04] <timrc> sinzui: I went through that first bug
[19:05] <timrc> sinzui: and I believe the fix was to add a retry to the _connection() call in restfulclient
[19:05] <timrc> sinzui: that gives n=6 attempts with 2^n seconds between tries
[19:07] <timrc> er _request() I guess (looking at /usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py)
[19:08] <timrc> (python-lazr.restfulclient 0.9.20-0ubuntu1)
[19:35] <timrc> sinzui: thanks
[20:10] <CarlFK> https://launchpad.net/~carlfk/+archive/ppa/+buildjob/2284936   "Start in 3 hours" - really?
[20:15] <spetrunia> Hello
[20:15] <spetrunia> is it just me, or all launchpad websites work extremely slow now?
[20:16] <spetrunia> for instance, it takes minutes to report a bug
[20:18] <genii-around> Hello. How to change the email address my launchpad account is in? The place it was at stopped their email services, etc. Can't find a setting for it though.
[20:20] <genii-around> Ah, found the area to set it. Not overly intuitive. Thanks.
[21:17] <jcsackett> lifeless: r=me.
[21:18] <jcsackett> crap. wrong channel, but you still get the msg.
[21:30] <aroman> hey -- what is canonical doing about Apple's copyright infringement on the trademark "Launchpad"?
[21:33] <lifeless> its with legal
[21:34] <aroman> and have they said anything?
[21:34] <lifeless> I haven't heard anything
[22:40] <Delemas> I deleted a pending build because it was going to 7 hours to build. The buildjob did not get aborted. Is there some what I can force buildjob 2285139, for a now deleted job, to abort?
[22:41] <lifeless> not at the moment
[22:41] <lifeless> once its on a machine, its on a machine
[22:41] <Delemas> Can someone there do it?
[22:41] <lifeless> not at the moment, the sysadmins are all asleep
[22:41] <Delemas> lol oh well... Thanks anyways...
[22:46] <wgrant> Delemas: It's not on the builder yet. It will be cancelled once it reaches the head of the queue.
[22:49] <Delemas> ya unfortunately that will take 6-7 hours to clue in. That package is a dependancy for my build and I was going to just copy the binaries from another PPA so I could proceed with my build...
[22:49] <Delemas> I get an error when trying to do that, because it's in the build queue...
[22:50]  * smokex_ is busy probably writing code: Gone away for now
[22:50]  * smokex_ is back.
[22:50] <lifeless> smokex_: please disable emote-on-away
[22:50] <lifeless> smokex_: its very annoying because it shows up in every channel you are in.
[22:52] <smokex_> done
[22:56] <lifeless> thanks
[23:02] <Delemas> Anyone know how to get pbuilder to pull a dependant package from a PPA?
[23:08] <sinzui> delemas, your building something locally and want to specify an archive to pull deps from?
[23:08] <lifeless> Delemas: add it to sources.list in the chroot; you can do that at runtime with an option that I have forgotten
[23:10] <Delemas> Yes I have a local package I want to build locally which needs a dependancy from a PPA. So I need a way to tell it to grab it from the PPA...
[23:12] <Delemas> I'm trying to build freeipmi 0.8.12 packages which needs autotools-dev (>= 20100122.1~)...
[23:19] <sinzui> Delemas: I think you want to look at http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html#usingspecialaptsources Launchpad ppas are archives like deb http://ppa.launchpad.net/team-of-user/ppa/ubuntu natty main
[23:35] <Delemas> Thanks