[00:00] !away > jasono [00:00] jasono, please see my private message [00:00] * jasono is back (gone 00:07:59) [00:01] sorry [00:01] won't use it again [03:28] hey Launchpad, I've been asked by a Debian Developer buddy of mine to forward you guys a copy of some copyright issues that a user is causing via his PPA [03:28] https://launchpad.net/~ivan1986/+archive/dropbox [03:28] related to: [03:28] https://answers.launchpad.net/launchpad/+question/141763 [03:28] from Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610257 [03:29] Looks to be a LP bug #703896 [03:29] Launchpad bug 703896 in dropbox (Ubuntu) "Multiple license issues" [High,Triaged] https://launchpad.net/bugs/703896 [03:29] It was removed from Debian main, and the ex-maintainer uploaded code he knew was tainted to the PPA build system [07:12] is bazaar lp broken? [07:12] Corrupted MAC on input. [07:12] Disconnecting: Packet corrupt [07:12] bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. [07:13] fta2: what were you doing? pull/push? [07:13] pull [07:14] a retry worked [07:14] if you see again, can you let us know? we've done some edge changes that *may* cause funkies. [07:14] sure [07:14] ta [08:28] Hey guys, yesterday evening I created my first recipe, but I couldn't find the "Create Recipe" link on the main site so I went to edge.launchpad.net and did it, this morning I went to create another - but there is still no link on the main site but edge.launchpad.net redirects to the main site... how can I create a recipe? [08:47] what time do launchpad recipe daily builds start? [09:20] there's spam on #196724 === zyga_ is now known as zyga-vaio === menesis1 is now known as menesis === oubiwann is now known as oubiwann_ === oubiwann_ is now known as oubiwann === oubiwann is now known as oubiwann_ [13:33] hi, one of my friends seem to be getting : Failed to fetch http://ppa.launchpad.net/project-neon/ppa/ubuntu/dists/maverick/main/source/Sources.gz 404 Not Found : whereas i can update the same repo file [13:33] *fine [13:33] however the link itself seems to be a 404 [13:37] nvm [13:39] shadeslayer: we're all at a meeting this week at UTC-6. You'll probably have more luck in an hour or two. [13:39] jtv: figured it out :) [13:40] ah good :) [13:40] jtv: is LP switching to C++ after this meeting? [13:40] * shadeslayer crosses his fingers [13:40] :P [13:40] shadeslayer: err… [13:40] possibly not just yet. [13:41] jtv: ohk .... thanks for daily builds tho :) [13:41] but we're all converted to scientology now and very interested in getting time-share condos! [13:41] to the whole LP and Bazaar teams [13:41] or no maybe that was the other meeting. [13:41] lol === yofel_ is now known as yofel === oubiwann is now known as oubiwann_ === oubiwann is now known as oubiwann_ [14:35] * mgedmin looks at the topic [14:47] does it make sense to sign 'code of conduct' if one does not use ubuntu? === Meths_ is now known as Meths [15:09] * jasono is away: The Cape [15:28] anyone around? or is everyone at the meeting? :P === joey` is now known as joey === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [16:52] Hi. I'm getting a mystifying error when I try to set the branch for the development focus of a project via the API: http://paste.ubuntu.com/555463/ [16:52] Is this a known bug (I couldn't find it), or a bug I should report, or is there something obvious I'm doing wrong? [16:52] cjwatson: the LP team is in one room and listening to poolie right now [16:52] we'll get back to you shortly [16:52] OK, thanks [16:53] the client code is http://paste.ubuntu.com/555464/, although I suspect the only other interesting bit is the initialisation of new_branch [17:05] cjwatson: can you do a breakpoint after getting the focus, and we'll see if it is getting it properly? [17:05] cjwatson: we aren't quite sure what is going on here [17:05] cjwatson: your code looks fine to me [17:08] (Pdb) p focus [17:08] [17:10] hmm.. [17:10] and the branch is valid too? [17:10] leonardr: the client code is http://paste.ubuntu.com/555464/, although I suspect the only other interesting bit is the initialisation of new_branch [17:10] (Pdb) p new_branch [17:10] [17:11] and https://code.launchpad.net/~ubuntu-installer/elilo-installer/master exists [17:11] I *can* go round and do all of this by hand in the UI, and that's worked fine for other projects; I was just hoping not to [17:11] cjwatson: what do you get if you go p new_branch.name [17:11] u'master' [17:11] ok... [17:12] what about p focus.name [17:12] u'trunk' [17:12] cjwatson: hi [17:12] hello, thanks for looking at this [17:12] i'll stop asking thumper to ask you things and ask you myself [17:12] :-) [17:12] try this [17:13] p self.lp_has_parameter('branch') [17:13] sorry [17:13] s/self/focus/? [17:13] yeah, exactly [17:13] True [17:13] (this is on up-to-date natty as of earlier today, BTW) [17:13] so the question is which object this is happening to [17:14] what is 'self' here? i thought it was focus [17:14] can you put a breakpoint on line 677 of resource.py? [17:14] let's see what 'self' is? [17:15] -> if not self.lp_has_parameter(name): [17:15] (Pdb) p self [17:15] [17:15] which is focus. odd [17:16] what is 'name'? 'branch'? [17:16] and if I run 'p self.lp_has_parameter(name)' there in the debugger, it returns True [17:16] yes [17:16] and branch? [17:17] wait, stepping past this in the debugger appears to work fine, what's going on [17:17] cjwatson: did it fail consistently before? [17:17] see if it still fails if you take out the breakpoint [17:18] as far as I can tell ... but restarting from scratch, breaking at line 160 of my script, and 'n'ing past, it fails [17:19] cjwatson: well, here's what the error was saying, so you're not mystified [17:19] does signing code of conduct influence one's karma at LP? [17:19] there's a json document that describes the 'focus' object [17:19] OK, calling self.lp_has_parameter(name) fails the first time, but succeeds the second time, AFAICT [17:20] oh, no - it succeeds only after I do 'p self' [17:20] when you call focus = project.development_focus it's supposed to grab that document and associate it with the object [17:20] but for some reason it's not [17:20] so: b lazr/restfulclient/resource:677; c; p self.lp_has_parameter(name); p self.lp_has_parameter(name) -> fails [17:20] ok, put this before Launchpad.login_with [17:20] but: b lazr/restfulclient/resource:677; c; p self.lp_has_parameter(name); p self; p self.lp_has_parameter(name) -> succeeds [17:20] import httplib2 [17:20] httplib2.debug_level = 1 [17:20] paste the result [17:21] that will tell us what requests it's making [17:21] gour: no [17:21] that's not producing any extra output [17:21] thumper: ta [17:23] cjwatson: sorry, i think it's debuglevel [17:23] yes [17:24] * leonardr needs to go for a bit but will be back [17:24] leonardr: http://paste.ubuntu.com/555478/ === beuno is now known as beuno-lunch [18:10] leonardr: this sounds awfully like bug 662740, except for getting attributes. Do I have the wrong end of the stick? [18:10] Launchpad bug 662740 in lazr.restfulclient "Setting an attribute on a shim object without first reading an attribute causes a crash" [Low,Triaged] https://launchpad.net/bugs/662740 [18:10] s/, except for getting attributes// (brainfart) [18:11] cjwatson: checking, it's possible [18:11] would you add 'print focus' to your code and send me the http dump? [18:11] i notice that the object was not in fact retrieved [18:12] cjwatson: yes, that's exactly the problem. this bug was not fixed [18:12] cjwatson: the workaround is to assign focus.name or something to a variable before trying to use focus [18:12] definitely working now, though I ctrl-ced it since I want to run most of this with debugging off. http://paste.ubuntu.com/555496/ [18:13] ok, great [18:13] thanks; I think this has still been a net time-saver :) [18:14] cjwatson: mention in the bug that you ran into the problem and maybe we can bump up the priority [18:16] mentioned, thanks - though I have an easy workaround now so it's not critical from my POV [18:16] until the next time I forget about it and run into it again of course ;-) [18:17] * cjwatson returns to the rebase-foreign from hell [18:22] thumper: src/lazr/restful/_resource.py line 825 === beuno-lunch is now known as beuno === Chex_ is now known as Chex === Ursinha is now known as Ursinha-afk [19:38] hey Launchpad, I've been asked by a Debian Developer buddy of mine to forward you guys a copy of some copyright issues that a user is causing via his PPA [19:38] https://launchpad.net/~ivan1986/+archive/dropbox [19:38] related to: [19:38] https://answers.launchpad.net/launchpad/+question/141763 [19:39] there's an LP and Debian bug that are related [19:56] wgrant: are you around, perchance? === Ursinha-afk is now known as Ursinha [20:12] paultag: Hi. I'll poke people about that copyright issue. [20:12] paultag: We're all sprinting this week, so there are a few distractions. [20:13] wgrant: great. thanks so much! [20:50] Afternoon, I'm having problem with bzr syntax copying ' lp:ubuntu/lucid-proposed/asterisk' into 'lp:~pabelanger/ubuntu/lucid-proposed/asterisk'. Any pointers? [20:51] pabelanger: "copying" ? [20:52] anyone can point me quick howto/doc to markup used in bug tracker to refer to bzr commits? [20:52] Most likely your problem is that it needs to be lp:~pabelanger/ubuntu/lucid-proposed/asterisk/some-name-goes-here [20:52] glen: I'm not aware of any such markup [20:53] maxb: you can't refer to commit @999 ? sad. somewhat bug #777 works in bzr commits otoh [20:53] Launchpad bug 777 in helix-player (Ubuntu) "installscript fails to create a symbolic link for plugin registration (mozilla-firefox)" [Medium,Invalid] https://launchpad.net/bugs/777 [20:55] glen: bzr commits can have specific metadata attached to them with "bzr commit --fixes ...." [20:55] Launchpad bugs can have linkage to particular branches stored [20:55] ah, indeed, i should used --fixes prior pushing (at the commit time) [20:56] You can of course write something like "lp:bzr r12345" in text in a bug, but it does not get turned into an automatic link to the revnum [20:56] is there a current PDF for packaging how to/basics? [20:57] as well as setting up a PPA, that kind of thing? [20:57] This isn't really a big problem usually, because usually you're discussing which branch contains a fix, and revnums are mostly unimportant [20:57] i found some real old ones with the Google [20:57] maxb: Ya, sorry. I'm coming from a subversion background so my bzr skills a little week. I guess 'bzr branch' is the command I want, but I was trying to figure out how to create the branch remotly on launch pad, rather then creating the branch locally, to turn around an push it back into launchpad. [20:58] timH: All current documentation I'm aware of is on wikis. Are you specifically seeking a PDF? [20:59] maxb: yes [20:59] pabelanger: Ah, some sites (github?) have such a thing. Launchpad operates on the basis that there is absolutely no need for you do preparation in a web form, so why not just branch, hack, push [20:59] timH: I fear you will be disappointed then, sorry. [20:59] maxb: i have some train time coming up and will have limited/no connectivity, perfect time to get started with packaging basics... [20:59] oy [21:00] pabelanger: A key point is that Launchpad will automatically "stack" new branches on the development focus branch for the project. This means you only spend network bandwidth pushing up the new revisions not already in the project's trunk [21:02] maxb: Okay, thanks. Looks like I have some reading to do. [21:02] timH: In my experience, "I want to learn packaging" is the wrong approach, because the subject is so vast and broad. A better approach is usually "I want to learn what I need to know to accomplish ". [21:02] timH: Unfortunately that means that you usually end up researching the topic as you work, so doing it disconnected isn't great [21:03] maxb: right.. i mean ultimately I just want to be able to release via a PPA [21:03] pabelanger: #bzr is a great resource for assistance getting to grips with bzr [21:03] danke [21:04] timH: Right... in which case, you should probably focus exclusively on getting a working package built on your own computer before even considering the PPA aspect. [21:04] maxb: so then isn't that learning how to make packages? [21:05] Sure, but worry about the packaging first and the PPA setup after [21:06] maxb: that was the first thing I asked about... [21:06] Try https://wiki.ubuntu.com/PackagingGuide/Complete (long!) [21:07] thanks, I can easily enough print that to a PDF.. i tried Render to Docbook earlier hoping somehow that would give me something I could convert to PDF but it appears to be broken [21:08] You'll probably want to pre-read it and download lots of stuff it mentions [21:10] hmm, perhaps I just need to get better coverage [21:12] ok, well thanks anyway === warp11 is now known as warp10 [21:32] Is there a LOSA around? [21:33] gah, never mind, question I was looking at has already been answered [21:41] what is supposed to go into the DEBIAN directory when using dpkg-deb ? [21:41] i tried doing a make install there but when I install the .deb I get some error about 'usr' [21:42] If you ever need to actually *think* about the DEBIAN directory (rather than the debian directory) it's usually a sign you're using tools much lower level than you need to [21:45] thats true, i started using dh-make but it was broken so i started implementing debian/rules by hand [21:45] its not really very hard, i got all the rest of the rules set up, i just need to figure out DEBIAN [21:46] has there been a recent increase in the space between lines in loggerhead? [21:47] there seems to be an excessive amount of whitespace here: http://bazaar.launchpad.net/~ssh-import-id/ssh-import-id/trunk/view/head:/ssh-import-id [21:50] jonrafkind: For any kind of non-trivial package I would highly recommend using at least debhelper rather than direct dpkg-* building commands [21:51] so dh-make uses debhelper? [21:51] dh-make is a program to lay down an initial slightly customized template for packaging [21:51] The templates that are constructed generally use debhelper [21:52] is debhelper the 'dh' program? [21:52] Although I think dh-make has a cdbs option too (though cdbs itself uses debhelper) [21:52] on my system its slightly broken, it doesnt handle the override_ stuff [21:52] The dh program is one part of debhelper [21:52] i guess i could just invoke the dh_auto things myself [21:52] yea ill probably do that [21:53] The dh program is a new style of usage introduced with debhelper 7. Before debhelper 7, everyone invoked the dh_foo commands explicitly [21:53] If your local debhelper has dh but doesn't understand override, that suggests you are using debhelper 7, but less than 7.0.50 [21:53] which suggests you are using hardy [21:53] which suggests you should upgrade! [21:53] im on jaunty I think [21:53] :-) [21:53] 9.04 [21:54] jonrafkind: jaunty is months beyond end-of-life, you know? [21:54] yea the package manager tells me like every day :p [21:54] i would upgrade if ubuntu had a chance of not destroying my machine.. but sadly thats extermely unlikely [21:54] And yes, the debhelper there is too old to support override_ [21:55] jonrafkind: What's special about your machine that you can't upgrade? [21:56] no idea, but ubuntu has destroyed 3 of my machines while trying to upgrade, so now i dont do it anymore [21:56] Then you should file bugs :-) [21:57] yea.. nice bug. "upgrading destroyed my machine" -- ok now what [21:57] Er. With more information about what happened, and so on. I mean for future reference. [21:58] jonrafkind: The point being, you're already running ancient unsupported software. If you want meaningful interaction with the rest of the Ubuntu community, upgrading isn't really optional at this point# [21:59] whatever [22:20] Oh, go faster, karkalla [22:20] actually it's coming up on 6x as long as the same build on other series [22:21] Anyone around who can abort a stuck build for me? [22:39] maxb: which build? [22:40] bigjools: huh *now* it's unstuck itself [22:40] thanks though :-) [22:40] heh, magic [22:40] ftr, if it's a virtual builder a losa can do it [22:41] Build killed with signal 15 after 150 minutes of inactivity [22:41] lovely [22:41] So either the bzr testsuite takes 6x as long on hardy as jaunty-natty, or that builder is a dud [22:41] the first is unlikely [22:42] though, it's possible it would happen if there were no compiled extensions [22:42] but still unlikely to hit 150m except on a very slow machine [22:43] Hi guys, I don't suppose someone can tell me how to find the Create Recipe link on LP? I found it last night but now I can't find it anywhere! [22:43] Requeued, hopefully it'll hit a different builder last time - Starts in 29 minutes - any buildd admin willing to bump it up the queue? https://launchpad.net/~bzr-beta-ppa/+archive/ppa/+build/2159873 [22:44] kazade: Are you a member of ~launchpad-recipe-beta ? [22:44] erm.. no [22:44] https://launchpad.net/~launchpad-recipe-beta/+join [22:45] kazade: You've been using edge.launchpad.net? [22:45] wgrant, yes [22:45] thanks maxb [22:45] kazade: That's deprecated, and was removed a day or so ago. Access to beta features is now gained by joining the relevant team. [22:46] ok cool that explains it, thanks wgrant [22:46] maxb: we generally add folk to the master beta team only [22:48] Oh, I didn't realize ~launchpad-beta-testers was a member of ~launchpad-recipe-beta. That wasn't mentioned in the initial emails I saw when ~launchpad-recipe-beta was initially created and mentioned [23:45] maxb: no worries