Git help in Debian Med policy seems insufficient
Hi,
I tried to package a Java library which is needed for Beast-mcmc and
which made be available by mail from author only (I asked for an upload
but this did not happened (yet)). Becase the license seems to be OK
(Apache 2.0) I see no real problem in this but IMHO this is a use case
for git to make sure people will have reasonable access to the source.
So I tried:
$ mkdir liboptions-java
$ cd liboptions-java
$ git init
Initialized empty Git repository in /home/tillea/debian-maintain/alioth/debian-med_git/liboptions-java/.git/
$ git import-orig --pristine-tar ../tarballs/liboptions-java_0.0.20120113.orig.tar.gz
What will be the source package name? [liboptions-java]
What is the upstream version? [0.0.20120113]
gbp:info: Importing '../tarballs/liboptions-java_0.0.20120113.orig.tar.gz' to branch 'master'...
gbp:info: Source package is liboptions-java
gbp:info: Upstream version is 0.0.20120113
pristine-tar: committed liboptions-java_0.0.20120113.orig.tar.gz.delta to branch pristine-tar
gbp:info: Successfully imported version 0.0.20120113 of ../tarballs/liboptions-java_0.0.20120113.orig.tar.gz
Now I tested:
$ git tag
upstream/0.0.20120113
$ git branch
* master
pristine-tar
upstream
Seems to look OK for me. Now I tried whether I could get the tarball
out of the archive again:
$ pristine-tar checkout tarball
fatal: Path 'tarball.delta' does not exist in 'refs/heads/pristine-tar'
pristine-tar: git show refs/heads/pristine-tar:tarball.delta failed
Bummer! So what exactly did I wrong? It's a bit unfortunate that vasks
is down currently. If you want to try the specific tarball I uploaded
everything to
http://people.debian.org/~tille/packages/options/
As I said we need a brain dead stupid working mechanism to create such a
Git repository. The procedure written down in our policy seems to not
qualify for this description.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: