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

Xavier yadd at debian.org
Thu Oct 3 09:19:04 BST 2019


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 <paolo.greppi at libpf.com> 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 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 package.json 
>  "name": "v8-compile-cache",
>
>the key part of the gbp import-orig is:
>gbp:info: Launching uscan...
>gbp:info: Using uscan downloaded tarball
>../node-yarnpkg_1.19.0.orig-v8-compile-cache.tar.gz
>What is the upstream version? [1.19.0] tar: 
>gbp:info: ../node-yarnpkg_1.19.0.orig.tar.gz already exists, moving to
>../node-yarnpkg_1.19.0.orig.tar.gz.1570089312
>gbp:info: Importing
>'../node-yarnpkg_1.19.0.orig-v8-compile-cache.tar.gz' to branch
>'upstream'...
>gbp:info: Source package is node-yarnpkg
>gbp:info: Upstream version is 1.19.0
>gbp:info: Replacing upstream source on 'master'
>gbp:info: Successfully imported version 1.19.0 of
>../node-yarnpkg_1.19.0.orig-v8-compile-cache.tar.gz
>
>Before I file a bug, has anyone an idea of what is going on ?
>
>Paolo
>
>-- 
>Pkg-javascript-devel mailing list
>Pkg-javascript-devel at alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20191003/b7268645/attachment.html>


More information about the Pkg-javascript-devel mailing list