Bug 2042447 - removing binutils warns /usr/bin/ld No such file or directory
Summary: removing binutils warns /usr/bin/ld No such file or directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: binutils
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nick Clifton
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-19 14:31 UTC by Jiri Jaburek
Modified: 2023-07-18 14:25 UTC (History)
4 users (show)

Fixed In Version: binutils-2.35.2-16.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:58:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-108725 0 None None None 2022-01-19 14:42:54 UTC
Red Hat Product Errata RHBA-2022:3985 0 None None None 2022-05-17 15:59:00 UTC

Description Jiri Jaburek 2022-01-19 14:31:49 UTC
Description of problem:

# dnf install binutils
...
Installing:
 binutils
Installing dependencies:
 binutils-gold
 elfutils-debuginfod-client


# dnf remove binutils
...
Removing:
 binutils
Removing unused dependencies:
 binutils-gold
 elfutils-debuginfod-client
...
Running transaction
  Preparing        :                                                                                              1/1 
  Running scriptlet: binutils-2.35.2-14.el9.x86_64                                                                1/3 
  Erasing          : binutils-2.35.2-14.el9.x86_64                                                                1/3 
warning: file /usr/bin/ld: remove failed: No such file or directory

  Running scriptlet: binutils-2.35.2-14.el9.x86_64                                                                1/3 
  Erasing          : binutils-gold-2.35.2-14.el9.x86_64                                                           2/3 
  Erasing          : elfutils-debuginfod-client-0.186-1.el9.x86_64                                                3/3 
  Running scriptlet: elfutils-debuginfod-client-0.186-1.el9.x86_64                                                3/3 
  Verifying        : binutils-2.35.2-14.el9.x86_64                                                                1/3 
  Verifying        : binutils-gold-2.35.2-14.el9.x86_64                                                           2/3 
  Verifying        : elfutils-debuginfod-client-0.186-1.el9.x86_64                                                3/3 
Installed products updated.


I can't quite figure out where the

  warning: file /usr/bin/ld: remove failed: No such file or directory

comes from - there is one "rm -f", but that is in the postinst scriptlet, the uninstall scripts don't have it.

Maybe rpm(8) attempts to find a packaged file,

  $ rpm -ql -p binutils-2.35.2-14.el9.x86_64.rpm  | grep /ld
  /usr/bin/ld
  ...

and since alternatives(8) removed it, rpm throws a warning?

If so, should /usr/bin/ld really be in %files ?

Thanks!


Version-Release number of selected component (if applicable):
binutils-2.35.2-14.el9

Comment 1 Nick Clifton 2022-01-20 14:50:59 UTC
The binutils.spec files contains:

  # %%verify(symlink) does not work for some reason, so using "owner" instead.
  %verify(owner) %{_bindir}/%{?cross}ld
 
In the %files section.  This is presumably the cause.  I will investigate changing this.

Comment 2 Nick Clifton 2022-01-24 14:46:01 UTC
Fixed in binutils-2.35.2-16.el9

Comment 5 Miloš Prchlík 2022-01-25 15:03:22 UTC
Verified with binutils-2.35.2-17.el9.

Comment 7 errata-xmlrpc 2022-05-17 15:58:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: binutils), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3985


Note You need to log in before you can comment on or make changes to this bug.