Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 771858

Summary: Incorrect URL reported by btrfs-progs-0.19-12.el6.x86_64 rpm
Product: Red Hat Enterprise Linux 6 Reporter: amedeo
Component: btrfs-progsAssignee: Josef Bacik <jbacik>
Status: CLOSED NOTABUG QA Contact: Eryu Guan <eguan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2CC: kzhang, rwheeler
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-07 14:15:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description amedeo 2012-01-05 09:28:55 UTC
Description of problem:
Rpm package btrfs-progs-0.19-12.el6.x86_64 report that it's url main page is:
"http://btrfs.wiki.kernel.org/index.php/Main_Page" but going to this page you can receive http error code 404 (Page not found). 
The correct page at the time of writing is: "https://btrfs.wiki.kernel.org"

Version-Release number of selected component (if applicable):
btrfs-progs-0.19-12.el6.x86_64

How reproducible:


Steps to Reproduce:
1. yum install btrfs-progs
2. rpm -qa | grep btrfs-progs | xargs rpm -q --info
Name        : btrfs-progs                  Relocations: (not relocatable)
Version     : 0.19                              Vendor: Red Hat, Inc.
Release     : 12.el6                        Build Date: mar 11 gen 2011 20:06:13 CET
Install Date: gio 05 gen 2012 10:08:16 CET      Build Host: x86-004.build.bos.redhat.com
Group       : System Environment/Base       Source RPM: btrfs-progs-0.19-12.el6.src.rpm
Size        : 1540765                          License: GPLv2
Signature   : RSA/8, mer 13 apr 2011 08:23:03 CEST, Key ID 199e2f91fd431d51
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://btrfs.wiki.kernel.org/index.php/Main_Page
Summary     : Userspace programs for btrfs
Description :
The btrfs-progs package provides all the userpsace programs needed to create,
check, modify and correct any inconsistencies in the btrfs filesystem.

  
Actual results:
rpm -qa | grep btrfs-progs | xargs rpm -q --info
...
URL         : http://btrfs.wiki.kernel.org/index.php/Main_Page
...

Expected results:
rpm -qa | grep btrfs-progs | xargs rpm -q --info
...
URL         : http://btrfs.wiki.kernel.org
...

Additional info:

Comment 2 Josef Bacik 2012-06-07 14:15:38 UTC
It was just because they were migrating things over, it is working now.