Bug 2293940

Summary:	libstdc++ package conflicts between i686 and x86_64
Product:	[Fedora] Fedora	Reporter:	Tom Caram <tomas.caram>
Component:	gcc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	dmalcolm, fweimer, jakub, jlaw, josmyers, jwakely, mcermak, mhroncok, mpolacek, msebor, nickc, nixuser, rxguy, sipoyare, valdis.kletnieks, vkadlcik
Target Milestone:	---	Keywords:	UpgradeBlocker
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-26 22:18:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2294381
Bug Blocks:

Description Tom Caram 2024-06-24 13:29:39 UTC

libstdc++ package conflicts between i686 and x86_64

Appears to be the same bug as in https://bugzilla.redhat.com/show_bug.cgi?id=1366516

 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64
  - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64
  - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64
  - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64

Reproducible: Always

Steps to Reproduce:
1. sudo dnf upgrade -y
2. download and wait for package install
3. get error
Actual Results:  
 - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64
  - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/printers.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64
  - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.opt-1.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64
  - file /usr/share/gcc-14/python/libstdcxx/v6/__pycache__/xmethods.cpython-313.pyc conflicts between attempted installs of libstdc++-14.1.1-6.fc41.i686 and libstdc++-14.1.1-6.fc41.x86_64

Expected Results:  
upgrade completes correctly without errors

Appears to be the same bug as in https://bugzilla.redhat.com/show_bug.cgi?id=1366516

Comment 1 Václav Kadlčík 2024-06-25 08:09:47 UTC

Indeed. Doesn't happen with gcc-14.1.1-5.fc41 because the shared files have the same contents there. The only change since then is a clean rebase+bump. An upstream issue is a possibility but, and more likely, something funny happened during the build...

Comment 2 Jonathan Wakely 2024-06-25 12:36:41 UTC

Or a python3 bug?

Comment 3 Jonathan Wakely 2024-06-26 11:30:37 UTC

See Bug 2293940 which has been re-assigned to the add-determinism component.

Can this bug be closed as a dup of that one?

Comment 4 Václav Kadlčík 2024-06-26 12:11:00 UTC

> Can this bug be closed as a dup of that one?

I'm not sure. Yes, apparently we need bz2294381 to be fixed first but that wouldn't make the libstdc++ conflict disappear. But then we still need to rebuild gcc to resolve it...

Comment 5 Jonathan Wakely 2024-06-26 12:12:25 UTC

OK, let's use the other one for the underlying bug and this one for the required gcc rebuild.

Comment 6 Miro Hrončok 2024-06-26 22:18:17 UTC

This is a bug in the gcc specfile, so there is no need for 2 separate bugzillas.

I am marking this one as a duplicate. It was opened earlier, but the other one includes my findings and possible fix.

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