I have an RPM that is sitting on a server I inherited. On the server is an RPM that is needed for one of the applications that it runs. xmlrpc-epi-0.54.2-1.x86_64.rpmRather than using this mystery rpm, I want to find the equivalent package on epel.yum search xmlrpc returns over a dozen results.How can I find out where this RPM came from, or at least verify if it is the same package that exists on one of the common repos (epel). The most information I can find is with rpm --query:[root@us-devops-build02 tmp]# rpm --query --info -p xmlrpc-epi-0.54.2-1.x86_64.rpmName        : xmlrpc-epi                   Relocations: /Version     : 0.54.2                            Vendor: noneRelease     : 1                             Build Date: Wed 23 Oct 2013 09:08:24 PM UTCInstall Date: (not installed)               Build Host: foo.barGroup       : default                       Source RPM: xmlrpc-epi-0.54.2-1.src.rpmSize        : 1060096                          License: unknownSignature   : (none)Packager    : <autobuild@foo.bar>URL         : http://example.com/no-uri-givenSummary     : no description givenDescription :no description givenEdit1Reasoning:The previous admin had a script that would use this RPM. I don't know why he used this special snowflake instead of using a package from epel.  I'm moving the script to puppet so I'd like to use official sources as much as possible. Edit2rpm -kv shows the followingrpm --checksig --verbose xmlrpc-epi-0.54.2-1.x86_64.rpmxmlrpc-epi-0.54.2-1.x86_64.rpm:    Header SHA1 digest: OK (2f2f1619cd1e251cc37675b57656f1394c74024e)    MD5 digest: OK (656e5696da9f259a47725dacd38b9697)Edit3 Here are all the 'xmlrpc' packages on epelsems-xmlrpc2di.x86_64 : XMLRPC interface for SEMSxmlrpc-c-c++.i686 : C++ libraries for xmlrpc-cxmlrpc-c-c++.x86_64 : C++ libraries for xmlrpc-cxmlrpc-c-client.i686 : C client libraries for xmlrpc-cxmlrpc-c-client.x86_64 : C client libraries for xmlrpc-cxmlrpc-c-client++.i686 : C++ client libraries for xmlrpc-cxmlrpc-c-client++.x86_64 : C++ client libraries for xmlrpc-cxmlrpc-c-devel.i686 : Development files for xmlrpc-c based programsxmlrpc-c-devel.x86_64 : Development files for xmlrpc-c based programsxmlrpc3-javadoc.noarch : Javadoc for xmlrpc3erlang-xmlrpc.x86_64 : HTTP 1.1 compliant XML-RPC library for Erlangkoji-hub.noarch : Koji XMLRPC interfacelua-xmlrpc.noarch : Lua package to access and provide XML-RPC servicesphp-ZendFramework2-XmlRpc.noarch : Zend Framework 2: XML-RPC Componentphp-xmlrpc.x86_64 : A module for PHP applications which use the XML-RPC protocolpython-offtrac.noarch : Trac xmlrpc librarypython-wordpress-xmlrpc.noarch : WordPress XML-RPC API Integration Librarytrac-xmlrpc-plugin.noarch : Allows Trac plugins to export their interface via XML-RPCxmlrpc-c.i686 : A lightweight RPC library based on XML and HTTPxmlrpc-c.x86_64 : A lightweight RPC library based on XML and HTTPxmlrpc-c-apps.x86_64 : Sample XML-RPC applicationsxmlrpc3-client.noarch : XML-RPC client implementationxmlrpc3-client-devel.noarch : Source for XML-RPC client implementationxmlrpc3-common.noarch : Common classes for XML-RPC client and server implementationsxmlrpc3-common-devel.noarch : Source for common classes of XML-RPCxmlrpc3-server.noarch : XML-RPC server implementationxmlrpc3-server-devel.noarch : Source for XML-RPC server implementation
How can I find out where an RPM came from?
yum;rpm
You can use:rpm -Kv xmlrpc-epi-0.54.2-1.x86_64.rpmto display the package's signature (if it has one). From that you could try and trace back the originator of the package.The package itself (without signature) could have been rebuild by anyone. If it is not signed I would try (from the generic rpm field data) to see if it was built on the machine itself. You can also try the logs if they go back to October last year to find out when file was copied to the machine if it was not build on it (might have been scp-ed).