Re: Solved (Was: Pristine-tar is broken when doing backports)

[Andrey Rahmatullin]

On Fri, May 03, 2019 at 07:18:41AM +0200, Andreas Tille wrote:
> Argh, for some reason the ~/.gbp.conf I'm using for Stretch contained
> 
># pristine-tar = True
> 
> (I probably once backported a package without pristine-tar.)
Consider putting pristine-tar = True into debian/gbp.conf.

> Its probably a bug to create **wrong** tarballs if pristine-tar is
> unset 
How is that a bug?

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Solved (Was: Pristine-tar is broken when doing backports)

[Andreas Tille]

Argh, for some reason the ~/.gbp.conf I'm using for Stretch contained

   # pristine-tar = True

(I probably once backported a package without pristine-tar.)
Its probably a bug to create **wrong** tarballs if pristine-tar is
unset but after removing the comment my setup is working again.

Kind regards

Andreas.

On Thu, May 02, 2019 at 10:44:14AM +0500, Andrey Rahmatullin wrote:
> On Thu, May 02, 2019 at 07:40:56AM +0200, Andreas Tille wrote:
> > Hi folks,
> > 
> > I'm using gbp successfully in all my packaging projects and it works
> > perfectly when building in sid.  However since some time (about 1-2
> > months) always if I try to do a backport to stretch git-buildpackage is
> > creating a wrong upstream source tarball (wrong size and md5sum).  This
> > *only* happens for backports so I assume the Git archive is OK, but the
> > backport build process does something differently.
> > 
> > Any idea what might be wrong?
> Anything.
> Please provide more info.
> 
> -- 
> WBR, wRAR



-- 
http://fam-tille.de