Result for 05AFA94E5BDC4B0FC89F1B59C9A86D8A2014C20A

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/Pyro4/constants.py
FileSize429
MD5C96FA4EBF3CDBB9CC7AFA71E0569ADDC
SHA-105AFA94E5BDC4B0FC89F1B59C9A86D8A2014C20A
SHA-25676B931F9B70F3CE2BA136857B19B357FAE5BD529CBC90BE3A601A04BD7797D60
SSDEEP12:Sexoch63c3gqCznstMd1nrijijXgKdAQbImMsI6y95Y:x6s3Ksti1mOjuk2Y
TLSHT1D0E0E506104286A716AB8EA3EE933883F75D5B70703D18888D9AF656A1E7C0F8259649
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5714F1CAEB08050255C5A4FD880CE3E51
PackageArchnoarch
PackageDescriptionPyro provides an object-oriented form of RPC. You can use Pyro within a single system but also use it for IPC. For those that are familiar with Java, Pyro resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or RMI. Pyro4 is a reimplementation of the original pyro, that was begun in 2010. According to upstream, pyro4 can now be considered the new ‘main’ Pyro version. Since it is not API compatible to pyro-3.x, the package was renamed to Pyro4
PackageMaintainerumeabot <umeabot>
PackageNamepython-pyro415
PackageRelease8.mga7
PackageVersion4.15
SHA-17DFC94931AA2823A5896D05300D79F51A9110A1E
SHA-2562E2C4BA7A3A2CF316CAF13F4A27D527B37B144FE94E3DDFF8A978590163D46CC