On 23/05/2016 23:52, Julien Puydt wrote:
Hi, On 23/05/2016 15:39, Jonathon Love wrote:hi julien, On 23/05/2016 23:16, Julien Puydt wrote:Hi, On 23/05/2016 14:19, Mattia Rizzolo wrote:Hi Julien, exactly the some days ago you hit this too: On Mon, May 23, 2016 at 09:48:41PM +1000, Jonathon Love wrote:hi, everything i can fix pretty easily, except:Also, you did not use git-dpm, as mandate inside the DPMT: https://wiki.debian.org/Python/GitPackagingthere are a lot of tutorials which explain how to start a repo from scratch using DPMT, but it's hard to know what to do with an established repo. i could easily solve this by nuking the repo and starting over, but this is frowned upon.Mind sharing with Jonathon how you successfully solved it? :)so do i start out be reverting all the commits after the original `gbpimport-orig blah.orig.tar.gz`, and then do all the DPMT stuff after that?that would be kind of ugly...any advice here would be appreciated.It's possible, not well documented maybe, but with some trials and thoughts it can be done.From memory, I used : git-dpm record-new-upstream --allow-changes-in-debian-branch --new-tarball-only <path-to-tarball>if i run that, i get git-dpm: ERROR: Missing file debian/.git-dpm do i need to do a `git-dpm init` first? i.e. git-dpm init ../python-nanomsg_1.0.orig.tar.gz but then i've already told it where the tarball is. any other pointers? thanks for your help jonathonPut: debianTag="debian/%e%v" patchedTag="patched/%e%v" upstreamTag="upstream/%e%u" in debian/.git-dpm and see if that makes it happy...
so the issue is that that file doesn't exist ... but if i create it with those three lines in it, then:
git-dpm record-new-upstream --allow-changes-in-debian-branch --new-tarball-only <path-to-tarball>
doesn't do anything. my understanding is that you add those three lines *after* .git-dpm has been created.
so i'm still trying to figure out the right way to create it in this situation.
with thanks jonathon