| Key | Value |
|---|---|
| FileName | ./usr/lib/x86_64-linux-gnu/libbytesize.so.1.0.0 |
| FileSize | 30632 |
| MD5 | 4BDF04FC69230518331B85A85D925016 |
| SHA-1 | A8245BC5F007791130F0A4903CD4C05B6902563F |
| SHA-256 | 6BD7C6697282D991B237D7CA49D2F8070FC5E87BE2C0E0FE3A4C9B15B717EC39 |
| SSDEEP | 192:RKXZw1g83CR4DsHPxtiUtKh3FjqS9wB5coQ4trzIfXB/igPzLD4C5o0eIj2cxPmz:UUSNHnixhZrwrcN4tcB6gPzUl |
| TLSH | T19ED2D53BB1829DFFD180CA34864791353574B542EA12B62B620463BD3F81F298B5AFB5 |
| hashlookup:parent-total | 2 |
| hashlookup:trust | 60 |
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 |
|---|---|
| FileSize | 11396 |
| MD5 | 671B07148CE47B23E769711C118190E6 |
| PackageDescription | library 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. |
| PackageMaintainer | Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org> |
| PackageName | libbytesize1 |
| PackageSection | libs |
| PackageVersion | 2.6-1 |
| SHA-1 | 0533836913FEB0A437FAEB520F2CAD632445A102 |
| SHA-256 | 3C48B28A1D1DD31807131C850F8DF44D2849D570F3F1C3C2135CD5036657C82C |
| Key | Value |
|---|---|
| FileSize | 11380 |
| MD5 | EBE2373F5F4822A78B1618E63E96C95A |
| PackageDescription | library 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. |
| PackageMaintainer | Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org> |
| PackageName | libbytesize1 |
| PackageSection | libs |
| PackageVersion | 2.5-1 |
| SHA-1 | F1D7E503200BB6680F06CAF73B2AE9DB40C9BD62 |
| SHA-256 | 9739C48AF8DD2A40E389E844A9932871A9A03CE4840C783FFB68B79530C9914D |