Comment # 7 on bug 1185700 from Fabian Vogt

(In reply to Stefan Br���ns from comment #6)
> (In reply to Fabian Vogt from comment #5)
> > (In reply to Fabian Vogt from comment #3)
> > > It appears to work here, that symbol is provided by
> > > libopencv4_5-4.5.2-1.1.x86_64. What's the version of the libopencv4_5
> > > package on your system? Where is it from?
> > 
> > That was indeed a false positive, it fails with LD_BIND_NOW=1.
> > I asked for a rebuild, that's running now.
> > 
> > It appears like OpenCV broke ABI, because the dnn namespace is versioned and
> > that version got bumped:
> > https://github.com/opencv/opencv/commit/
> > a823b06fa5afd0a1c42f032f00a5169bf8ddef1e#diff-
> > 635059e6e33138c5734e926dfbb7355b08ce112d9ec542313f0377761bf00da6
> > 
> > Was that change intentional? If so, is it possible to use symbol versioning
> > for that so that it's expressed as RPM dependencies?
> 
> Definitely intentional, as DNN API/ABI has changed.
> 
> cv::dnn is the only module which has broken ABI in a minor version. For all
> other modules, the soversion/soname is sufficient. I have filed
> https://github.com/opencv/opencv/issues/20046

Thanks, subscribed.

> > The problem in the original comment was using old opencv (old TW) with new
> > digikam (KDE:Extra), while plain TW has new opencv combined with old digikam.
> 
> Why was digikam in TW not rebuild?

Packages in Tumbleweed are only rebuilt when they are no longer installable.
That's why symbol versioning or an explicit %requires_eq would solve this
particular issue.