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