On Tue, Jun 04, 2024 at 08:11:29AM +0200, Mathieu Malaterre wrote: > I am being asked to rebuild all reverse dependencies of dcmtk to > transition to 3.6.8 (*). I have tried without success to get access to > debomatic-amd64 with no luck so far.
If I infer the information correctly, they are asking you if they
reverse-dependencies are "known" to build properly, which means if there are any
API breakages or not, and if just a rebuild of reverse builddeps is enough to
get
things going, or if there are any more caveats to take care of.
A good way not an exhaustive way to go about this is to check pseudo excuses
for failing autopkgtests of reverse depends against your package
https://release.debian.org/britney/pseudo-excuses-experimental.html
If there are several reverse build depends (and not just reverse depends), and
you have machine constraints to build them all, you could
ask Lucas Nussbaum to help you with this (as he also does archive
wide rebuilds several times).
However, in this case (see below) ...
> Would anyone have any other suggestions to get this transition rolling
> (stuck for 5 months now).
[~]$ reverse-depends libdcmtk-dev -b
Reverse-Build-Depends
=====================
* amide
* ants
* biosig
* cmtk
* dicomscope
* elastix
* insighttoolkit5
* mia
* odil
* odin
* openimageio
* orthanc
* orthanc-wsi
* plastimatch
[~]$ reverse-depends libdcmtk17t64 -b
No reverse dependencies found
[~]$ reverse-depends dcmtk -b
Reverse-Build-Depends
=====================
* odil
* sight
In total it looks like 15 reverse build depends and it should be possible to
build locally (except for maybe itk5). You could use ratt package or
ruby-team/meta: https://salsa.debian.org/ruby-team/meta for the same.
Hope that helps at least a little bit!
> (*)
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060704#10
Best,
Nilesh
signature.asc
Description: PGP signature
