Red Hat Bugzilla – Bug 430344
Missing Python Egg info in f8 build
Last modified: 2008-11-18 03:19:17 EST
Description of problem:
One of the scripts of the python-ZSI package breaks due to missing egg info in
the PyXML package from f8 (https://bugzilla.redhat.com/show_bug.cgi?id=429464).
This seems to be fixed in the latest rawhide/f9 build PyXML-0.8.4-8
(https://bugzilla.redhat.com/show_bug.cgi?id=364961). Can you build the new
version for f8 (and probably f7) as well?
Version-Release number of selected component (if applicable):
BTW. Release tag doesn't contain disttag. You could add it when building new
I'm now also experiencing this bug. Any reason not to make an update?
FWIW, I installed the F9 version PyXML-0.8.4-8.i386.rpm from koji on my F8
system and it seems to work.
This bug is for me as well.
PyXML-0.8.4-8.fc8 has been submitted as an update for Fedora 8
Rebuild is done, requested for updates-testing.
Build is available here :
I've added egg infos and disttag, also corrected a few rpmlint errors.
PyXML-0.8.4-8.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update PyXML'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-3112
PyXML-0.8.4-8.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
Looks like this bug is still current in RHEL. At least it still is in CentOS, I don't have a real RHEL box for testing.
There are no owner (https://admin.fedoraproject.org/pkgdb/packages/name/PyXML) nor branches in the CVS (http://cvs.fedoraproject.org/viewvc/rpms/PyXML/) for Elx.
Do not know where you package came from, but I think it was probably not from EPEL.
It came from CentOS 5, and as far as I can see it is in RHEL5 proper.
I've just checked, and its indeed on CentOS 5, from the base repository.
Maybe you should consider opening a new bug against RHEL and not Fedora, the proper maintenair would be selected and advised ?
Oops, I had not noticed these were different packages. I just reported the bug against RHEL5.