Bug 2000498

Summary:	F36FailsToInstall: wine
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	wine	Assignee:	Michael Cronenworth <mike>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	andreas.bierfert, besser82, ego.cordatus, mike
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	wine-6.16-1.fc34 wine-6.16-1.fc35	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-09-05 17:15:02 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:
Bug Blocks:	1992487

Description Miro Hrončok 2021-09-02 09:31:02 UTC

Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (wine) Fails To Install in Fedora 36:

can't install wine:
  - nothing provides wine-mono = 6.2.0 needed by wine-6.13-1.fc35.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.

P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors.

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!

Comment 1 Fedora Update System 2021-09-05 14:58:04 UTC

FEDORA-2021-5185ef85df has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5185ef85df

Comment 2 Fedora Update System 2021-09-05 14:58:52 UTC

FEDORA-2021-a9d0d4b1a4 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a9d0d4b1a4

Comment 3 Miro Hrončok 2021-09-05 17:15:02 UTC

Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 36.

Thanks for taking care of it!

Comment 4 Fedora Update System 2021-09-05 19:55:37 UTC

FEDORA-2021-5185ef85df has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-5185ef85df`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5185ef85df

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-09-05 21:23:33 UTC

FEDORA-2021-a9d0d4b1a4 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a9d0d4b1a4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a9d0d4b1a4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-09-06 22:46:37 UTC

FEDORA-2021-a9d0d4b1a4 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2021-09-24 20:16:45 UTC

FEDORA-2021-5185ef85df has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.