[packman] OpenShot and libopenshot mismatch

[Wolfgang Bauer]

Am Mittwoch, 30. Oktober 2019, 09:38:42 schrieb packman at howorth.org.uk:
> On Tue, 29 Oct 2019 14:47:52 +0100
> 
> Wolfgang Bauer <e9325712 at student.tuwien.ac.at> wrote:
> >Am Montag, 28. Oktober 2019, 23:04:54 schrieb Mark Post:
> >> I am currently running openSUSE Leap on my laptop. I have openshot-qt
> >> version 2.4.4-18.1 installed from the Packman repository.
> >
> >Are you sure?
> >I don't see any openshot-qt or libopenshot in Packman at all...
> 
> I have libopenshot15 which claims to be 0.2.0-16.1-x86_64 from packman
> (Leap 15.0) I also have libopenshot13 from packman (version marked in
> red) and everything else, including libopenshot14 from opensuse. No idea
> how they all got there :) Or whether they're 'correct'.

Well, post the zypper output that I asked, that would show which versions 
exactly you have installed (and from where), and what is actually available.

That the version is marked in red means that it's not available in the 
configured repos (anymore).

It probably is a left-over from previous Leap versions if you upgraded, but 
you should be able to safely uninstall libopenshot13 as nothing should use it 
anymore. (the openshot-qt package in Leap 15.0 uses libopenshot14)

And/or maybe openshot-qt and libopenshot were indeed available in Packman for 
15.0 as well, but have been removed meanwhile (as it is included in the 
standard repos anyway).



As I found out meanwhile, the OP likely uses Leap 42.3 though, where openshot-
qt and libopenshot were not included in the distribution yet and only 
available from Packman.
Probably the openshot-qt 2.4.4 version (that needs a newer libopenshot) 
slipped in by mistake.

But: Leap 42.3 was end-of-life 4 months ago and is no longer supported:
https://en.opensuse.org/Lifetime

So the advice would be to upgrade to a supported version. (preferably 15.1, as 
15.0 will be EOL in a few weeks as well)

Otherwise, the only option would be to stick to the older openshot-qt 2.4.2, 
which is still in the repo as well. Maybe lock the package to not update it 
accidentally.

Kind Regards,
Wolfgang