(forgot to change the subject to attract Git-Experts interest ...) On Thu, Nov 29, 2012 at 08:39:39AM +0100, Andreas Tille wrote: > Hi, > > there seems to be some problem with creating the source tarball from > libvistaio. > Any hint? > > On Thu, Nov 29, 2012 at 12:19:37AM +0100, Gert Wollny wrote: > > Hello Andreas, > > > > > > > Cool. Unfortunately it does not (yet) build for me: > > > > > > ~/tmp $ debcheckout --user tille > > > git://git.debian.org/debian-med/libvistaio.git --git-track '*' > > > declared git repository at > > > git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git > > > git clone git+ssh://ti...@git.debian.org/git/debian-med/libvistaio.git > > > libvistaio ... > > > Cloning into 'libvistaio'... > > > remote: Counting objects: 192, done. > > > remote: Compressing objects: 100% (145/145), done. > > > remote: Total 192 (delta 58), reused 143 (delta 35) > > > Receiving objects: 100% (192/192), 184.98 KiB | 191 KiB/s, done. > > > Resolving deltas: 100% (58/58), done. > > > Branch pristine-tar set up to track remote branch pristine-tar from > > > origin. > > > Branch upstream set up to track remote branch upstream from origin. > > > Use of uninitialized value $srcpkg in substitution (s///) at > > > /usr/bin/debcheckout line 822. > > > > > > ~/tmp $ cd libvistaio > > > ~/tmp/libvistaio(master) $ git-buildpackage > > > dh clean > > > dh_testdir > > > dh_auto_clean > > > dh_clean > > > gbp:info: Orig tarball 'libvistaio_1.2.14.orig.tar.xz' not found at > > > '../tarballs/' > > > fatal: Path 'libvistaio_1.2.14.orig.tar.xz.delta' does not exist in > > > 'refs/heads/pristine-tar' > > > pristine-tar: git show > > > refs/heads/pristine-tar:libvistaio_1.2.14.orig.tar.xz.delta failed > > > gbp:error: Couldn't checkout "libvistaio_1.2.14.orig.tar.xz": > > > /usr/bin/pristine-tar returned 128 > > > > I think if you don't have the tarball, you need to run > > > > git-buildpackage --git-pristine-tar > > > > at least I did it once, when it complained about the missing tarball. > > As far as I know (and see from the prefectly identical output) > git-buildpackage is doing this automatically in case it can not find the > source tarball at the expected location - at least when adding this > option the output remains identically. > > > There is another problem though, I forgot to tag the last upload. You > > can work around this by doing > > > > git tag -d upstream/1.2.14-1 > > git tag upstream/1.2.14-1 > > > > this will delete the tag that I set earlier (*) and then set the tag to > > the current git head. > > > > *) Actually, the tagged version should also work, just not with > > multiarch. Which reminds me that this requires to set a minimum cmake > > version in the dependencies. I'll fix this and the tag first thing in > > the morning tomorrow. > > I do not think that there is a need to tag > > upstream/<upstream-version>-<debian-version> > > If you are properly using pristine-tar as written in our team policy[1] > > git import-orig --pristine-tar /path/to/package_version.orig.tar.gz > > the tagging of upstream versions is done automatically (and is lacking > the '-<debian-version>' part). Once you are done with the Debian > packaging the tag is rather > > debian/<upstream-version>-<debian-version> > > However, there is no point in doing this tagging before we upload the > read package to the Debian mirror (in case of an initial package upload > I do even delay the tagging until the package was acceted by ftpmaster.) > > Kind regards > > Andreas. > > > [1] http://debian-med.alioth.debian.org/docs/policy.html#git-tips > > -- > http://fam-tille.de > > > -- > To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20121129073939.ga4...@an3as.eu > >
-- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121129080556.gc4...@an3as.eu
