Bug 1577719 - upstream URL reference in the rpm header is unreachable/dead
Summary: upstream URL reference in the rpm header is unreachable/dead
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: chrpath
Version: 8.1
Hardware: All
OS: All
unspecified
low
Target Milestone: pre-dev-freeze
: 8.1
Assignee: Marek Polacek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-14 03:49 UTC by Christian Horn
Modified: 2023-07-18 14:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-14 16:35:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Christian Horn 2018-05-14 03:49:43 UTC
Description of problem:
upstream URL reference in the rpm header is unreachable/dead

Version-Release number of selected component (if applicable):
chrpath-0.16-0.el7.x86_64.rpm

How reproducible:
always

Steps to Reproduce:
[chris@Гага́рин Downloads]$ rpm -qi /mnt/store/deploy/repos/rhel-7.5/Packages/chrpath-0.16-0.el7.x86_64.rpm|egrep '^Name|^URL'
warning: /mnt/store/deploy/repos/rhel-7.5/Packages/chrpath-0.16-0.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Name        : chrpath
URL         : ftp://ftp.hungry.com/pub/hungry/chrpath/
[chris@Гага́рин Downloads]$ 
$ ftp ftp://ftp.hungry.com/
ftp: ftp://ftp.hungry.com/: Name or service not known
ftp> 
$

Actual results:
upstream url not accessible.

Expected results:
upstream reference should be correct.

Additional info:

Comment 2 Marek Polacek 2018-05-22 19:57:33 UTC
I don't think chrpath deserves a respin in 7.6 just because of this.

Comment 3 Christian Horn 2018-05-23 01:22:13 UTC
If respin means that extra rounds of QA would be done or such, it's certainly not worth it, I agree.

Comment 4 Marek Polacek 2018-06-01 19:55:54 UTC
This package did not make the 7.6 ACL. Moving out for consideration at 7.7
planning phase. Note that this is not a commitment to fix in the 7.7 release.

Comment 8 Jeff Law 2020-01-14 16:35:35 UTC
I don't see a scenario where we're likely to want to burn QE resources on this, so I'm just going to close.


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