Re: netCDF Strategy
> Can you push your pristine-tar branch too, or if you didn't commit the
> new upstream release to the pristine-tar branch you can do so
> retroactively with `pristine-tar commit ../netcdf_126.96.36.199.orig.tar.gz`.
Did that, thanks for the hint.
Anything else to be done?
On Thu, Mar 5, 2015 at 10:15 PM Sebastiaan Couwenberg <firstname.lastname@example.org
On 03/05/2015 10:02 PM, Nico Schlömer wrote:
>> The tags for the upstream releases are also missing
There is no pristine-tar commit for the 188.8.131.52 tarball.
Can you push your pristine-tar branch too, or if you didn't commit the
new upstream release to the pristine-tar branch you can do so
retroactively with `pristine-tar commit ../netcdf_184.108.40.206.orig.tar.gz`.
The gbp.conf included in the package has pristine-tar enable by default,
so you only need to use git-import-orig (without the --pristine-tar option).
If you created the pristine-tar branch instead of cloning it from the
git repository on Alioth, you need to use `git push origin pristine-tar
--set-upstream` to have the branch track the origin repository. `git
branch -av` will report the number of commits your branch is out of sync
with the repository on Alioth.
This is documented in the Debian GIS policy I linked earlier:
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
Archive: [🔎] 54F8C768.email@example.com" target="_blank">https://lists.debian.org/[🔎] 54F8C768.firstname.lastname@example.org