> 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_4.3.3.1.orig.tar.gz`.
Did that, thanks for the hint. Anything else to be done? –Nico On Thu, Mar 5, 2015 at 10:15 PM Sebastiaan Couwenberg <[email protected]> wrote: > 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 4.3.3.1 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_4.3.3.1.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: > > http://pkg-grass.alioth.debian.org/policy/packaging. > html#push-package-to-alioth > > Kind Regards, > > Bas > > -- > GPG Key ID: 4096R/6750F10AE88D4AF1 > Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact > [email protected] > Archive: https://lists.debian.org/[email protected] > >
