RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1967221 - consider removing libmetalink from RHEL-9
Summary: consider removing libmetalink from RHEL-9
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libmetalink
Version: 9.0
Hardware: All
OS: Linux
high
high
Target Milestone: beta
: 9.0 Beta
Assignee: Richard Lescak
QA Contact: rhel-cs-infra-services-qe
URL:
Whiteboard:
Depends On: 1967213 1967216
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-02 16:10 UTC by Kamil Dudka
Modified: 2021-06-21 12:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1967213
Environment:
Last Closed: 2021-06-10 08:44:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Kamil Dudka 2021-06-02 16:10:53 UTC
libmetalink seems to be dead upstream:

    https://launchpad.net/libmetalink

Today curl upstream decided to stop using it.  I filed RHEL-9 bugs for curl and wget to stop using this library:

    bug #1967213
    bug #1967216

Assuming both get resolved, please consider removing libmetalink from RHEL-9.


+++ This bug was initially created as a clone of Bug #1967213 +++

Description of problem:
Today curl upstream announced that they are going to completely remove support for metalink from curl already in the next release of curl due to a number of difficult to fix security issues:

    https://curl.se/mail/archive-2021-06/0006.html
    https://github.com/curl/curl/pull/7176

I believe it is not too late to follow this decision in RHEL-9, too.  We could hardly support it ourselves till RHEL-9 EOL when it is broken and unsupported upstream since the beginning.


Version-Release number of selected component (if applicable):
curl-7.76.1-4.el9


Steps to Reproduce:
1. curl -V | grep -i metalink


Additional info:
We might want to do the same with wget and consider removing libmetalink, which seems to be dead upstream:

    https://launchpad.net/libmetalink

I will file separate bugs for wget and libmetalink for consideration.

Comment 1 Richard Lescak 2021-06-07 07:40:52 UTC
Hi, I will remove libmetalink after both curl and wget get resolved. Thanks for the report.

Comment 2 Michal Ruprich 2021-06-10 06:15:28 UTC
Hi Richard,

wget is now metalink-free. The corresponding bug is in ON_QA and will probably stay that way until RHEL9 is released so it will not show itself as resolved here in this bug. But now it should be ready and you can start the process of removing libmetalink from the distribution.

Regards,
Michal

Comment 3 Kamil Dudka 2021-06-10 06:44:22 UTC
Yes, both the blocking bugs are now technically resolved in el9 beta.  It should be safe to proceed with the package removal.  Thanks to all involved!


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