Description of problem:
broken URL in xmlrpc3-client package description
URL : http://xml.apache.org/xmlrpc3/
the correct URL seems to be http://ws.apache.org/xmlrpc/
Version-Release number of selected component (if applicable):
Steps to Reproduce:
rpm -qi xmlrpc3-client
The latest version of xmlrpc is 3.1
I don't think we'll be updating to xmlrpc 3.1 unless it's not API-breaking.
Would you be willing to verify that it doesn't break API? The only project that
I know of that uses xmlrpc in Fedora is eclipse-mylyn (the Mylyn Eclipse.org
project). If that still works with the new xmlrpc, it's probably fine to move
A better question: would you be willing to co-maintain xmlrpc?
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.
If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)
Thanks for your help and we apologize for the interruption.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
This bug has been triaged
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Still wrong link in f11.
As far as I can see from the changelog, version 3.1 didn't change API but gives many bugfixes. I don't use it myself (yet?) so, unfortunately, I can't say anything about compatibility from own experience.
I've asked upstream about moving to 3.1:
Is this really just a simple matter of updating the URL? If that's decouple-able from moving to 3.1, I'll do it in a heart beat.
this particular bug is about fixing the broken URL only.
Fixed in CVS. Build is going now:
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I should have closed this. It looks like what I have installed in F-12 (what went out with F-12) has the fix: 3.0-4.10.fc12.