Bug 1219750

Summary:	libvpl2-2023 not found
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Chase Steenbock <chase>
Component:	X11 Applications	Assignee:	E-mail List <screening-team-bugs>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	Andreas.Stieger, chase, hp.jansen, hpj, sndirsch
Version:	Current
Target Milestone:	---
Hardware:	PC
OS:	openSUSE Tumbleweed
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Chase Steenbock 2024-02-09 05:50:53 UTC

Hello, I am trying to install updates to my system (2600+ at the time of this writing), but the installs continue to fail due to a missing libvpl2 2023 dependency. I've tried updating via Discover, Yast 2, and zypper dup with the same results.

Here is the message from Discover:

File './x86_64/libvpl2-2023.4.0-1.1.x86_64.rpm' not found on medium 'https://download.opensuse.org/tumbleweed/repo/oss/'

I can't find this file anywhere online and I also am unable to build it from source (not my area of expertise), so I'm not sure how to get it in the repo so my updates can work. By the way, my updates fail regardless of the number of updates I have selected.

Comment 1 Andreas Stieger 2024-02-09 10:45:31 UTC

Breaking change: https://build.opensuse.org/request/show/1140080

> -Version:        2023.4.0
> +Version:        2.10.1

$ zypper vcmp 2023.4.0 2.10.1
2023.4.0 is newer than 2.10.1

Workaround: zypper dup --allow-downgrade

Comment 2 Stefan Dirsch 2024-02-09 10:57:19 UTC

(In reply to Chase Steenbock from comment #0)
> Here is the message from Discover:
> 
> File './x86_64/libvpl2-2023.4.0-1.1.x86_64.rpm' not found on medium
> 'https://download.opensuse.org/tumbleweed/repo/oss/'

I think a 'zypper ref' helps here

Comment 3 Stefan Dirsch 2024-02-09 10:59:01 UTC

(In reply to Andreas Stieger from comment #1)
> Breaking change: https://build.opensuse.org/request/show/1140080
> 
> > -Version:        2023.4.0
> > +Version:        2.10.1
> 
> $ zypper vcmp 2023.4.0 2.10.1
> 2023.4.0 is newer than 2.10.1
> 
> Workaround: zypper dup --allow-downgrade

And how should I handle this better. Use

2023.4.0.2.10.1 or rename the package to libvpl21, which also would be wrong?

Comment 4 Stefan Dirsch 2024-02-09 10:59:53 UTC

(In reply to Stefan Dirsch from comment #3)
[...] or rename the package to libvpl21, which also would be wrong?
And add the appropriate Provides/Obsoletes of course.

Comment 5 Stefan Dirsch 2024-02-09 11:53:49 UTC

If anybody has a proposal which improves the situation, please speak up! But for now I set this to WONTFIX.

Comment 6 Hans-Peter Jansen 2024-02-09 12:04:44 UTC

FTR: https://github.com/intel/libvpl/releases

The upstream version went "backwards". Urgh! Let's call this upstream madness!

As Stefan noted already, if somebody knows a better way how to handle this, let us know!

What happens, if we add a Provides/Obsoletes with a fixed version of 2023.4.0?

Comment 7 Stefan Dirsch 2024-02-09 12:11:30 UTC

(In reply to Hans-Peter Jansen from comment #6)
> What happens, if we add a Provides/Obsoletes with a fixed version of
> 2023.4.0?

Don't know ...

Comment 8 Andreas Stieger 2024-02-09 12:24:31 UTC

We don't use/support RPM's epoch. zypper can do downgrades fine, I think the root cause for the bug report was "zypper ref", the version downgrade is a coincidence.

Comment 9 Chase Steenbock 2024-02-09 13:57:22 UTC

So should I run `zypper dup --allow-downgrade` to get around this and submit an issue in the libvpl repo?

Comment 10 Chase Steenbock 2024-02-09 14:26:20 UTC

(In reply to Chase Steenbock from comment #9)
> So should I run `zypper dup --allow-downgrade` to get around this and submit
> an issue in the libvpl repo?

Looks like zypper ref followed by zypper dup --allow-downgrade did the trick. Thank you all for your time and I apologize if I submitted a bug report erroneously.