Re: New CamiTK 6.0.0 release

Étienne Mollier <[email protected]> Sun, 11 Jan 2026 18:58:05 +0100
Newsgroups	gmane.linux.debian.devel.medical
Message-ID	<[email protected]>
Hi Emmanuel,

Emmanuel Promayon, on 2026-01-10:
> On 08/01/2026 22:05, Étienne Mollier wrote:
> > Great!  Thank you for caring for camitk!  :)
> > 
> > I'm sorry there is an ongoing maintenance on salsa and could not
> > fetch your work right now, so I cannot comment about your
> > piuparts issue, but I thought I would comment on the blhc:
> We checked yesterday with Manik and tried some tweaking in the libcamitk-dev
> package (which seems to still pull the older 5.2 version), but without
> success.

Right, the piuparts run looks to test against version 5.2.
Initially, I thought that was to install a starting point with
an older version, but I ran into a couple of difficulties when
trying to build the package.  Apparently, some artifacts are
missing from the pristine-tar branch:

	$ gbp export-orig 
	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

Something off also occurred to the upstream branch, as it's head
is outdated from before camitk 5.2 in trixie:

	$ git log upstream | head
	commit 0c9ad36ae84636b3e74d690f147de30ebae8d34a
	Author: Andreas Tille <[email protected]>
	Date:   Mon Jan 17 09:33:52 2022 +0100
	
	    New upstream version 5.0.2
	
	commit ddac4758554c4f89e61d280594a49ec5594a5b52
	Author: Emmanuel Promayon <[email protected]>
	Date:   Mon Jul 16 20:21:30 2018 +0000

The upstream tag made it to the master branch, which may explain
how Salsa CI eventually managed to have most items pass anyways.
I'm afraid the git repository of camitk in salsa does not look
in good shape right now.  :(

Anyway, if the issue persists after putting back the git
repository in good shape, then I believe the particular test
that causes Salsa CI to crash should not be a blocker.  In my
opinion, the important test is that the upgrade from trixie
(which is supposed to be installable in trixie as far as I can
check) to the new build artifacts should work no problems.  If
there are still blockers for migration to testing after an
upload, there is also the option to liaise with the Release Team
to determine precisely blockers, mitigations, or eventually help
migrate the package due to intricate deadlock condition.

In hope this helps,
-- 
  .''`.  Étienne Mollier <[email protected]>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-    on air: Les Claypool's Frog Brigade - Sheep
signature.asc (application/pgp-signature, 833 B)