[00:26] <poolie> kirkland: did you get an oops?
[00:26] <poolie> are you using lpnet or edge?
[00:26] <poolie> hi btw
[00:28] <kirkland> poolie: howdy
[00:28] <kirkland> poolie: lp.net
[00:28] <kirkland> poolie: i did get an oops, i lost the page already
[00:28] <kirkland> poolie: sorry
[00:28] <poolie> np
[00:28] <poolie> generally speaking filing a bug or pasting the oops here is good if it's hurting you
[00:29] <poolie> otherwise, all the oopses are collected and eventually looked into
[00:29] <kirkland> poolie: cool, thanks a lot
[00:29] <kirkland> poolie: i'll do that next time
[00:29] <poolie> np
[00:44] <ajmitch> is there a way I can search across all LP bugs via the API?
[01:05] <jcsackett> ajmitch: you can search across all bugtasks for a project by using searchTasks on the project in question.
[01:11] <ajmitch> jcsackett: right, I'd seen that, but was wanting to search across all projects as the form on bugs.launchpad.net does
[01:12] <jcsackett> ajmitch: ah. i don't off the top of my head know of any way to do that.
[01:12] <ajmitch> ok
[01:14] <Peng> a/6
[01:14] <Peng> ergh, sorry
[05:35] <ub3rst4r> hi, for some reason when i try to push to a new branch i get this: bzr: ERROR: At lp:lilregdefrag/1.0 you have a valid .bzr control directory, but not a branch or repository. This is an unsupported configuration. Please move the target directory out of the way and try again. Any Ideas?
[05:46] <wgrant> ub3rst4r: It sounds like you terminated the first push.
[05:47] <wgrant> ub3rst4r: Perhaps delete the branch and try again.
[05:49] <ub3rst4r> what branch? mine or launchpads?
[05:49] <wgrant> The one on Launchpad.
[05:49] <ub3rst4r> ok will do thx
[05:52] <ub3rst4r> now it says different rich-root support
[05:52] <wgrant> Ahh.
[05:53] <wgrant> So, it sounds like your local branch is in the 2a format (default in bzr 2.0 and later), while lp:lilregdefrag is still the old 0.92 format. You should upgrade lp:lilregdefrag to 2a (there should be a link on https://code.launchpad.net/~lrc-team/lilregdefrag/main)
[05:54] <ub3rst4r> k i got it
[05:56] <ub3rst4r> thanks :)
[07:28] <eagles0513875> hey guys
[07:28] <eagles0513875> for some reason im not finding the report bug on launchpad
[07:28] <eagles0513875> has it been moved or is it missing?
[07:33] <tsimpson> eagles0513875: where are you looking?
[07:34] <eagles0513875> home page
[07:34] <tsimpson> well, you need a project to report a bug against
[07:35] <eagles0513875> ahh ok
[07:35] <eagles0513875> let me take a look here
[07:35] <eagles0513875> ok tsimpson im looking here https://launchpad.net/ubuntu
[07:35] <eagles0513875> when i click on report a bug
[07:35] <eagles0513875> it takes me to the wiki O_0
[07:36] <tsimpson> it's supposed to
[07:36] <tsimpson> the ubuntu project wants you to use apport, so they default to redirecting you to instructions for that
[07:37] <eagles0513875> ahh ok
[07:38] <eagles0513875> tsimpson: does this apply to kubuntu as well
[07:38] <tsimpson> kubuntu is part of ubuntu, same project
[07:39] <tsimpson> there are instructions on the wiki page describing how to manually report a bug though
[09:56] <daeavelwyn1> hi here
[09:56] <daeavelwyn1> i'm using firefox to post bug report for ubuntu natty
[09:57] <daeavelwyn1> and I just want to say I'm a bit fade up with a recurrent problem
[09:57] <daeavelwyn1> Every time I try to post a bug report
[09:57] <daeavelwyn1> I have the No REFERER Header
[09:57] <daeavelwyn1> error
[09:57] <daeavelwyn1> i've already set my browser to accept this
[09:57] <daeavelwyn1> but it doesn't work
[09:58] <daeavelwyn1> why the hell is there this f... refered header ?
[13:05] <pat79> hi, how do request a renaming of a project?
[13:09] <pat79> other question how do I request project deletion?
[13:14] <wgrant> pat79: In both cases you should ask at https://answers.launchpad.net/launchpad/+addquestion
[13:48] <pat79> wgrant: thanks!
[17:45] <avar> Hi, I've just created a new project and can't find out from the UI how to upload a POT file so translators can start translating things.
[17:45] <avar> I'm sure I'm an idiot and missing something obvious.
[17:45] <avar> ah, there it is
[17:45] <avar> I am an idiot.
[17:56]  * avar created https://translations.launchpad.net/git-i18n
[17:56] <avar> still pending review of the POT file upload
[19:03] <sebrock> will someone help me package netatalk 2.2?
[19:14] <TheEvilPhoenix> sebrock:  uh... why?
[19:15] <TheEvilPhoenix> sebrock:  why not just build from source?
[19:22] <TheEvilPhoenix> sebrock:  i say that because it comes with its own ./configure scripts :/
[20:56] <maxb> sebrock: Asking for help to package a specific package is seldom fruitful. This is because to offer effective help, someone must first go and study the project named in detail. Effectively they must nearly go and package it themselves.
[20:57] <maxb> Instead, you should aim to attempt to package the software yourself, and ask specific questions about any elements you are unsure of.
[20:57] <maxb> this enables people to offer you help much more easily
[22:04] <sebrock> ok guys, been afk for some time
[22:04] <sebrock> I will check it out tomorrow
[22:04] <sebrock> thanks
[23:12] <thomi> Hi - I'm getting errors when LP tries to upload my recipe-built src package because the file already exists with the same version.
[23:12] <thomi> I'm trying to tweak the package dependencies, nothing more. Is there a way around this?
[23:15] <thomi> The help on lp (https://help.launchpad.net/Packaging/UploadErrors) doesn't help much since I'm using a recipe rather than a manual build.
[23:21] <maxb> thomi: Version numbers must change if packages change in any way.
[23:22] <thomi> maxb: so I have to touch trunk in some way to force a new version?
[23:22] <maxb> Not necessarily
[23:22] <thomi> ..or I guess I could delete the old package from the PPA and then re-generate it? (no one's using it yet)
[23:22] <maxb> You still can't reassign versions to different content, even if you delete the old ones
[23:23] <maxb> The PPA still tracks history to that extent
[23:23] <thomi> oh ok
[23:23] <maxb> You do need to use a different version number - you don't need to touch trunk to achieve that
[23:23] <maxb> If a recipe involves multiple branches, it may be appropriate to include the revno of each branch in the overall PPA version string
[23:24] <thomi> ahhh, ok
[23:24] <maxb> Or, you can tweak the recipe definition to change the version as required
[23:24] <maxb> Or, as a bit of a blunt solution, you can use the {date} and {time} substitutions in the version definition
[23:25] <thomi> so, is there a way in the recipe definition to include the version of the 'debian/' nested branch?
[23:25] <thomi> seems to me like the trunk revno + debian revno should give a unique version number...
[23:26] <maxb> indeed
[23:26] <maxb> {revno:name-assigned-to-branch-in-recipe}
[23:29] <thomi> ahhh, cool - thanks
[23:31] <thomi> is it a bug that the recipe contents is wrapped at a very narrow width when viewing it, but not when editing it? e.g. here: https://code.launchpad.net/~sloecode/+recipe/sloecode-daily
[23:40] <maxb> Hmm, that wrapping seems  a bit unnecessary