=== bilal_ is now known as bilal [16:51] all: hi, what does it mean when import branch has only "Partial success" ? [16:51] My branch: https://code.launchpad.net/~gtg/gtg/liblarch [16:52] I don't see any error in logs but the latest revision is not fetched [18:21] izidor: It means the importer made progress but stopped after importing a defined number of revisions, and will reschedule another run to make more progress / complete the import. Which is seems to have now done [18:37] hey guys... how does the branch= work for the git import? [18:38] bzrlib.plugins.git.errors.NoSuchRef: The ref refs/heads/dev. was not found in the repository at git://github.com/ecere/sdk.git,branch=dev.. [18:40] Looks like you've got an extra . character in there [19:03] Can somebody please remove the upstream link from https://launchpad.net/ubuntu/+source/youtube-dl ? [19:03] It is linked to an incorrect project. [19:10] Done [19:10] Thanks. :) === yofel_ is now known as yofel [19:11] * Logan_ wishes Launchpad would track GitHub bugs. [21:10] maxb: For example the other branch (which does work) https://code.launchpad.net/~jerstlouis/ecere/ppaPrecise [21:10] display exactly the same :P [21:11] I don't know how that one's working. You do have an extra '.' in there [21:12] maxb: I never wrote those . I swear!! [21:12] maxb: I'll delete the dev branch and do it over again.. [21:13] it's annoying, the recipes will get deleted too? [21:13] Don't delete it, I'll change the url [21:13] oops | [21:13] :| too late [21:15] I hate how you can't 'edit' the git import path... [21:16] I deleted a ppa once, then regretted it because you're unable to create a new one with the same url (which was the project name) [21:17] I guess it makes sense for other users to not be allowed to "take over" PPAs, but not the user of the old one [21:17] Yeah, for git imports editing the url could probably be allowed [21:17] that'd be nice :) [21:17] There are interesting issues in the implementations of some of the other import types, though [21:18] maxb: So I recreated it... [21:18] This branch is an import of the HEAD branch of the Git repository at git://github.com/ecere/sdk.git,branch=dev. [21:18] Hmm, so those ppa imports of yours with the extra dots in them seem to have imported master [21:18] is that correct / different ? [21:18] why the heck are there . there anyways [21:18] Oh they did?? [21:18] * maxb has a go at reconfiguring them [21:18] thanks man. [21:19] Yeah. death to the dots man. [21:19] having the URL on its own line and the . in the same font [21:19] is very confusing [21:20] (and the git import editbox should error on an invalid path ;| especially since you can't edit it later... ANd you have to delete associated recipes :P) [21:20] jelmer: Around, perchance? [21:22] branch=refs/heads/ppa/oneiric ? [21:23] Hmm, neither ,branch=ppa/oneiric nor ,branch=refs/heads/ppa/oneiric seems to have resulted in LP importing something other than master [21:24] that is annoying [21:24] doesn't support the branches with / in them? [21:24] I guess we'll see what happens with dev [21:24] my feeling is it's the / [21:24] that's why it didn't err on the .. [21:24] I had branch=debian before and that worked fine [21:25] Is there a quick fix for this, or should I rename my branches ppaOneiric ? [21:26] * maxb thankful for the 'Import now' button [21:26] Ah, there we go [21:27] ,branch=ppa%2foneiric [21:28] ah, nice :) [21:28] thanks [21:29] are you able to fix them up? :) [21:29] seems like you have some editing controls I don't have :P [21:29] Yeah, I'm a member of ~vcs-imports [21:30] ah nice :) many thanks vcs-importer =) [21:30] OK, they're all good now [21:30] thanks man :) [21:31] Now I'm curious to see if these will build :) I added the libffi dependency... [21:31] also first time I'm trying on Quantal :) [21:31] what's the animal btw? ;) [21:31] Quetzal! [21:31] is that related to Quetzalcoalt ? [21:31] Quetzalcoatl* [21:32] cute little bird [21:33] fitting name for the last release of this cycle of the Mayan calendar! [21:39] ok I fixed the recipes :) [21:42] Missing build dependencies: lib32ffi-dev :S [21:49] lib32? really? [21:50] yeah I dunno what's up with that... yeah my package still builds only as 32 bit even on 64 bit machines... [21:51] and ffi is architecture specific... [21:51] I dunno if I should say lib32ffi5 instead? [21:52] Not if you want to link against it [21:52] Got a link to the failed build? [21:53] sure [21:53] https://launchpadlibrarian.net/112505268/buildlog.txt.gz [21:53] Natty/Lucid says Dependency Wait: https://launchpadlibrarian.net/112517064/buildlog.txt.gz [21:54] hi maxb, ESphynx [21:54] ESphynx: if you use a forward slash you need to URL encode it [21:55] ESphynx: there is branch=foo%2Fbar or ref=refs%2Fheads%2Ffoo%2Fbar [21:55] jelmer: Hi :) yes that seems to be what maxb found out :) [21:56] he fixed them :) [22:16] maxb: Did you find anything there? :| I'm really puzzled what dependency I should list [22:25] ESphynx: So, the quantal failure suggests there was no debian/changelog present after the recipe had been performed [22:27] maxb: hmm somethign wrong [22:27] ESphynx: Meanwhile that natty build is executing in an i386 environment, so of course there's no lib32ffi-dev in existence; libffi-dev is 32-bit anywa [22:27] maxb: https://launchpadlibrarian.net/112517040/buildlog.txt.gz [22:31] Again, in that one, no lib32ffi-dev, except it then went on to fail in a particularly obscure way [22:32] should I say: lib32ffi-dev [amd64] ? [22:33] yes [22:34] There's libffi6 also :| [22:53] https://launchpadlibrarian.net/112525179/buildlog.txt.gz -- wth happened there? it's using a super old version name? [22:53] ecere-0.44pre15prep5amd64 -- where did that come from? [22:54] I guess that's the {debupstream}-0~{revno} ? [22:55] changelog :| [23:47] (0.44.01-0~766~precise1) is earlier than the previous one (0.44.01) ? [23:47] ESphynx: Yes. [23:47] ESphynx: ~ is less than everything -- including nothing at all. [23:48] wgrant: i do'nt understand why I'm getting these errors now :| [23:48] I just set my changelog version to be that... [23:49] ah I had {time}-0~{revno} before [23:49] INFO ecere_0.44.01-0~766~precise1.dsc: Version older than that in the archive. 0.44.01-0~766~precise1 <= 201204161936-0~580~precise1 [23:50] If I go back to {time}-0~{revno} it should be good? [23:51] Well, having a pure time-based version when there are real release version numbers is pretty strange. [23:51] If the PPA has few users, it might best to just pretend the {time}-based package versions never happened. Delete them and rerun the recipe. [23:51] well there has only been one release... [23:52] But anyone who has the package installed would need to manually remove and reinstall it in order to get upgrades. [23:52] and they are daily build PPAs [23:52] and releases are sparse