Bug 1970512

Summary:	Needs a rebuild for EL 8.4
Product:	[Fedora] Fedora EPEL	Reporter:	alex
Component:	barrier	Assignee:	Ding-Yi Chen <dchen>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	alex, dchen
Target Milestone:	---
Target Release:	---
Hardware:	All
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-15 11:11:34 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 alex 2021-06-10 15:34:19 UTC

Description of problem:

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

How reproducible:

$ dnf update
...
Error: 
 Problem 1: package avahi-devel-0.7-19.el8.x86_64 requires avahi(x86-64) = 0.7-19.el8, but none of the providers can be installed
  - cannot install both avahi-0.7-20.el8.x86_64 and avahi-0.7-19.el8.x86_64
  - cannot install the best update candidate for package avahi-devel-0.7-19.el8.x86_64
  - cannot install the best update candidate for package avahi-0.7-19.el8.x86_64
 Problem 2: package avahi-compat-libdns_sd-0.7-19.el8.x86_64 requires avahi-libs(x86-64) = 0.7-19.el8, but none of the providers can be installed
  - cannot install both avahi-libs-0.7-20.el8.x86_64 and avahi-libs-0.7-19.el8.x86_64
  - cannot install the best update candidate for package avahi-libs-0.7-19.el8.x86_64
  - cannot install the best update candidate for package avahi-compat-libdns_sd-0.7-19.el8.x86_64
 Problem 3: package avahi-compat-libdns_sd-devel-0.7-19.el8.x86_64 requires avahi-devel(x86-64) = 0.7-19.el8, but none of the providers can be installed
  - package avahi-devel-0.7-19.el8.x86_64 requires avahi-libs(x86-64) = 0.7-19.el8, but none of the providers can be installed
  - cannot install both avahi-libs-0.7-20.el8.x86_64 and avahi-libs-0.7-19.el8.x86_64
  - package avahi-glib-0.7-20.el8.x86_64 requires avahi-libs(x86-64) = 0.7-20.el8, but none of the providers can be installed
  - cannot install the best update candidate for package avahi-glib-0.7-19.el8.x86_64
  - cannot install the best update candidate for package avahi-compat-libdns_sd-devel-0.7-19.el8.x86_64
 Problem 4: problem with installed package avahi-devel-0.7-19.el8.x86_64
  - package avahi-devel-0.7-19.el8.x86_64 requires avahi-libs(x86-64) = 0.7-19.el8, but none of the providers can be installed
  - cannot install both avahi-libs-0.7-20.el8.x86_64 and avahi-libs-0.7-19.el8.x86_64
  - package avahi-gobject-0.7-20.el8.x86_64 requires avahi-libs(x86-64) = 0.7-20.el8, but none of the providers can be installed
  - cannot install the best update candidate for package avahi-gobject-0.7-19.el8.x86_64
 Problem 5: package barrier-2.3.3-2.el8.x86_64 requires libdns_sd.so.1()(64bit), but none of the providers can be installed
  - package avahi-compat-libdns_sd-0.7-19.el8.x86_64 requires avahi-libs(x86-64) = 0.7-19.el8, but none of the providers can be installed
  - cannot install both avahi-libs-0.7-20.el8.x86_64 and avahi-libs-0.7-19.el8.x86_64
  - package avahi-ui-gtk3-0.7-20.el8.x86_64 requires avahi-libs(x86-64) = 0.7-20.el8, but none of the providers can be installed
  - cannot install the best update candidate for package barrier-2.3.3-2.el8.x86_64
  - cannot install the best update candidate for package avahi-ui-gtk3-0.7-19.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Actual results:

Can't upgrade completely to EL 8.4 with barrier installed from EPEL

Expected results:

Upgrade is smooth :)

Comment 1 Ding-Yi Chen 2021-10-14 23:56:50 UTC

It seems to stuck with avahi*-devel, would you mind removing those avahi*-devel packages, then try to upgrade?

Comment 2 alex 2021-10-15 11:11:34 UTC

This was solved at some point, I was able to upgrade. Doing a "closed - current release".