Description of problem: Current versions of xmlrpc-c-devel cause ldconfig to print errors when it's run. Version-Release number of selected component (if applicable): xmlrpc-c-devel-1.21.00-1301.1851.fc13.x86_64 How reproducible: Always Steps to Reproduce: 1. Install xmlrpc-c. 2. Run /sbin/ldconfig. Actual results: ldconfig: /usr/lib64/libxmlrpc_server_abyss.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_server++.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_server_abyss++.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_abyss.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_cpp.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_packetsocket.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_server_cgi.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_client.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_server_pstream++.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_server_cgi++.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_server.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc_client++.so is not an ELF file - it has the wrong magic bytes at the start. ldconfig: /usr/lib64/libxmlrpc++.so is not an ELF file - it has the wrong magic bytes at the start. Expected results: Quiet success.
has been fixed yesterday http://koji.fedoraproject.org/koji/buildinfo?buildID=157735
*** Bug 570626 has been marked as a duplicate of this bug. ***
*** Bug 570976 has been marked as a duplicate of this bug. ***
How about getting an update to F-13 instead of refering to a koji build?
F-13 has not been released so there is no update channel. Just wait for the next milestone.
F-13 has been branched, which means, you can now submit an 'update' to F-13. Once this 'update' is stable, it is added to the normal F-13 repository. Currently there is no updates repository for F-13, which means all updates you submit to F-13, will go to the F-13 dist repository. See the updates for F-13 as usual: https://admin.fedoraproject.org/updates/F13 See Use Case 5,8 at: https://fedoraproject.org/wiki/No_frozen_rawhide_announce_plan#Use_Cases (Sorry, need to reopen again...)
Forgot to add: Maybe there is no F-13 subfolder even when you run cvs update. I don't remember the deeper update command for cvs anymore, so I checkout new. Then there will be a F-13 subfolder and you can 'make update' as usual.
ok; I did a 'make update' and requested push to stable. https://admin.fedoraproject.org/updates/xmlrpc-c-1.21.00-1303.1851.fc13