Result for 589007358ECBDDEB2B258F9F86C93D890CDA4253

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/libbytesize.so.1.0.0
FileSize30004
MD5C94DB843D7F0118297DF9B7B05407329
SHA-1589007358ECBDDEB2B258F9F86C93D890CDA4253
SHA-256320EF93B7254CA41307F66528D09C7D7609875D8F472B1519F117CBA66E17195
SSDEEP768:ZrGUNHefTRlHC6Xe046Ruyc1scJQFbSH36my3IvQEFsn57pBimMCyHLJB7CLYsz2:VGZtFe046Ruyc1JJQFzThNk
TLSHT17ED2F72BB7C3D9F1F3A245B8079782267A308516D517D7E6F70E33897AB23592C22274
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
FileSize12948
MD513730CC90ACC10FB0B1156030855DBD3
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-1564E436281770F13060595E5838E642AFA9E4893
SHA-2564F23F678B1A77EDFB48F40B83A0174CDD9B0CCAF5D005E61793DEDB1CCF22ED7
Key Value
FileSize12924
MD5E4C0B2FA39BE7FDC5685A0383EB51E47
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-1779C9DDC378912C363F8DEB94B682940AE83846F
SHA-256259B4D2897EF57DADBF8362ACAF387211794644C4E0E2BCCCADB4C5E8639F640