Result for CFCE67D6DA24A3321B741E19E9269CA229304911

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/libbytesize.so.1.0.0
FileSize17776
MD5C337979BED37BE8689DE920E5E81C895
SHA-1CFCE67D6DA24A3321B741E19E9269CA229304911
SHA-2565691B1E6EDBC964B9BBE10EE34FA53197CAFCE1CB49B1F64BD1799E5D9B4B051
SSDEEP384:IFPIJNHwXPb7vkzkfYfYwfvxufQh1yhn:IFgJNHSP3vk6YQkXh1
TLSHT18C82D7F6A1C6DC93F5C1637EF867CEC40151C388DD8A9B83914CA0B45EA56AF4E92F60
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
FileSize10644
MD5635EAC3F2281D7577845D6696CD5FABB
PackageDescriptionlibrary for common operations with sizes in bytes Many projects need to work with sizes in bytes (be it sizes of storage space, memory,...) and all of them need to deal with the same issues like: . * How to get a human-readable string for the given size? * How to store the given size so that no significant information is lost? * If we store the size in bytes, what if the given size gets over the MAXUINT64 value? How to interpret sizes entered by users according to their locale and typing conventions? * How to deal with the decimal/binary units (MB vs. MiB) ambiguity? . This library aims to be as much generally usable as possible, small, fast and be easily interfaced from other languages.
PackageMaintainerUtopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>
PackageNamelibbytesize1
PackageSectionlibs
PackageVersion2.6-1
SHA-1A4B0A027BCEA916F7FD2A77EACAD23D96B84368F
SHA-2560C6BF2FFBE9C540446C12AFF08B5E65252C26C46F4535125DD2C785608FB55B2
Key Value
FileSize10624
MD5B433F31EB26E29F0CEF2C383BE9514F5
PackageDescriptionlibrary for common operations with sizes in bytes Many projects need to work with sizes in bytes (be it sizes of storage space, memory,...) and all of them need to deal with the same issues like: . * How to get a human-readable string for the given size? * How to store the given size so that no significant information is lost? * If we store the size in bytes, what if the given size gets over the MAXUINT64 value? How to interpret sizes entered by users according to their locale and typing conventions? * How to deal with the decimal/binary units (MB vs. MiB) ambiguity? . This library aims to be as much generally usable as possible, small, fast and be easily interfaced from other languages.
PackageMaintainerUtopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>
PackageNamelibbytesize1
PackageSectionlibs
PackageVersion2.5-1
SHA-1602948C68CE9B7F206E4D65D529AEBF3EAF0676C
SHA-256126BA5D03F1A91149D718B81A5C96CB97E61F54E734327EF44F97589DF23ACD6