[pycoast] tag upstream/0.5.4+dfsg.1 created (now d4dfdaf)

[Sebastiaan Couwenberg]

On 07/03/2016 07:43 PM, Antonio Valentino wrote:
> Il 03/07/2016 19:33, Sebastiaan Couwenberg ha scritto:
>> Hi Antonio,
>>
>> On 07/03/2016 07:30 PM, Antonio Valentino wrote:
>>> a_valentino-guest pushed a change to tag upstream/0.5.4+dfsg.1
>>> in repository pycoast.
>>
>> Can you also push the upstream & pristine-tar branches?
> 
> I used a new dfsg_clean branch and disabled pristine-tar as suggested in
> [1].
> 
> [1]
> http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.special.html#GBP.SPECIAL.DFSGFREE

That's not a procedure I'd recommend for use in the Debian GIS team.

Using the Files-Excluded field in debian/copyright along with setting
the repacksuffix option in debian/watch is the recommended method to
repack upstream tarballs.

I've pushed the changes for this in:

 https://anonscm.debian.org/cgit/pkg-grass/pycoast.git/commit/?id=73e92a4cfad753ad41275f54ee0bdedadc32e249

uscan will refuse to download the upstream tarball again, so you need to
remove it before using uscan to download the upstream tarball. There is
no need to disable pristine-tar, all users of the git repository
need to be able to (re)generate the repacked upstream tarball too.

Updating the packaging with a new repacked upstream tarball is the same
as importing unmodified upstream tarballs. For this specific case it
came down to:

 rm ../pycoast-0.5.4.tar.gz
 uscan --verbose --download-current-version
 gbp import-orig ../pycoast_0.5.4+dfsg.orig.tar.gz
 dch -v 0.5.4+dfsg-1

I've pushed the changes for the above. Please keep it in mind for the
next time you need to repack upstream tarballs.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1