Result for B92A6FBB258C5D6569C3C6756218FE103E29F343

Query result

Key Value
FileName./usr/share/doc/libbytesize1/changelog.Debian.gz
FileSize1119
MD5B3D4F015C43ED33F33E33A4F60B595CA
SHA-1B92A6FBB258C5D6569C3C6756218FE103E29F343
SHA-256C77231FF240DB7046E002B17E70E18D9C58363C9DE2669DCF6A85D3E76144531
SSDEEP24:Xn/AbXeUJ6G5+iPgFk7d2RwNhASQr1FDv7LR:XnoTtJZnoYnb6X7l
TLSHT1DC21F95E413005064C02C510FB241821623C7B8F7AD89237D76ED528C4FC35DB873303
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
FileSize12980
MD5945BD366BAD00AB354596569F4097276
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamelibbytesize1
PackageSectionlibs
PackageVersion2.4-1
SHA-1E55C90ABF3ACE3CC85E810268D449900533E76A6
SHA-25603782674C8CFAF9140C6554D5647D45AB56E3AF5B182E1415CE995C3562A0CC3
Key Value
FileSize11384
MD5C22FABDE07858003D5D66657FBA98B60
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamelibbytesize1
PackageSectionlibs
PackageVersion2.4-1
SHA-1162CC7A7047CD56FFB873CFD103B98A30B96ED88
SHA-2560C1E692606EBB3D6F1AEA1E3A12517F642F7DFB33F58ECFDABFB4DF4D6AA3F2B