[Debian-med-packaging] Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory

[Andreas Tille]

Hi Johannes,

Am Wed, May 04, 2022 at 12:22:50PM +0200 schrieb Johannes Schauer Marin Rodrigues:
> Quoting Andreas Tille (2022-05-04 11:25:20)
> > Aaargh, sorry for my sloppyness.  I did not expect a SONAME bump connected
> > with micro-Version bump.  An updated package is in new.
> 
> thanks a lot for this very quick fix!

You are welcome and for sure I'm keen on fixing what I messed up before.
 
> I think the problem is that package-name-doesnt-match-sonames is overridden and
> thus you didn't have Lintian tell you that there was a problem. That would've
> probably have happened to me as well.

Well, if I'm creating library packages I'm using d-shlibs which even
breaks at build time in these cases.  I would have even converted this
package right now, but this does not work since no static library is
build.  I admit I simply underestimated the number of dependencies
which I should habe checked.

> Will you take care of making sure that reverse dependencies are binNMU-ed?

I admit I would use the chance to to real team uploads and check the
other dependencies manually.  Your finding with ant makes me suspicious
about some of the other dependencies.  However, what do you think about
asking ftpmaster for rejecting what is currently in new, re-upload 3.6.6
to unstable and do a proper migration via experimental.  Currently the
package is sitting in new and we have this chance.  Or do you think it
is OK to force this "non-transition" somehow and leave things as they
are now?  What does this mean from your blender perspective?

Kind regards

      Andreas.

-- 
http://fam-tille.de