Bug 1219797

Summary: Files from openssl-3 at /etc/ssl conflict with those from openssl-1 when using new rpm install backend
Product: [openSUSE] openSUSE Tumbleweed Reporter: Sergio Laverde <sergiolaverde0>
Component: Upgrade ProblemsAssignee: E-mail List <screening-team-bugs>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Log from zypper

Description Sergio Laverde 2024-02-11 00:30:42 UTC
When setting ZYPP_SINGLE_RPMTRANS=1 as an option on zypper, upgrading Opensuse Tumbleweed is aborted with the following error message:

Problem occurred during or after installation or removal of packages:
Executing the transaction failed because of the following problems:
    file /etc/ssl/engdef.d from install of openssl-3-3.1.4-4.1.x86_64 conflicts with file from package openssl-1_1-1.1.1w-5.1.x86_64
    file /etc/ssl/engines.d from install of openssl-3-3.1.4-4.1.x86_64 conflicts with file from package openssl-1_1-1.1.1w-5.1.x86_64

I assume this is related to this issue reported in the forums https://forums.opensuse.org/t/dont-update-tumbleweed/172248/19 however the error message differs because I have the new rmp backend enabled and the solution proposed there doesn't work since I am not given the option the ignore the error with the package since, in my case, the whole upgrade is aborted by this issue.

I'm aware I can just disable the option and attempt the proven solution, but I decided to fill a report both due to the importance of the package involved and the non-zero chance that I bork my system if something goes wrong on my end. I have attached my zypper.log to this report, please let me know should I provide something more.
Comment 1 Sergio Laverde 2024-02-11 00:34:46 UTC
Created attachment 872640 [details]
Log from zypper
Comment 2 hui 2024-02-11 08:25:01 UTC
.

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