On Sat, 28 Feb 2009, Stéphane Glondu wrote:
Hello Mike,
Hey Stephane,
This is probably because of a misuse of pristine-tar.
Well, that's not too surprising since this is the first time I've used it. :)
All the git-buildpackage family commands must be called with the pristine-tar option, or alternatively, you can put a gbp.conf file in your debian (I've done it for mlgmp). You must remove any mlgmp_*.orig.tar.gz that might be around, because it won't be regenerated if it already exists. See [1].
Gotcha, thanks.
BTW, you just imported the last release of your package and forgot all the history of this package... is it intentional?
Nope, just an oversight.
We usually don't want to forget the history when something is migrated to git. There are scripts available [2] to convert a svn repository in svn-buildpackage format with upstream tarballs into a git-buildpackage format with upstream and pristine-tar branches.
I do know about the script, but I intentionally didn't use it to force myself to learn a bit more about git and git-related packaging tools. I'll likely be using it for the rest of my packages that I plan to transition though.
This script has been used to convert all our repositories so far. It is very hackish and might be difficult to use, but at least Samuel and I can use it, and we can do migration for you if you want.
I probably won't be able to get back to this until monday and since I'm still learning the ropes of git would you mind fixing the mlgmp repository for me (the broken orig.tar, history and anything else you see fit)? If you do and think the package is otherwise in good shape, feel free to make an upload as well.
Cheers, -Mike