Your message dated Sat, 28 May 2022 12:12:12 +0200
with message-id <[email protected]>
and subject line Re: Bug#917789: Wrong tarball id (pristine-tar) when
import-orig with --components
has caused the Debian Bug report #917789,
regarding pristine-tar: fails to checkout when there are multiple source
tarballs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
917789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917789
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pristine-tar,git-buildpackage,devscripts
Control: found -1 pristine-tar/1.49
Control: found -1 devscripts/2.20.5
Control: found -1 git-buildpackage/0.9.20
severity: serious
I'm filing against all 3 possible packages which might have a bug here.
Example package node-mermaid. It fails on all packages that uses
multiple source tarballs. (gitlab is another example and many node
packages use multiple source tarballs).
These are usually created with gbp import-orig --pristine-tar
We have to always fall back to 'apt source' command whcih makes
pristine-tar useless in these situations.
I think origtargz should try apt source when pristine-tar fails.
I'm not sure if it fails only with tar.xz though.
$ origtargz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-webpack-node-externals.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-stylis.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-strip-css-comments.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-slugify.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-scope-css.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-sanitize-url.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-khroma.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-is-regexp.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-escaper.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-entity-decode.tar.xz
pristine-tar: successfully generated
./node-mermaid_8.7.0+ds+~cs27.17.17.orig-crypto-random-string.tar.xz
fatal: ambiguous argument
'cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}': unknown revision or
path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: not a valid object name:
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4\^\{tree\} | (cd
'/tmp/pristine-tar.x11yV6IWxf' && tar x)
$ pristine-tar list |grep 8.7.0+ds+~cs27.17.17.orig.tar.xz
node-mermaid_8.7.0+ds+~cs27.17.17.orig.tar.xz
$ pristine-tar checkout ../node-mermaid_8.7.0+ds+~cs27.17.17.orig.tar.xz
fatal: ambiguous argument
'cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}': unknown revision or
path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
fatal: not a valid object name:
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4^{tree}
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
pristine-tar: command failed: git archive --format=tar
cb3a82caf3951fbab382b5a0d7dbdd7936bee2c4\^\{tree\} | (cd
'/tmp/pristine-tar.JY3lejdcNL' && tar x)
--- End Message ---
--- Begin Message ---
Version: git-buildpackage/0.9.26
Hi,
On Sat, May 28, 2022 at 11:13:20AM +0200, Mattia Rizzolo wrote:
> On Sat, May 28, 2022 at 11:10:26AM +0200, Guido Günther wrote:
> > > You need a tree that has the component's tarball dirs dropped:
> > >
> > > https://github.com/agx/git-buildpackage/blob/master/gbp/scripts/export_orig.py#L77
> > >
> > > gbp-buildpackage uses the same code when generating tarballs.
> >
> > Is there still an issue with opencv and it's additional tarball that I
> > could reproduce?
>
> I don't think so. I understand now that in those cases I need to use
> `gbp export-orig` instead of just running `pristine-tar checkout`.
Closing then. I'll use the version I retested things with for version tracking.
Thanks!
-- Guido
>
> However, now I'm mostly confused why you're requiring such special tree
> when in my tests a plain `pristine-tar` using the main tree seemed to
> just work, mhh.
> (or at least, that's what my memory of this old matter claims)
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
> More about me: https://mapreri.org : :' :
> Launchpad user: https://launchpad.net/~mapreri `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
--- End Message ---
