Bug 1872497 - URL in RPM is incorrect
Summary: URL in RPM is incorrect
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: deltarpm
Version: 7.8
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: swm-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-25 22:22 UTC by Mark Chandler
Modified: 2021-11-10 18:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-10 13:21:06 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 17688 0 None None None 2020-08-25 22:27:43 UTC

Description Mark Chandler 2020-08-25 22:22:54 UTC
Description of problem:
The URL value for the RPM package is "http://gitorious.org/deltarpm/deltarpm". This URL is unreachable.

Version-Release number of selected component (if applicable):
deltarpm-3.6-3.el7.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Install deltarpm (yum install deltarpm)
2. Check the URL info in the RPM (rpm -qi deltarpm | grep URL)


Actual results:
URL         : http://gitorious.org/deltarpm/deltarpm

Expected results:
URL         : https://github.com/rpm-software-management/deltarpm

Additional info:
This bug was first raised with CentOS. https://bugs.centos.org/view.php?id=17688

Comment 4 Kyle Walker 2021-11-10 13:21:06 UTC
Good afternoon.

On Aug 6, 2020 Red Hat Enterprise Linux 7 entered Maintenance Support 2 Phase.

https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase

That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released". This BZ does not appear to meet Maintenance Support 2 Phase criteria so is being closed WONTFIX. If this is critical for your environment please open a case in the Red Hat Customer Portal, https://access.redhat.com, provide a thorough business justification and ask that the BZ be re-opened for consideration in a future erratum.


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