Re: seeking RFS for pat v0.12.0-1

[Shengjing Zhu <zhsj@debian.org>]

On Sun, Jan 2, 2022 at 2:47 AM tony mancill <tmancill@debian.org> wrote:
>
> On Sat, Jan 01, 2022 at 01:38:55PM -0500, Federico Grau wrote:
> > On Sun, Jan 02, 2022 at 01:46:22AM +0800, Shengjing Zhu wrote:
> > > git checkout upstream
> > > git merge --ff upstream/0.12.0
> > >
> >
> > Thanks for the feedback Shengjing Zhu,
> >
> > I've completed the suggested steps and pushed them to salsa.
> > Ready for further review, feedback, or upload as cycles are available.
>
> Hi Federico,
>
> Do you mind also pushing your pristine-tar branch to Salsa?  If you
> don't have one, you should be able to run the following command from the
> same directory as your git repo - that is the same directory where you
> can successfully run gbp buildpackage:
>
>   pristine-tar commit ../build-area/pat_0.12.0.orig.tar.gz
>
> or
>
>   pristine-tar commit ../tarballs/pat_0.12.0.orig.tar.gz
>
> (or pat_0.12.0.orig.tar.xz, if that's what you have)
>
> The reason your build is working locally is that the build system can
> find the orig.tar.gz.  On my system, after pulling the latest from
> Salsa, the error is:
>
> $ gbp buildpackage
> gbp:info: Tarballs 'pat_0.12.0.orig.tar.gz' not found at '../tarballs/'
> gbp:warning: Pristine-tar branch "pristine-tar" not found
> gbp:info: Creating /data/debian/sponsor/pat/build-area/pat_0.12.0.orig.tar.gz
> gbp:error: Error creating pat_0.12.0.orig.tar.gz: Pristine-tar couldn't checkout "pat_0.12.0.orig.tar.gz": pristine-tar: no pristine-tar branch found, use "pristine-tar commit" first
>

You can get rid of this error by running `gbp buildpackage
--git-no-pristine-tar`, or adding `pristine-tar=False` to
debian/gbp.conf .

Decision to use pristine-tar or not could be not affected by this error.

-- 
Shengjing Zhu