Request 730229 (superseded)

This request is superseded by request 730232 (Show diff)

You're not reviewing the full diff of request 730229 , but the diff to the superseded request 713812 (Show full diff)

Overview

Request 730229 superseded

Work around file conflict in devel package, update to 3.24

Created by StefanBruens about 5 years ago
In state superseded
Supersedes 713812
Superseded by 730232
Open review for opensuse-review-team
Open review for openSUSE:Factory:Staging:adi:44

Submit libsvm

Comments for request 730229 0
Comments for request 713812 3

Max Lin (mlin7442) - over 5 years ago

found conflict of libsvm-devel-3.23-5.1.x86_64 with vpp-devel-19.4-2.3.x86_64 /usr/lib64/libsvm.so

Dominique Leuenberger (dimstar) - about 5 years ago

reviewer

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

Stefan Brüns (StefanBruens) - about 5 years ago

source maintainer

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).