Overview
Request 713812 superseded
Updates
- Created by dstoecker
- In state superseded
- Supersedes 713745
- Superseded by 730229
- Open review for openSUSE:Factory:Staging:adi:44
Request History
dstoecker created request
Updates
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:44"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:44
maxlin_factory added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:30"
maxlin_factory accepted review
Moved to openSUSE:Factory:Staging:adi:30
licensedigger accepted review
ok
dimstar accepted review
dimstar declined review
found conflict of libsvm-devel-3.23-5.3.x86_64 with vpp-devel-19.4-2.4.x86_64
/usr/lib64/libsvm.so
2 months without reaction ? I declare this unmaintained before it's merged
dimstar declined request
found conflict of libsvm-devel-3.23-5.3.x86_64 with vpp-devel-19.4-2.4.x86_64
/usr/lib64/libsvm.so
2 months without reaction ? I declare this unmaintained before it's merged
dstoecker reopened request
Actually that is a bug in vpp. vpp-devel packages a lot of c sources (and cmake and dox and other source stuff) and header files which have nothing to do with vpp in the /usr/include path. That looks awful to me.
staging-bot approved review
Re-evaluation needed
staging-bot accepted review
Re-evaluation needed
staging-bot added factory-staging as a reviewer
Requesting new staging review
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:44"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:44
found conflict of libsvm-devel-3.23-5.1.x86_64 with vpp-devel-19.4-2.3.x86_64 /usr/lib64/libsvm.so
CC @ndas - can you please check what's up with vpp?
Like where is there libsvm.so - this seems to be provided by this new package
For VPP, svm means <something>VirtualMachine. It is one of the public interfaces of VPP, so the existence of /usr/lib{,64}/libsvm.so in the vpp-devel package is warranted.
libsvm as in SupportVectorMachine is late to the game (at least regarding the openSUSE repos), so it has to deal with it, either: 1. Conflicting vpp-devel 2. Installing its libraries under a prefix, e.g. /usr/lib{,64}/svm/libsvm.so.*
Strictly speaking, even the library packages conflict, as libvpp0 contains libsvm.so.19.04 (yeah, shared library policy violation ahead), and libsvm2 contains libsvm.so.2, both in %{_libdir}. So if possible, I would prefer solution (2.) (install under prefix).