[00:15] hmm, a branch I've uploaded half an hour ago is still updating and I've already asked for a merge and got a mail from noreply@launchpad.net saying that there are no revisions and my branch.. will my merge proposal get updated once branch is scanned? === fta_ is now known as fta === PsyTrance_ is now known as PsyTrance === yofel_ is now known as yofel === Ursinha-afk is now known as Ursinha [06:23] Hi I would like to unify my launchpad accounts (created due to some confusion) === arjun_ is now known as arjun === arjun_ is now known as arjun [07:00] arjun: you can do that yourself [07:01] there should be a request merge button on the account page === arjun_ is now known as arjun === bpeel_away is now known as bpeel === arjun__ is now known as arjun === bpeel is now known as bpeel_away === Jordan_U_ is now known as Jordan_U [08:53] Do I need to start a project to set up a PPA? [08:53] orly_owl: No. [08:53] Projects are currently unrelated to PPAs. [08:53] You'll find a link to activate a PPA if you click on your name in the top right of any Launchpad page. [08:53] ah thanks [08:59] is it ok if Displayname and PPA name are the same? [09:03] orly_owl: It will work. But the PPA name is to be used in a URL, and the display name in the UI (and the name of the archive key), so you probably want them to be different. [09:03] The default display name used to be something like 'PPA for Some User' [09:03] There's no default any more, but I'd recommend using something along those lines. [09:05] oh [09:05] But it still works if they're the same? [09:05] Yes. But it's probably not the right thing to do. [09:05] :/ [09:05] The name is something like 'ppa', and the display name 'PPA for William Grant' [09:06] ok [09:06] It doesn't matter exactly what they are, but that's the sort of style that's intended. [09:06] well [09:06] i made them almost the same === _martin is now known as m4rtin === bilalakhtar is now known as bilalakhtar_ [09:35] hmm, did LP always display the LP account name and not the full name next to the "Log out" button? [09:35] no [09:36] the full name has led to confusion [09:40] how so? persons with multiple accounts? [09:56] the display name isn't unique [09:57] so yes [09:57] there is/was a bug around it [09:57] geser: but also [09:57] if you ask someone 'whats your account name' its hard for them to answer with the display name shown [09:58] and there are lots of times you want to ask that: to subscribe someone, to help them with bzr, etc [10:03] lifeless: OTOH, unfriendly names aren't shown anywhere else in the UI. [10:04] It seems inconsistent to have one in such a prominent location. [10:04] In particular, it looks really wrong to have an unfriendly name next to the usual person icon. [10:06] wgrant: perhaps we should show both ? [10:07] wgrant: and its a lie to say its not shown anywhere else : branching instructions are a place where its shown. But yes, its not common. [10:07] lifeless: Ah, true, forgot them. === jelmer is now known as Guest99497 === Guest99497 is now known as jelmer === yofel_ is now known as yofel === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [15:25] hi, i cant seem to trigger maverick builds for https://code.edge.launchpad.net/~rekonq/+recipe/rekonq-daily [15:25] but i can trigger builds for other ppa's fine [15:25] for eg: https://code.edge.launchpad.net/~neon/+recipe/project-neon-kdetoys [15:26] shadeslayer: IIRC there was an issue with the maverick build that rockstar was working on [15:27] ok but why do the other PPA's build fine? [15:27] i triggered the builds for the neon ones last night and it built fine [15:28] shadeslayer: in that case I'm not sure [15:28] im perplexed as well :( [16:44] what's the right way to push a branch based on a ubuntu branch (like lp:ubuntu/rhythmbox/maverick in this case) to launchpad? I pushed to lp:~marienz/rhythmbox/blah, which worked but took a bit longer than I expected. [16:45] hmm [16:46] id say : lp:rhythmbox : but im not sure that thats what you mean [16:47] it stacks it on lp:rhythmbox, yes. [16:47] I was wondering if there was a better (faster) way, possibly stacking it on the ubuntu branch. [16:47] ah.. no idea on that ... [16:47] marienz: you branched lp:ubuntu/maverick/rhythmbox? [16:48] then push to lp:~marienz/ubuntu/maverick/rhythmbox/blah [16:49] ahh, that works? I was assuming I'd always need a single component between my accountname and the branch name I make up [16:49] is this documented somewhere? [16:51] I only know of https://wiki.ubuntu.com/DistributedDevelopment/Documentation/SeekingSponsorship [16:51] (this did what I wanted, thanks) [16:51] you should perhaps also read https://wiki.ubuntu.com/DistributedDevelopment/Documentation for more context [16:52] perhaps I should (I don't really do this frequently enough for all the details to stick in my memory, if you know what I mean) === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [17:28] Im having trouble with referer headers on the site [17:29] can someone help? === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === kancerman_ is now known as kancerman [19:18] Could someone rescore https://edge.launchpad.net/~bzr/+archive/proposed/+build/1928583 ? It missed publication of a build-dep by a few minutes - I've asked for a retry, but now it needs to go through the far too huge queue again :-( [19:19] that sux [19:20] A buildd-admin around at weekends would be nice :-) [19:20] shame you cant score own packaging [19:21] that would be slightly cheating :-) [19:21] thers not evven a request solution on launchpad [19:21] like get rescored for stuff that matters [19:23] im just saying that there should be a launchpad request opt-in for admins to know who is requesting what [19:23] irc shouldnt be only port of call specially on sunday [19:29] actually never mind, I'm reuploading anyway [20:47] Dear people, how can I write a proper recipe when the upstream author included an outdated debian directory? Can I somehow remove the debian directory within the recipe? [20:48] Something like this: [20:48] # bzr-builder format 0.2 deb-version 0+{revno}+{time} [20:48] lp:~vcs-imports/yarp/main [20:48] run bzr remove debian [20:48] nest debian lp:~annevanrossum/robot3d/yarp-packaging debian === menesis1 is now known as menesis [21:16] Okay, I did something that is probably not allowed. [21:16] I changed at "Branch details" the owner. [21:17] If I now want to get the branch, it gives the following error: [21:17] bzr branch lp:~robot3d-team/robot3d/debian [21:17] bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~annevanrossum/robot3d/trunk/". [21:18] I will move it back, I hope it will be solved then. [21:20] Yes: bzr branch lp:~annevanrossum/robot3d/debian does work... === Ursinha is now known as Ursinha-afk [21:33] MrQuincle: it's a bug in Launchpad, where if you move a branch on which another is stacked, the bzr-level stacking metadata isn't updated [21:34] The issue can be worked around by resetting the bzr-level metadata to point to the new name of the branch === Ursinha-afk is now known as Ursinha [21:34] Here is the script I use for doing that: http://paste.ubuntu.com/482024/ [21:35] * maxb afk [21:36] Let's check that because I placed everything back, but now it remembers the other "owner" === bpeel_away is now known as bpeel [21:46] Shit, now I am in even more trouble. [21:47] "Invalid stacked on location: /~annevanrossum/robot3d/trunk" it didn't say that before... [21:51] Everything seems to be normal [21:51] Thanks a lot for your script [22:08] MrQuincle, maxb: I'm hoping to get the fix for moving a branch that is stacked on into LP this cycle [22:09] thumper: Nice! === bpeel is now known as bpeel_away [22:54] Is it perhaps possible to mirror something excluding the "debian" directory? [23:03] I am still clueless about what to do with an outdated "debian" directory. [23:04] I've also been reading through this: https://wiki.edubuntu.org/MeetingLogs/devweek1007/DailyBuilds but it assumes that the "upstream" debian directory is up to date. [23:34] Okay, guys, I don't know if it is intended to run shell commands... [23:34] On my local machine I can just do:# bzr-builder format 0.2 deb-version 0+{revno}+{time} [23:34] lp:~vcs-imports/yarp/main [23:34] run rm -rf debian [23:34] I know you guys probably get this all the time, but what's the word on the LP wiki? [23:34] nest yarpdeb lp:~annevanrossum/robot3d/yarp-packaging debian [23:34] MrQuincle: You can't nest inside a directory that already exists? [23:35] No, it gives conflicts, and I think that's okay to do. [23:35] But he run rm -rf debian command works fine on my local machine [23:36] I am just curious if you are taking that into considering on Launchpad [23:36] Some dickhead might do "run rm -rf /" [23:36] I hope that's accounted for... ;) [23:36] You can't use 'run' in recipes on Launchpad. [23:37] Aha :) [23:38] For me it runs perfectly locally if I include this. So, that's the only thing that holds me back from using it on Launchpad. [23:38] Do you want to exact errors? [23:38] I will run it again locally [23:40] anne@gamix:~/mypackages/tryout$ bzr dailydeb yarp.recipe ~/temp/yarp [23:40] Conflict adding file changelog. Moved existing file to changelog.moved. [23:40] Conflict adding file control. Moved existing file to control.moved. [23:40] Conflict adding file libyarp.install. Moved existing file to libyarp.install.moved. [23:40] Conflict adding file rules. Moved existing file to rules.moved. [23:40] Conflict adding file yarp-bin.install. Moved existing file to yarp-bin.install.moved. [23:40] bzr: ERROR: Conflicts... aborting. [23:41] No surprise of course. But I don't see an easy work around... Perhaps a merge first... [23:41] In which I delete the debian directory.