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

[Andreas Tille]

On Tue, Oct 23, 2018 at 12:09:21AM +1100, Stuart Prescott wrote:
> > > $ 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.

I understand that the teams are different but if you want help from
members other teams it helps to stick to some standards - specifically
if there is no written team policy (as far as I know Debichem has none).
 
> 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

I admit I'm not aware that this is no default.

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

Fair enough

> >     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)

Graham has just answered this and I can only stress:  Its not the first
time that I've seen different content in identically named tarballs. 

Kind regards

       Andreas.

-- 
http://fam-tille.de