Re: New CamiTK 6.0.0 release

Hi Etienne,

thanks for your remarks and efforts.

Emmanuel and I checked our process to update the salsa repository, which 
seems to be wrong on some steps, and was already wrong for the previous 
versions.

We updated the upstream and pristine-tar branches with what should be 
the correct content, and our new procedure should ensure that the next 
versions will not have those problems.

Unfortunately, the piuparts pipeline step still fails, and I don't 
understand why it still tries to install the old version (5.2.0) of 
libcamitk-dev instead of the new 6.0.0.

https://salsa.debian.org/med-team/camitk/-/jobs/8882675#L6976

There might be a different mistake in our packaging process, or a 
missing parameter in debian/control ?

Thank you for your help !


Manik.


Le 11/01/2026 à 21:19, Étienne Mollier a écrit :
> Hi Manik,
>
> Manik Bhattacharjee, on 2026-01-11:
>> I wonder if this might due a change I did during the process: I imported a
>> tar.xz file in the pristine-tar (which is now the default format provided by
>> gitlab), but the previous version was a tar.gz
>>
>> Could this explain the issue ?
> Hmm, let me think this out loud.  I do some cleanup in my
> working directory.  When I delete all original tarballs, be them
> upstream or the renamed artifact, my actual error is:
>
> 	$ gbp export-orig
> 	gbp:info: Creating /home/emollier/area/debian/med-team/camitk_6.0.0.orig.tar.xz
> 	gbp:error: Cannot find pristine tar commit for archive 'camitk_6.0.0.orig.tar.xz'
>
> The pristine-tar branch indeed stores information for the
> original tarball camitk-6.0.0.tar.xz, but not the orig.tar.xz
> file.  Since upstream and pristine-tar branches prove difficult,
> I pull the release upstream:
>
> 	$ uscan  --force-download
> 	warning: refs/tags/6.0.0 c862cbd903d999b3b52ef11079f7f0a1aefc3298 is not a commit!
> 	uscan warn: Possible OpenPGP signature found at:
> 	   https://gricad-gitlab.univ-grenoble-alpes.fr/CamiTK/CamiTK.git refs/tags/6.0.0.asc
> 	 * Add opts=pgpsigurlmangle=s/$/.asc/ or opts=pgpmode=auto to debian/watch
> 	 * Add debian/upstream/signing-key.asc.
> 	 See uscan(1) for more details
> 	Successfully symlinked ../camitk-6.0.0.tar.xz to ../camitk_6.0.0.orig.tar.xz.
>
> Only then I can begin to build the package, modulo having to
> ensure that I don't try to fetch information from the
> pristine-tar branch:
>
> 	$ gbp buildpackage --git-no-pristine-tar
> 	gbp:info: Performing the build
> 	[…]
>
> otherwise I run into the original error message I reported:
>
> 	$ gbp buildpackage
> 	gbp:error: Pristine-tar couldn't verify "camitk_6.0.0.orig.tar.xz": fatal: path 'camitk_6.0.0.orig.tar.xz.delta' does not exist in 'refs/heads/pristine-tar'
> 	pristine-tar: git show refs/heads/pristine-tar:camitk_6.0.0.orig.tar.xz.delta failed
>
> I try injecting the camitk_6.0.0.orig.tar.xz in the pristine-tar
> branch with gbp:
>
> 	$ gbp pristine-tar commit ../camitk_6.0.0.orig.tar.xz
> 	gbp:info: Successfully committed pristine-tar data for version 6.0.0-1 of ../camitk_6.0.0.orig.tar.xz
>
> 	$ gbp buildpackage
> 	gbp:info: Performing the build
> 	[…]
>
> This seems to do the trick.  :)
>
> The upstream branch looks partially rebased into master, which
> made things extra confusing, but I think it will be possible to
> get the situation back on tracks by injecting the next upstream
> release fully automatically thanks to --uscan option using:
>
> 	$ gbp import-orig --uscan
>
> Sorry for the slight digression from the original piuparts
> issue, but it seemed important to make sense of the state of the
> camitk repository and how to recover; hopefully aligning the git
> repository layout to typical git-buildpackage branches will help
> a bit.  I have not pushed anything to Salsa yet, maybe you want
> to stress these commands on your side and see how things behave.
>
> In hope this helps,