|Summary:||rpm: useless error message when /usr/sbin is a symlink to /usr/bin|
|Product:||[Fedora] Fedora||Reporter:||Zbigniew Jędrzejewski-Szmek <zbyszek>|
|Component:||procps-ng||Assignee:||Jan Rybar <jrybar>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2019-05-28 20:11:29 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Zbigniew Jędrzejewski-Szmek 2018-05-11 14:42:43 UTC
Description of problem: # ls -l /usr/sbin lrwxrwxrwx. 1 root root 3 Feb 20 18:28 /usr/sbin -> bin # rpm -Uvh /var/cache/dnf/rawhide-2d95c80a1fa0a67d/packages/procps-ng-3.3.14-1.fc29.x86_64.rpm Preparing... ################################# [100%] file /usr/sbin/pidof conflicts between attempted installs of procps-ng-3.3.14-1.fc29.x86_64 and procps-ng-3.3.14-1.fc29.x86_64 Version-Release number of selected component (if applicable): rpm-4.14.1-8.fc28.x86_64 How reproducible: 100% I know that symlinking /usr/sbin to /usr/bin is not supported in Fedora right now, but we'll probably want to do this in the future. Arch and some other distros do this already. But even if it's not supported, the message is very confusing. It would be much nicer if rpm could say something like "/usr/sbin/pidof and /usr/bin/pidof point to the same file".
Comment 1 Zbigniew Jędrzejewski-Szmek 2018-05-11 14:43:21 UTC
Doing 'rpm -Uvh --force' results in: # ls -l /usr/bin/pidof lrwxrwxrwx. 1 root root 14 Apr 16 14:30 /usr/bin/pidof -> /usr/bin/pidof
Comment 2 Ben Cotton 2019-05-02 21:48:20 UTC
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 3 Ben Cotton 2019-05-28 20:11:29 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.