=== jamesh__ is now known as jamesh [10:25] hi [10:27] I stuck on important issue with building packages from recipe - can't build package imported from GIT - bzr: ERROR: bzrlib.errors.NoSuchRevision: CHKInventoryRepository [10:28] This issue exists for few months and other people also are affected, see https://answers.launchpad.net/launchpad/+question/264781 [10:28] and bug #1433680 [10:28] bug 1433680 in Launchpad itself "NoSuchRevision error during recipe build" [Undecided,New] https://launchpad.net/bugs/1433680 [10:44] bug is reported a month ago, 2 answers are asked, what should I do? [11:51] menesis: labas [11:52] labas, Mantai === bladernr_ is now known as bladernr-lex [14:35] I stuck on important issue with building packages from recipe - can't build package imported from GIT - bzr: ERROR: bzrlib.errors.NoSuchRevision: CHKInventoryRepository [14:35] This issue exists for few months and other people also are affected, see https://answers.launchpad.net/launchpad/+question/264781 [14:35] and bug #1433680 [14:35] bug 1433680 in Launchpad itself "NoSuchRevision error during recipe build" [Undecided,New] https://launchpad.net/bugs/1433680 [14:36] I asked about this launchpad problem few hours ago but didn't got any answer [14:40] how I can help to solve this issue? [15:06] mantas-baltix: You might find somebody in #bzr who can untangle what's wrong with the bzr repository here, but realistically I suspect this will be fixed by adding some kind of native Git recipe building support ... [15:07] mantas-baltix: "bzr check --verbose lp:~baltix/atomix/atomix-debian" shows some inconsistencies, so it might be possible to disentangle. I don't know enough bzr internals though [15:11] cjwatson: thanks for info, but the same build problem appears not only with lp:~baltix/atomix/atomix-debian but also with other repos, imported from git, see bug #1433680 [15:11] bug 1433680 in Launchpad itself "NoSuchRevision error during recipe build" [Undecided,New] https://launchpad.net/bugs/1433680 [15:36] mantas-baltix: Ah, I think the problem is that the upstream tag is bad [15:37] You can see it in "bzr tags", with some tags showing a question mark === charles_ is now known as charles [15:38] mantas-baltix: If you want to help track this down, perhaps see if running a bzr-git import locally on the same repository yields the same incorrect tags [15:44] bzr-git being broken in vivid isn't helping matters [15:47] http://paste.ubuntu.com/10816614/ [15:47] it doesn't help that developers who use git sometimes often like to rebase directly in master or whatever, after an MP was merged in. i've had weird things happen before as a result of that, when building with recipes on lp [15:48] So that's going to take bzr-git debugging [15:48] Rebasing isn't relevant here [15:48] Or maybe the git tag is just broken, I guess I should check that [16:00] well, sometimes tags get dropped when people rebase i guess. the worst problme i've had from rebasing though is that the bzr revno ends up being the same as it was for a previous build, and the upload fails, even though there were new revisions. [16:01] This is not rebases, please stop derailing [16:02] The problem is the upstream tag pointing to something not in the specific branch being imported [16:02] But that's not because of a rebase === menesis1 is now known as menesis === menesis1 is now known as menesis === robfrawley is now known as Guest54511