-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-10.0
-
None
-
No
-
Moderate
-
rhel-net-perf
-
ssg_core_services
-
26
-
3
-
False
-
False
-
-
None
-
None
-
Pass
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
rhel9 > rhel10
What is the impact of this issue to you?
file conflict
Please provide the package NVR for which the bug is seen:
bind-doc-32:9.18.33-2.el10.noarch
How reproducible is this bug?:
upgrade test
Steps to reproduce
Stderr: No matches found for the following disable plugin patterns: subscription-manager Warning: Package marked by Leapp to install not found in repositories metadata: paper Warning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey leapp python3-leapp Error:
Transaction test error: file /usr/share/doc/bind/html/_static/css from install of bind-doc-32:9.18.33-2.el10.noarch conflicts with file from package bind-doc-32:9.16.23-24.el9_5.noarch file /usr/share/doc/bind/html/_static/js from install of bind-doc-32:9.18.33-2.el10.noarch conflicts with file from package bind-doc-32:9.16.23-24.el9_5.noarch
Hint: If there was a problem reaching remote content (see stderr output) and proxy is configured in the YUM/DNF configuration file, the proxy configuration is likely causing this error. Make sure the proxy is properly configured in /etc/dnf/dnf.conf. It's also possible the proxy settings in the DNF configuration file are incompatible with the target system. A compatible configuration can be placed in /etc/leapp/files/dnf.conf which, if present, it will be used during some parts of the upgrade instead of original /etc/dnf/dnf.conf. In such case the configuration will also be applied to the target system. Note that /etc/dnf/dnf.conf needs to be still configured correctly for your current system to pass the early phases of the upgrade process.
Expected results
Actual results
- links to
-
RHBA-2024:140564 bind bug fix and enhancement update