Bug 2009432

Summary:	python nest asyncio failed transaction test on dnf offline upgrade
Product:	[Fedora] Fedora	Reporter:	David Marceau <d.marceau>
Component:	python-nest-asyncio	Assignee:	Lumír Balhar <lbalhar>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	lbalhar
Target Milestone:	---
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:	2021-10-01 09:08:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Marceau 2021-09-30 16:00:46 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  dnf offline-upgrade download --allowerasing -y

Actual results:
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction test error:
  file /usr/lib/python3.10/site-packages/__pycache__/nest_asyncio.cpython-310.opt-1.pyc from install of python3-nest-asyncio-1.5.1-1.fc36.noarch conflicts with file from package python3-nest_asyncio-1.4.3-5.fc35.noarch
  file /usr/lib/python3.10/site-packages/__pycache__/nest_asyncio.cpython-310.pyc from install of python3-nest-asyncio-1.5.1-1.fc36.noarch conflicts with file from package python3-nest_asyncio-1.4.3-5.fc35.noarch
  file /usr/lib/python3.10/site-packages/nest_asyncio.py from install of python3-nest-asyncio-1.5.1-1.fc36.noarch conflicts with file from package python3-nest_asyncio-1.4.3-5.fc35.noarch

Expected results:
transaction tests passed.

Additional info:

Comment 1 Lumír Balhar 2021-10-01 09:08:26 UTC


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