[06:28] <tonyFlury> i have my code on launchpad in a simple hierarchy for development purposes - how do i get launchpad to build a deb which can be downloaded by others and installed ?
[06:29] <tonyFlury> or do i have to build the deb myself - based on a daily/weekly build off my own machine ?
[06:30] <geser> tonyFlury: https://help.launchpad.net/Packaging/SourceBuilds/Recipes
[06:33] <tonyFlury> geser - now i need someone to translate that lot into english - it made no sense to me how i specific which file in my code branch goes into which directory on the installation target machine
[06:38] <tonyFlury> geser - is there an example build recipe that i can use as a basis for my recipe ?
[06:40] <geser> you need two parts: a) a debian/ directory with those packaging files to build a deb from a source package and b) a recipe to build a source package from your bzr branch
[06:41] <geser> for a) you could take a look at https://wiki.ubuntu.com/PackagingGuide for how packaging works (and what all those files in debian/ do)
[06:42] <geser> and for b): I didn't work with recipes yet myself, so I don't know if there are any good examples
[06:42] <tonyFlury> ok - i am not sure i understand to be honest - I can build a deb on my local machine - but I can't work out (admitedly i have skim read it) how the recipie specifies which file to put where
[06:43] <tonyFlury> so i create my deb directory - and upload it to launchpad (as a specific branch to my project) ?
[06:44] <geser> the recipes just builds a source package from your bzr branch (e.g. when you commit a new revision), then the source package gets build by the PPA buildds
[06:45] <geser> it's like you would upload a source package for your new revision youself to your PPA, just automated
[06:45] <wgrant> tonyFlury: The recipe tells Launchpad to combine branches in a certain way to create a Debian source package.
[06:45] <wgrant> The Debian source package needs to specify where to put the files. That's where the Packaging Guide that geser linked comes in.
[06:45] <wgrant> You still need normal Debian packaging; recipes just automate regular builds.
[06:46] <tonyFlury> wgrant: thanks - i think i need an actual example of how it actually works in practice - i.e. a working recipe and package directory ....
[06:49] <tonyFlury> presumanbly you build the deb directory with empty files with the same names as the actual files in your source code - and the recipe will then replace the files with the actual contents
[06:52] <wgrant> tonyFlury: Recipes don't go near that part of the build.
[06:52] <wgrant> That's all the source package, which is Launchpad-independent.
[06:53] <tonyFlury> ok - then i am lost completely :-(
[06:53] <wgrant> tonyFlury: It's best to start with the packaging guide, ignoring recipes until you have something working locally.
[06:53] <wgrant> Recipes are a layer on top of that.
[06:53] <tonyFlury> i know how to build packages locally - had that working already
[06:54] <wgrant> How did you do it?
[06:55] <tonyFlury> i built a directory - with some control files - and then a tree under there with each file in it's correct place in the tree
[06:55] <wgrant> Ah
[06:55] <wgrant> Sounds like you manually built a binary package.
[06:55] <wgrant> Which there's no reason to ever do :)
[06:55] <wgrant> Launchpad doesn't accept binary package uploads; you need to create a source package that Launchpad can use to create binary packages.
[06:55] <tonyFlury> well - when you work with Python there is no difference between a source and binary
[06:56] <wgrant> There often is (eg. C extensions)
[06:56] <tonyFlury> I am not asking launchpad to upload a binary package.
[06:56] <wgrant> And binary packages don't always contain binaries.
[06:56] <wgrant> It's a Debian packaging term.
[06:56] <wgrant> A source package takes the original source tree and produces a deb
[06:56] <wgrant> The deb traditionally being called a binary package.
[06:57] <geser> tonyFlury: if you want to have a deb ready for downloading on Launchpad, then LP has to build that deb for you (for your PPA)
[06:57] <tonyFlury> yes - I know - what in does - i don't understand how it works ...
[06:57] <tonyFlury> and the guide does not give examples
[06:59] <wgrant> You need to follow the packaging guide to produce a source package such that you can run 'debuild' locally to produce a deb
[06:59] <tonyFlury> i can do that ....
[06:59] <wgrant> Recipes are a step after that, so just ignore that they exist for now
[07:00] <tonyFlury> well ignoring them wont help when i want to produce a daily build for my project that others can download and install
[07:00] <tonyFlury> which i want to be able to do in the next few weeks - ignoring the complicated stuff is not an option -
[07:00] <wgrant> Do you have a .dsc?
[07:01] <wgrant> It's not complicated.
[07:01] <tonyFlury> no - i haven't
[07:01] <wgrant> It just requires that you have a source package first.
[07:01] <wgrant> So not ignoring it now is silly, as you can't do anything with recipes yet.
[07:01] <tonyFlury> and to understand the badly written guide - that assumes you know what you are doing anyway
[07:02] <tonyFlury> wgrant - even if i had a source package which i can use to locally install - the recipe guide still makes no sense
[07:02] <wgrant> It makes sense when you know how source packages work.
[07:03] <wgrant> Recipes just combine branches to create a source package.
[07:03] <tonyFlury> wgrant - I see no point in explaining yet again that i do - that i have built them before
[07:03] <wgrant> They don't do packaging for you.
[07:03] <wgrant> tonyFlury: AFAICT you've manually *binary packages* (debs), not a source package.
[07:04] <wgrant> Regardless of content, a deb is radically different from a source package.
[07:04] <wgrant> A deb is a final installed tree of files with a little bit of metadata
[07:04] <wgrant> A source package specifies how to create that tree.
[07:04] <wgrant> A recipe specifies how to create the source package.
[07:04] <geser> tonyFlury: so you have a working debian/rules file (and other files in debian/)?
[07:04] <tonyFlury> wgrant: thanks for trying to help - but i think you and i are getting confused about what each other are saying
[07:05] <tonyFlury> geser - i can have one for my project in the next hour - as I have said repeatedy build a locally installable deb for my python project is not complicated
[07:05] <wgrant> It doesn't matter if it's complicated.
[07:06] <wgrant> All that matters is if you have a source package, consisting of a debian/ directly with rules, control, etc. in it.
[07:06] <wgrant> That can produce that deb.
[07:06] <geser> tonyFlury: once you have that, you can start worrying about recipes (as recipes need that debian/rules file in the end)
[07:06] <tonyFlury> the point is that i can do it .... yes - assume that i have - and if i don't right now i can in a few hours
[07:06] <wgrant> You need to do that first.
[07:06] <wgrant> Before you can understand what recipes do.
[07:07] <wgrant> Recipes aren't going to make much sense if you're thinking about them in terms of manually building a deb.
[07:07] <wgrant> Because that's not what they do.
[07:07] <tonyFlury> um - believe it or not - I am able to understand stuff by reading .... and i wasn't thinking of them building the deb
[07:07] <wgrant> You just said you *couldn't* understand the guide.
[07:08] <tonyFlury> but hey ho - i will hack it about until it works - or I find an English version
[07:08] <tonyFlury> wgrant - the guide is appalling - it does not actually explain anything - it works on the basis that you already know - ah well
[07:09] <tonyFlury> never mind -
[07:09] <wgrant> That's not a very useful complaint.
[07:10] <tonyFlury> wgrant: it is a valid complaint - there needs to be a guide which actually explains stuff - not an expert reminder.
[07:10] <wgrant> Which guide are you talking about?
[07:10] <wgrant> The packaging guide starts right from basics.
[07:10] <tonyFlury> I am talking about the recipe guide on launchpad
[07:10] <wgrant> Don't look at that yet.
[07:11] <wgrant> It won't make sense until you know what a source package is.
[07:11] <wgrant> Which you do not.
[07:11] <tonyFlury> wgrant: Please stop telling me not to do things
[07:11] <tonyFlury> bye all -
[07:11] <tonyFlury> quit
[07:11] <wgrant> wtf
[07:12] <czajkowski> wgrant: morning :)
[07:12] <wgrant> Hi
[10:30] <io> is there any way to edit an answer on lp?
[10:30] <io> (that you've written)
[10:33] <czajkowski> io: no
[10:50] <io> czajkowski: is that intentional?
[11:23] <czajkowski> io: yes
[11:32] <io> czajkowski: what's the reason for that?
[11:34] <czajkowski> io: not sure I'm sure it's the same logic that stops people going in and editing answers from others and changing information on bugs as well.
[14:43] <askhl> Hi.  Where can I find an overview of the keyboard shortcuts for Launchpad translations?  I can't seem to find it in the guide or google
[14:50] <askhl> Okay, I found them by googling 'Adi Roiban [the guy who implemented them] keyboard shortcuts', but they don't seem to be working, generally speaking.  So never mind
[16:32] <stokachu> hi, who can i talk to about getting a branch made private
[16:33] <czajkowski> stokachu: me
[16:33] <stokachu> czajkowski: may i pm you?
[16:33] <czajkowski> sure
[17:11] <czajkowski> stokachu: that branch is now private
[17:45] <stokachu> czajkowski: great thank you again
[17:46] <czajkowski> stokachu: np
[18:01] <alo21> hi all
[18:02] <alo21> Can I link a project to a team?
[18:03] <matsubara> alo21, you can set a team as the maintainer of the project
[18:03] <alo21> matsubara: could you tell me how?
[18:05] <matsubara> alo21, go to the project home page, look for the maintainer field and click the yellow edit button
[18:05] <matsubara> it should be under Project Information
[18:06] <alo21> matsubara: done..
[18:07] <alo21> matsubara: if i work in bug managment in a specific project
[18:07] <alo21> will my karma linked with the team which is the maintainer?
[18:09] <matsubara> alo21, IIRC, karma is per person only, not for teams, so setting the team as the maintainer won't have any effect on your karma
[18:09] <alo21> matsubara: what does it mean: https://launchpad.net/~ubuntu-it-magazine/+karma
[18:10] <alo21> matsubara: this page shows me total karma of that team
[18:12] <matsubara> alo21, it shows 0 to me. is that what you see?
[18:13] <matsubara> it's likely to be bug https://bugs.launchpad.net/launchpad/+bug/547113 or https://bugs.launchpad.net/launchpad/+bug/422335
[18:13] <alo21> matsubara: yes... I see 0
[18:14] <matsubara> alo21, so, that's it. basically the +karma page for teams doesn't show anything useful at the moment which is related to the bugs above
[18:15] <alo21> matsubara: https://launchpad.net/ubuntu-accomplishments-system/+topcontributors
[18:15] <alo21> here you can see a specific karma in that project
[18:16] <alo21> matsubara: Can i use it in a programme with API?
[18:19] <matsubara> alo21, I think the only karma information exported through launchpad's API is for a person. you probably can get the total karma of your team members and do some fancy stuff with it but the calculation would need to be done by your application. Look at https://launchpad.net/+apidoc for information about the API
[18:20] <alo21> matsubara: I have seen it yet, thanks
[18:20] <matsubara> np
[19:53] <stokachu> when doing branch merges from a proposal how are we supposed to keep original commit messages to show up in the merge?
[20:15] <dobey> stokachu: the original commits will be merged in, when you do bzr merge. the new revision you commit will include them, and you can view them with bzr log -r $NEWREV -n 0 if you want
[20:47] <stokachu> dobey: ah ok thanks
[23:38] <kirkland> howdy!  anyone around who can help me with a new commercial launchpad subscription?