On Thu, Nov 28, 2024 at 05:37:41PM +0530, Pirate Praveen wrote:
> This can now be reproduced with node-cacache
>
> pravi@mahishi2:/tmp$ gbp clone --pristine-tar
> g...@salsa.debian.org:js-team/node-cacache.git
> gbp:info: Cloning from 'g...@salsa.debian.org:js-team/node-cacache.git'
> pravi@mahishi2:/tmp$ cd node-cacache/
> pravi@mahishi2:/tmp/node-cacache$ less debian/gbp.conf
> pravi@mahishi2:/tmp/node-cacache$ origtargz
> pristine-tar: successfully generated
> ../node-cacache_17.0.3+~cs10.3.7.orig-npmcli-move-file.tar.gz
> pristine-tar: successfully generated
> ../node-cacache_17.0.3+~cs10.3.7.orig-npmcli-fs.tar.gz
> pristine-tar: successfully generated
> ../node-cacache_17.0.3+~cs10.3.7.orig-infer-owner.tar.gz
> pristine-tar: successfully generated
> ../node-cacache_17.0.3+~cs10.3.7.orig-gar-promisify.tar.gz
> pristine-tar: successfully generated
> ../node-cacache_17.0.3+~cs10.3.7.orig-fs-minipass.tar.gz
> fatal: ambiguous argument '60b4383b8c982ac64553f2754abaefe7ca7ebf79^{tree}':
> unknown revision or path not in the working tree.node-cacache_17.0.3+~cs10.3.7.orig.tar.gz.id contains that hash and there is indeed no object with that has in that repo. So I guess the main question is how was this repo generated. > Same works with > > pravi@mahishi2:/tmp/node-cacache$ gbp export-orig --pristine-tar Not sure what does this imply. -- WBR, wRAR
signature.asc
Description: PGP signature
