On Tue, Apr 22, 2025 at 09:05:39PM +0200, Sébastien Jodogne wrote:
The "orthanc" service fails to start properly, and I suspect (but I am not sure) that this is related to an issue with the "/usr/share/dcmtk/" path,
It would be nice to see an actual error message pointing to that, but if you think this is the reason, you already know the solution from the replies to #1103505: you need to add suitable Depends/Breaks so that CI doesn't try to test package combinations that are not expected to work together.
autopkgtests for orthanc 1.12.7+dfsg-1 fail for me locally.The latest version is orthanc 1.12.7+dfsg-2
Indeed.However, autopkgtests for orthanc 1.12.7+dfsg-2 fail for me locally with the same output as 1.12.7+dfsg-1, though I now see that the output is different from the CI one:
Setting up orthanc (1.12.7+dfsg-2) ... Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. invoke-rc.d: could not determine current runlevel All runlevel operations denied by policy invoke-rc.d: policy-rc.d denied execution of start. invoke-rc.d: could not determine current runlevel All runlevel operations denied by policy invoke-rc.d: policy-rc.d denied execution of start. Processing triggers for libc-bin (2.41-7) ... autopkgtest [00:28:38]: test run-test: [----------------------- User 'orthanc' exists. Orthanc is active. autopkgtest [00:28:38]: test run-test: -----------------------] autopkgtest [00:28:38]: test run-test: - - - - - - - - - - results - - - - - - - - - - run-test FAIL non-zero exit status 7 autopkgtest [00:28:38]: @@@@@@@@@@@@@@@@@@@@ summary run-test FAIL non-zero exit status 7It seems that it simply exits via set -e when your new curl invocation fails.
-- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature