Re: [Pkg-javascript-devel] strange behavior of gbp import-orig --uscan --pristine-tar

2019-10-03 Thread Xavier
More simple : salsa co node-yarnpkg; uscan; ... Le 3 octobre 2019 12:56:50 GMT+02:00, Paolo Greppi a écrit : >On 03/10/19 10:19, Xavier wrote: >> Never use gbp --uscan, totally buggy. Préfet uscan, then gbp >import-orig ../xx.orig.tard.gz > >Thanks for the quick reply. It is indeed a

Re: [Pkg-javascript-devel] strange behavior of gbp import-orig --uscan --pristine-tar

2019-10-03 Thread Paolo Greppi
On 03/10/19 10:19, Xavier wrote: > Never use gbp --uscan, totally buggy. Préfet uscan, then gbp import-orig > ../xx.orig.tard.gz Thanks for the quick reply. It is indeed a git-buildpackage bug: https://bugs.debian.org/934200 For future reference, this worked: cd `mktemp -d` git clone

Re: [Pkg-javascript-devel] strange behavior of gbp import-orig --uscan --pristine-tar

2019-10-03 Thread Xavier
Never use gbp --uscan, totally buggy. Préfet uscan, then gbp import-orig ../xx.orig.tard.gz Le 3 octobre 2019 09:57:17 GMT+02:00, Paolo Greppi a écrit : >I do this: > >cd `mktemp -d` >git clone https://salsa.debian.org/js-team/node-yarnpkg >cd node-yarnpkg >git checkout -b upstream

[Pkg-javascript-devel] strange behavior of gbp import-orig --uscan --pristine-tar

2019-10-03 Thread Paolo Greppi
I do this: cd `mktemp -d` git clone https://salsa.debian.org/js-team/node-yarnpkg cd node-yarnpkg git checkout -b upstream origin/upstream git checkout upstream git pull git checkout master gbp import-orig --uscan --pristine-tar at the end of the process, the master branch is screwed: grep name