[00:02] <askhl_> Hi.  The Danish translation of the Ubuntu manual has dropped from 56% or 54% to slightly below 50% at some point these last days.  The manual people have made no changes to the template.  What might be happening?
[00:03] <askhl_> I have a previously exported po-file from Launchpad on my hard drive.  This file contains strings that now only have suggestions.
[01:11] <intgr> Hi, I just created a branch on lp and I'm trying to push a single commit to it, but it's ticking over 9MB already and taking forever
[01:11] <intgr> Am I doing something wrong?
[01:13] <beuno> intgr, that is odd
[01:13] <intgr> Phew, after pushing >10MB it finished
[01:13] <beuno> and this single commit, it doesn't contain any binary files?
[01:13] <intgr> Nope, just a single line changed in a short file
[01:13] <wgrant> intgr: Which project was this, and how did you create the branch?
[01:13] <intgr> https://code.launchpad.net/~intgr/listen/tweaks
[01:14] <wgrant> Which version of bzr are you using?
[01:14] <intgr> I went to their project home, chose "Submit code" and entered branch name
[01:14] <intgr> 'bzr push lp:~intgr/listen/tweaks' failed with:
[01:14] <intgr> bzr: ERROR: Target directory lp:~intgr/listen/tweaks already exists, but does not have a .bzr directory. Supply --use-existing-dir to push there anyway.
[01:14] <intgr> So I added --use-existing-dir
[01:15] <intgr> Sorry, that's where I should have started
[01:15] <wgrant> Ah. So, you should probably have just run 'bzr push lp:~intgr/listen/tweaks', without creating it through the web UI first.
[01:15] <wgrant> That way it would have shared revision data with lp:listen, and you would have only been uploading your changes.
[01:15] <intgr> Oh...
[01:16] <wgrant> You don't actually need to go through the web UI at all; just push, and the branch will be created.
[01:16] <intgr> That's kinda non-obvious at first
[01:16] <intgr> GitHub and Bitbucket work the other way around.
[01:18] <wgrant> That's because Git is somewhat crippled: it doesn't really have the ability to share revision data between repositories.
[01:18] <wgrant> So you have to copy it all server-side first.
[01:18] <wgrant> With Bazaar, your branch just has a reference to lp:listen.
[01:19] <intgr> Why can't the web UI do that when I'm branching?
[01:19] <wgrant> I think bzr will avoid stacking if the directory already exists, but I couldn't be sure.
[01:20] <intgr> Then lp needs an advance warning when creating branches :)
[01:20] <wgrant> Probably, yes.
[01:22] <intgr> Thanks
[02:06] <thumper> man I want to fix the +register-branch page
[02:07] <wgrant> Delete delete delete.
[02:08] <thumper> wgrant: not quite that easyu
[02:08] <wgrant> :(
[02:09] <wgrant> Stick imports and mirrors into a single field. Then delete.
[02:09] <thumper> that is part of it
[02:09] <thumper> but the register branch page should give instructions on how to push
[02:46] <lfaraone> do the launchpad PPA builders have internet access?
[02:48] <mwhudson> lfaraone: no
[02:48] <lfaraone> mwhudson: great, thanks.
[03:10] <taiyal> yay this channel exists
[06:09] <poolie> where do people tend to talk about common patterns for using ppas? if anywhere?
[06:09] <poolie> like scripts they might use
[06:11] <nigelb> #ubuntu-motu might be a good place.
[06:11] <poolie> mm good idea
[06:12] <poolie> is there a list or forum?
[06:13] <nigelb> motu does  have a list but I don't think ppa audience would be there
[06:13] <nigelb> ppa uploader audience rather
[06:30] <poolie> thumper: is there any concept in the recipe builder of building just one tag, or the latest tag, rather than the tip of a branch?
[06:30] <poolie> or maybe of building only when the tag changes?
[06:30] <thumper> poolie: I'm not sure, that'd be a bzr-builder question
[06:31] <wgrant> poolie: There is #ubuntu-packaging. But it's fairly dead.
[06:31] <thumper> one thing we are trying to do is to use the builder manifests
[06:31] <wgrant> As for lists, there's really only launchpad-users.
[06:31] <thumper> which contain the revids of the different branches used
[06:31] <thumper> and compare against the last manifest
[06:31] <thumper> so if the revids of the branches change, we build again
[06:32] <thumper> so if bzr-builder started to support tags (if it doesn't already)
[06:32] <thumper> then it shouldn't be too hard (I think) to hook it all up to work as expected
[06:34] <poolie> so it would perhaps need only a builder change and nothing else?
[06:34] <poolie> that would be nice
[06:34] <poolie> i'm going to post to udd
[06:34] <poolie> you two should join, if you haven't already
[08:58] <poolie> can i copy from the main archive (for maverick) directly into a ppa?
[08:59] <wgrant> Yes, but it's generally discouraged. Why?
[08:59] <noodles775> wgrant: via the API its not discouraged is it?
[08:59] <poolie> i want to make maverick's up-to-date bzr-rebase available in our ppa for lucid
[08:59] <poolie> for example
[08:59] <wgrant> noodles775: Well, it's often not the right solution.
[08:59] <noodles775> wgrant: ah, you mean policy-wise...
[08:59] <poolie> it should be pure python
[08:59] <wgrant> poolie: Does it need a rebuild?
[08:59] <wgrant> If not, you can do a copy with binaries through the API.
[08:59] <poolie> i don't think so? would it?
[09:00] <wgrant> You'd have to test. But it's probably fine.
[09:00] <poolie> i don't suppose there's a standard tool for that?
[09:00] <wgrant> dpkg -i :P
[09:00] <poolie> snort, i meant an api tool to copy it
[09:00] <wgrant> Oh.
[09:02] <wgrant> https://edge.launchpad.net/ubuntu/+archive/primary/+copy-packages?field.name_filter=bzr-rebase&field.status_filter=published&field.series_filter=maverick
[09:02] <wgrant> Use that.
[09:02] <wgrant> Oh wow, that's still close to timing out.
[09:02] <wgrant> What is that view doing..!?
[09:03] <noodles775> wgrant: *that* was what I thought was discouraged... hence the API ;)
[09:03] <wgrant> noodles775: Well, with the filter prefilled it tends to work.
[09:03] <poolie> you just made up the url by hand?
[09:03] <wgrant> poolie: Yes.
[09:03] <poolie> i'm not complaining
[09:03] <noodles775> :)
[09:03] <wgrant> Make sure you copy with binaries, though.
[09:04] <poolie> oh, or what?
[09:04] <wgrant> Or you'll end up with identically-versioned binaries that are in fact different.
[09:04] <wgrant> And that is wrong.
[09:05] <poolie> right
[09:06] <poolie> !
[09:06] <poolie> that says it copied the ppc, armel, sparc packages etc
[09:06] <poolie> i assume that's just "will try to copy"?
[09:06] <poolie> or it's misunderstanding the arch=any
[09:06] <wgrant> arch=all
[09:06] <wgrant> The same thing happens when copying within a PPA, which is a little confusing.
[09:06] <poolie> sorry, =all
[09:07] <wgrant> While normal PPAs build only for the Big (Three|Two), they publish on all.
[09:07] <wgrant> Which means arch-indep packages publish everywhere.
[09:07] <wgrant> And arch-dep binaries copied from the primary archive will also publish everywhere.
[09:14] <poolie> right
[09:16] <poolie> so, seriously, it seems like we ought to put tools to do this into hydrazine or something
[09:16] <wgrant> Probably.
[09:16] <poolie> not just this specific case but ppa copying in generally
[09:16] <poolie> it's very amenable to scripting
[09:19] <poolie> some oopses on that page
[09:19] <poolie> probably i should add that
[09:20] <poolie> maybe not tonight
[09:26] <poolie> that's timing out a bit fwiw
[09:30] <noodles775> poolie: yeah, that url is not meant to be used with the main archive (which is why its not linked anywhere, and if you remove the /+copy-packages it'll even redirect to the distro page instead).
[09:30] <poolie> ok
[09:30] <poolie> well, thanks for the tip
[09:30] <poolie> that saved me some time
[09:30] <poolie> (assuming it worked)
[09:30] <poolie> and then i may add that to hydrazine in a cleaner way later
[09:30] <poolie> probably not next week though
[09:31] <noodles775> Great (the api version works well.
[09:31] <poolie> are you on the udd list?
[09:31] <noodles775> I am, but have not been keeping up with it.
[09:31] <poolie> np, there's not a lot of stuff
[09:32] <poolie> i'm just about to post some thoughts on the packaging exprerience
[09:32] <poolie> not to load more work on you
[09:32] <noodles775> Great, I'll look out for it :)
[09:32] <poolie> perhaps people can tell me i'm doing it wrong
[09:32]  * wgrant subscribes to udd@
[09:32] <wgrant> Is it a Launchpad mailing list?
[09:33] <poolie> yes, but its actually ubuntu-distributed-devel
[09:33] <wgrant> Ah.
[09:33] <wgrant> Well, there's ~ubuntu-distributed-development, which tells me to use a lists.u.c list.
[09:33]  * wgrant does so.
[09:41] <poolie> oh, sorry
[09:41] <poolie> it's that policy thing about ubuntu lists being over there
[17:00] <Tucos> there are no post-push hooks in launchpad are there? (looking for an irc commit bot without too much labour ^^)
[17:02] <jelmer> Tucos: That's correct.
[17:03] <Tucos> any polling commit bots you know of?
[18:57] <ChogyDan> I'm trying to put a kernel into a ppa, and I don't want to upload the full source every upload.  In Maverick, when I grab the source, it includes the minor version number, linux-2.6.35-17.23.tar.gz, where as in lucid, it was just linux-2.6.32.tar.gz.  How do I get the debuild and dput commands to recognize the proper source file?  I'm not sure what to name it
[19:40] <maxb> ChogyDan: linux_2.6.32.orig.tar.gz (assuming your source package name is just 'linux')
[19:46] <ChogyDan> maxb: thanks
[19:47] <ChogyDan> I realized the error may not be with me.  It looks like when I apt-get source, it is giving me just one big tarball instead of the upstream tarball and then the ubuntu patches.  o well!  Just a little extra upload
[20:04]  * mtaylor has once again lost the "merge users" link ... 
[20:26] <maxb> mtaylor: /people/+requestmerge
[21:03] <micahg> jcastro: do you think an adopt me button in LP is worthwhile for packages instead of the wiki?
[21:05] <jcastro> micahg: sort of like "Bug Supervisor"?
[21:08] <micahg> jcastro: well, not exactly it could be a little different than subscribe so that people would know that they take care of it
[21:08] <micahg> and a lp/~me/+adopted-packages could be created
[21:09] <micahg> one might want to be subscribed, but not adopt
[21:11] <lifeless> what would adopt do *differently*
[21:12] <micahg> lifeless: well, hmmm..I guess the only application is for triage...
[21:12]  * micahg gives up on the idea
[21:13] <jcastro> I think it's worth discussing
[21:13]  * jcastro jots it down
[21:13] <micahg> lifeless: I guess they could be the distro "experts" on the package
[21:25] <jenkins> when I click "delete branch" i get "This branch cannot be deleted as it has 1 branch sharing revisions." how do i work out which branch and unlink them?
[22:53] <gregcoit> I think I broke lp: Sorry, there was a problem connecting to the Launchpad server. Try reloading this page in a minute or two. If the problem persists, let us know in the #launchpad IRC channel on Freenode.
[23:11] <thumper> gregcoit: were you browsing a branch?
[23:11] <gregcoit> thumper: yes
[23:12] <thumper> gregcoit: the branch browser is somewhat flakey
[23:12] <gregcoit> it'
[23:12] <gregcoit> it's back btw
[23:12] <gregcoit> and no worries
[23:39]  * maxb bemoans the build queue
[23:44] <wgrant> I believe jelmer is working on a fix for most of that.
[23:44] <wgrant> Oh.
[23:44] <wgrant> All manual. Yay.