Bug 2209151 - Cannot install gcc-toolset-13-binutils due to wrong alternatives requires
Summary: Cannot install gcc-toolset-13-binutils due to wrong alternatives requires
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: binutils
Version: 8.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nick Clifton
QA Contact: Miloš Prchlík
URL:
Whiteboard:
Depends On: 2209148
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-22 21:25 UTC by Marek Polacek
Modified: 2023-06-30 11:59 UTC (History)
1 user (show)

Fixed In Version: gcc-toolset-13-binutils-2.40-11.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 2209148
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-157874 0 None None None 2023-05-22 21:26:54 UTC

Comment 1 Marek Polacek 2023-05-22 21:26:26 UTC 
Nick, I can create an MR if the el9 is approved.
Comment 2 Nick Clifton 2023-05-23 09:53:03 UTC 
(In reply to Marek Polacek from comment #1)
> Nick, I can create an MR if the el9 is approved.

No worries - I will do it myself.  Thanks for the patch! :-)

Cheers
  Nick
Comment 3 Nick Clifton 2023-05-23 12:20:38 UTC 
Fixed in gcc-toolset-13-binutils-2.40-9.el8
Comment 7 Nick Clifton 2023-06-12 13:04:05 UTC 
I am taking this one back.  It turns out that just using "alternatives" on the command line still selects the wrong alternatives script for GTS-13 binaries.  This caused:

https://bugzilla.redhat.com/show_bug.cgi?id=2213913

I am now testing an version that uses an explicit path to the alternatives script.
Comment 9 Marek Polacek 2023-06-12 14:17:17 UTC 
Clearing DTM/ITM.  Please re-set.
Comment 11 Nick Clifton 2023-06-12 14:29:38 UTC 
Should be fixed in: gcc-toolset-13-binutils-2.40-11.el8
Comment 12 Miloš Prchlík 2023-06-30 11:59:52 UTC 
Verified with gcc-toolset-13-binutils-2.40-11.el8.
Note You need to log in before you can comment on or make changes to this bug.