Re: Bug#723175: [SoB osgearth] Vcs is not up to date
On Wed, Sep 18, 2013 at 01:45:00PM +0200, Sebastiaan Couwenberg wrote:
> Thanks for looking into osgEarth so shortly before you VAC.
Well, forcing people to wait is demotivating ... and I want to push a
bit on the motivation side, right. ;-)
> On 09/18/2013 01:25 PM, Andreas Tille wrote:
> > on SoB Wiki page you asked for sponsering your package. I checked
> > out VCS via
> > gbp-clone ssh://git.debian.org/git/pkg-grass/osgearth.git
> > and found an old version there which is lagging behind mentors please
> > commit everything to VCS to make sure it is in sync with what you intend
> > to upload. I'll generally rebuild a package from VCS via
> > git-buildpackage.
> The changes for the package on mentors are in git, but in the jessie
> branch not in master. This should work for the moment:
> gbp-clone --debian-branch=jessie
Ahhh, that was a bit hidden from the workflow I'm usually following
> I'll merge the changes for jessie into master and push it to git.debian.org.
.../osgearth (master) $ git-buildpackage
gbp:info: Orig tarball 'osgearth_2.4.0+dfsg.orig.tar.gz' not found at '../tarballs/'
gbp:warning: Pristine-tar branch "pristine-tar" not found
pristine-tar: no pristine-tar branch found, use "pristine-tar commit" first
gbp:error: Couldn't checkout "osgearth_2.4.0+dfsg.orig.tar.gz": /usr/bin/pristine-tar returned 1
.../osgearth (master) $ git branch
Hmmm, it seems pristine-tar branch is missing. I'm used to import upstream
git import-orig --pristine-tar
which enables the byte-identical recreation of the upstream tarball. While
I could download the tarball for sure would you consider also injecting this
(or am I missing something again?)