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