-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
rhel-sst-cs-base-utils
-
ssg_core_services
-
None
-
False
-
-
None
-
None
-
None
-
None
-
Release Note Not Required
-
-
Unspecified
-
None
Description of problem:
When I run "dnf check-update", the output claims that gimp-libs.i686 obsoletes
gimp-libs.x86_64. I do not have any *.i686 rpms installed on this system.
Version-Release number of selected component (if applicable):
dnf-4.12.0-2.el9.noarch
How reproducible:
always
Steps to Reproduce:
1. dnf check-update
2.
3.
Actual results:
gimp.x86_64 2:2.99.8-3.el9 appstream
gimp-libs.x86_64 2:2.99.8-3.el9 appstream
...
Obsoleting Packages
gimp.x86_64 2:2.99.8-3.el9 appstream
gimp.x86_64 2:2.99.8-2.el9 @System
gimp-libs.i686 2:2.99.8-3.el9 appstream
gimp-libs.x86_64 2:2.99.8-2.el9 @System
gimp-libs.x86_64 2:2.99.8-3.el9 appstream
gimp-libs.x86_64 2:2.99.8-2.el9 @System
Expected results:
I do not expect to see gimp-libs.i686 obsoleting gimp-libs.x86_64 in the results.
Additional info:
Running "dnf update" does not attempt to install gimp-libs.i686. I don't know
whether this is a dnf issue, or a packaging problem with the gimp spec file.
The gimp spec file says:
#Demodularizing of gimp (#1772469)
Obsoletes: %
Conflicts: %{name}
-libs < %
{epoch}:%
{version}-%
{release}Should the Obsoletes specify the ISA to avoid this issue? Or is "dnf check-update" being stupid?
- external trackers