[Debichem-devel] Bug#910686: Pymol 2.2.0 sources available from github

[Stuart Prescott]

> > Having downloaded the upstream source (with uscan) and ensuring that you
> > have no uncommitted changes:
> > 
> > $ gbp import-orig ../pymol_2.2.0.orig.tar.gz
> 
> This is what I did ... except that I always use --pristine-tar (as per
> several other science related team policies).  

Note that debichem-team ≠ debian-science-team and there is no consensus for 
this within debichem.

BTW, I obey the configuration of the repo -- if you really want pristine-tar 
used, then please configure the repository correctly so that gbp would do so 
on its own, debian/gbp.conf:

[DEFAULT] 
pristine-tar = True

The individual developer should not need to remember to do this or what the 
particular preference of one team or another is. 


> Please also do this to
> safe other team members extra work to download the tarball and ensure
> that we all work on the very same tarball.  You can simply do
> 
>     pristine-tar commit ../pymol_2.2.0.orig.tar.gz

Done, but given that the tarball is identical to the upstream one, pristine-
tar isn't actually that useful: "uscan --download --force" is enough. (when 
the tarball is repacked, pristine-tar is also not useful as it cannot 
represent the delta)

Regards
Stuart

-- 
Stuart Prescott    http://www.nanonanonano.net/   stuart at nanonanonano.net
Debian Developer   http://www.debian.org/         stuart at debian.org
GPG fingerprint    90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7