Bug 2231379

Summary:	EVR upgrade path issue from F38 -> F39/F40
Product:	[Fedora] Fedora	Reporter:	Mamoru TASAKA <mtasaka>
Component:	fwupd	Assignee:	Richard Hughes <rhughes>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	39	CC:	rhughes
Target Milestone:	---	Keywords:	Upgrades
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mamoru TASAKA 2023-08-11 13:06:04 UTC

Currently F38 fwupd is fwupd-1.9.3-2.fc38 , while F39 one is fwupd-1.9.3-1.fc39 , so F39 has lower EVR than F38 (F40 has the same issue).
This is now causing libcbor upgrade breakage when upgrading from F38 to F39:

# env LANG=en_US.utf8 dnf upgrade libcbor
Last metadata expiration check: 0:23:09 ago on Fri 11 Aug 2023 09:33:29 PM JST.
Dependencies resolved.

 Problem: cannot install both libcbor-0.10.2-2.fc39.x86_64 from fedora and libcbor-0.7.0-9.fc38.x86_64 from @System
  - package fwupd-1.9.3-2.fc38.x86_64 from @System requires libcbor.so.0.7()(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package libcbor-0.7.0-9.fc38.x86_64
  - problem with installed package fwupd-1.9.3-2.fc38.x86_64


I tried rebuilding fwupd on F39/F40 using provenpackager power, however tagging the package failed, releng people says that 'secure-boot' permission is needed for fwupd:

https://pagure.io/releng/issue/11612

Would you rebuild fwupd with bumping release on F39/F40?

Reproducible: Always