Package: orthanc-dicomweb
Version: 1.7+dfsg-5
The build-dependencies of orthanc-dicomweb are not satisfiable on armel
package: orthanc-dicomweb
version: 1.7+dfsg-5
architecture: any
type: src
status: broken
reasons:
-
missing:
pkg:
package: node-ms
version: 2.1.3+~cs0.7.31-2
architecture: all
unsat-dependency: nodejs:armel
depchains:
-
depchain:
-
package: orthanc-dicomweb
version: 1.7+dfsg-5
architecture: any
type: src
depends: node-axios:armel
-
package: node-axios
version: 0.26.1+dfsg-2
architecture: all
depends: node-follow-redirects:armel (>= 1.13.0)
-
package: node-follow-redirects
version: 1.15.1+~1.14.1-2
architecture: all
depends: node-debug:armel
-
package: node-debug
version: 4.3.4+~cs4.1.7-1
architecture: all
depends: node-ms:armel
This in itself is nothing new, it was not previously rc however as there
were no binary packages on armel.
However, a few days ago, the node-undici source package which builds the
node-llhttp binary package was accepted into unstable, there was a
screw-up in the packaging leading to the node-llhttp package briefly
providing node-debug. As a result of this the build-dependencies of
orthanc-dicomweb breifly became satisfiable on armel. The Debian
autobuilders spotted this and succesfully built orthanc-dicomweb. Then a
few days later the mistake in node-undici was fixed with the result that
the build-dependencies of orthanc-dicomweb are once-again unsatisfiable
on armel.
So now we have a binary package in testing and unstable that can't be
rebuilt or updated, that is rc.
I see two possible routes forward.
1. Make dependency adjustments, either in orthanc-dicomweb or in
packages it depends on so that it can be built on armel, I do not know
how practical this is to do without causing other problems.
2. Declare orthanc-dicomweb unsupported on armel and file a removal
request with the ftpmasters.
