Re: Struggling with multi-tarball source of yorick-optimpack
Hi,
On 09/01/25 12:56 am, Andreas Tille wrote:
dget http://deb.debian.org/debian/pool/main/y/yorick-optimpack/yorick-optimpack_1.3.2+dfsg+1.4.0-1.dsc
you get a multi-tarball source which was not commited to the Git
repository. In principle this is possible with the following gbp.conf:
https://salsa.debian.org/science-team/yorick-optimpack/-/blob/master/debian/gbp.conf?ref_type=heads
and than doing
$ gbp import-orig --pristine-tar --no-interactive PATH/TO/yorick-optimpack_1.3.2+dfsg+1.4.0.orig.tar.gz
gbp:error: Cannot find component tarball /home/andreas/debian-maintain/salsa/science-team/botd/build-area/yorick-optimpack_1.3.2+dfsg+1.4.0.orig-optimpack1.tar.gz
The problem seems to be that `.orig.tar.gz` is GZIP compressed while
`.orig-optimpack1.tar.gz` is XZ compressed. I tried my luck with
specifying the compression in gbp.conf but failed.
Any idea how to import the source properly?
The gbp import-orig manpage[1] states for component import:
| --component=COMPONENT
| When importing the upstream tarball also look for an additional
| tarball with component name COMPONENT.
| ...
| The additional tarball is expected to be in the same directory than
| the upstream tarball and to use the ** same compression type. **
So it is likely not be possible to manage importing this version with gbp.
Even looking at git history makes me think that imports are done
manually and not via gbp. You might have to actually manually commit the
updated changes to upstream branch (i.e. clone the source minus debian/
directory), tag it, merge it to master and do a pristine-tar commit of
the orig tar and the component.
[1]:
https://manpages.debian.org/testing/git-buildpackage/gbp-import-orig.1.en.html
-n
Reply to: