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 1579178 - upstream URL reference in the rpm header is unreachable/dead
Summary: upstream URL reference in the rpm header is unreachable/dead
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-chardet
Version: 7.5
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: Lumír Balhar
QA Contact: Jan Kepler
URL:
Whiteboard:
Depends On:
Blocks: 1660491 1660494
TreeView+ depends on / blocked
 
Reported: 2018-05-17 06:40 UTC by Christian Horn
Modified: 2019-08-06 12:40 UTC (History)
5 users (show)

Fixed In Version: python-chardet-2.2.1-3.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1660491 1660494 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:40:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2068 0 None None None 2019-08-06 12:40:44 UTC

Description Christian Horn 2018-05-17 06:40:06 UTC
Description of problem:
upstream URL reference in the rpm header is unreachable/dead

Version-Release number of selected component (if applicable):
python-chardet-2.2.1-1.el7_1.noarch.rpm

How reproducible:
always 

Steps to Reproduce:
1. rpm -qi /mnt/store/deploy/repos/rhel-7.5/Packages/python-chardet-2.2.1-1.el7_1.noarch.rpm|grep URL
warning: /mnt/store/deploy/repos/rhel-7.5/Packages/python-chardet-2.2.1-1.el7_1.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
URL         : http://chardet.feedparser.org

2. wget http://chardet.feedparser.org
--2018-05-17 08:39:02--  http://chardet.feedparser.org/
Resolving chardet.feedparser.org (chardet.feedparser.org)... failed: Name or service not known.
wget: unable to resolve host address ‘chardet.feedparser.org’

Comment 2 Raphael Groner 2018-09-28 21:04:20 UTC
The project moved to GitHub:
https://github.com/chardet/chardet

This needs a fix in Fedora as well.

Comment 4 Lumír Balhar 2018-12-18 12:54:57 UTC
I'm going to create copies of this bug for RHEL8 and python36 module in RHEL8.

Comment 5 Lumír Balhar 2018-12-18 13:04:56 UTC
PR for RHEL 7.7: https://src.osci.redhat.com/rpms/python-chardet/pull-request/1

Comment 10 errata-xmlrpc 2019-08-06 12:40:42 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, 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-2019:2068


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