Re: New CamiTK 6.0.0 release

Étienne Mollier <[email protected]> Tue, 13 Jan 2026 22:59:37 +0100
Newsgroups	gmane.linux.debian.devel.medical
Message-ID	<[email protected]>
Hi Manik,

Manik Bhattacharjee, on 2026-01-13:
> 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.

You're welcome, I'm glad you could review your procedure to
identify what went off and put things back on tracks.  :)

> 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 ?

As far as I can parse from the piuparts output that has run on
Salsa CI, there were not one but multiple runs: one per binary
package produced by the build.  Several managed to get through,
the failing one tested libcamitk-dev.  Previous packages, that
passed, were: camitk-actionstatemachine, camitk-config and
camitk-imp, in that order.  In every cases, the first thing
piuparts did was to deploy the version currently in unstable and
for libcamitk-dev it failed due to the conflicts between the vtk
dependencies.  Therefore, I'm afraid I stand by my initial
impression: I don't know how to recover from that particular
test scenario, apart from having piuparts run with option
--no-upgrade-test, which will skip the part in which camitk
5.2.0 gets installed during the run.  When my own build of
camitk went through, I could manually trigger piuparts with the
following arguments (roughly) and the test went through:

	$ piuparts -d sid --no-upgrade-test ./camitk_6.0.0-1_amd64.changes

I see a few low hanging fruit items that I would prefer to see
addressed before upload, as reported by lintian informational
and pedantic messages:

	[…]
	I: camitk source: older-debian-watch-file-standard 4 [debian/watch]
	[…]
	P: camitk source: redundant-priority-optional-field [debian/control:7]
	P: camitk source: redundant-rules-requires-root-no-field [debian/control:34]
	P: camitk source: trailing-whitespace [debian/rules:28]
	P: camitk source: trailing-whitespace [debian/rules:83]

but overall I'm fine with the state of the package and plan to
upload tomorrow evening (it's a bit late for me now today).  Let
me know if you carry the changes suggested by lintian; the
timestamp for the 6.0.0-1 in debian/changelog may also benefit
from being refreshed, which in turn will prompt lintian to also
flag that the package would benefit being aligned with standards
version 4.7.3.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier <[email protected]>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-    on air: Cirkus - Sanctus
signature.asc (application/pgp-signature, 833 B)