Bug 1223170

Summary: Discover: Wine Package Conflicts
Product: [openSUSE] openSUSE Tumbleweed Reporter: Stocks <colejstocks>
Component: KDE ApplicationsAssignee: E-Mail List <opensuse-kde-bugs>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None CC: Andreas.Stieger
Version: Current   
Target Milestone: ---   
Hardware: 64bit   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screen presented with Wine packages after initial updates installed. Note the packages attempting to downgrade in version.

Description Stocks 2024-04-21 08:23:18 UTC
Created attachment 874396 [details]
Screen presented with Wine packages after initial updates installed. Note the packages attempting to downgrade in version.

Discover works for the most part as intended. However:

- I tell Discover to check for new app updates.
- Discover checks against repositories and fetches new packages. Installs packages.
- After installation of packages, it will then state there are Wine packages to install. Note: Packages look to be "updating" from latest versions to older versions. The Wine repository added to the system is https://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Tumbleweed/
- Discover fails with either of the following messages:

"Dependency resolution failed:
problem with the installed wine-9.6-1704.2.x86_64
problem with the installed wine-32bit-9.6-1704.2.x86_64
problem with the installed wine-gecko-2.47.4-68.8.noarch
problem with the installed wine-mono-9.0.0-68.2.noarch
problem with the installed winetricks-20240105-45.5.x86_64"

"No distro upgrade data:
No Distribution Upgrade Available."

- The option to then install the Wine conflicting packages show up again and only go away after Discover is closed. This will happen when re-opening Discover and having it run through update installation with the same outcome.
Comment 1 Andreas Stieger 2024-04-21 11:12:48 UTC
duplicate report

*** This bug has been marked as a duplicate of bug 1223171 ***