Bug 139987 - URL field is out of date -- should be http://xmlsoft.org/
Summary: URL field is out of date -- should be http://xmlsoft.org/
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: libxml
Version: 3
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL: http://xmlsoft.org/
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-19 03:36 UTC by Matthew Miller
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-30 14:57:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthew Miller 2004-11-19 03:36:28 UTC
Description of problem:

This is trivial, but the URL: field in the libxml (not libxml2) RPM
points to http://rpmfind.net/veillard/XML/, which tells me that I'm
"Lost in the WWW".

Version-Release number of selected component (if applicable):

I noticed it in the updates that appeared for FC2 and FC3
(libxml-1.8.17-10.1.2. and libxml-1.8.17-12, respectively). There
doesn't appear to be a libxml package in rawhide currently -- I assume
it's finally declared obsolete.

How reproducible:

Every time you look at the RPM's metainfo. :)

Steps to Reproduce:
1. rpm -qp --qf '%{url}\n' libxml-1.8.17-*.i386.rpm 

  
Actual results:

http://rpmfind.net/veillard/XML/

Expected results:

http://xmlsoft.org/

Additional info:

http://rpmfind.net/veillard/XML/ actually works sometimes, but then
goes away on reload -- I notice that there's round-robin DNS, and
that's probably what's going on.

Comment 1 Daniel Veillard 2004-11-30 14:57:52 UTC
I can't fix the round robin. I don't think I will fix the
libxml package which is really obsolete, I don't think it's 
worth pushing updates just for that change. So while your
report is right, I will close it as a DEFERRED. People doing
any kind of active development should use libxml2 anyway
and that package has the proper informations,

  thanks,

Daniel



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