Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/pako/__pycache__/config_loader.cpython-36.pyc |
FileSize | 1948 |
MD5 | B5B17B9B5D32332CB4C4E81D567A42CE |
SHA-1 | 4E01425A2186A97EF05D7E1F307DD722676573BC |
SHA-256 | 2DF212089AA78C8D6DDEB0901873009126F6CC6F1AFC93D49C659EAC301D75C3 |
SSDEEP | 48:SbsrTn0THb3lA8jBg6HWAGCJRGe1OFCddogWlgdK3OT9to:XT0T7FW62JFe1OCdogW+d7pto |
TLSH | T1064183C30349EE6AF44EF8B4D29D02282D9773B3778ED0831205A19DBC560E409B6A97 |
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 |
---|---|
MD5 | 0B300E39B14FBC8940B485D7E2C2FA89 |
PackageArch | noarch |
PackageDescription | Often, scripts need to install system dependencies using the native package manager of the user's OS. Typically, this is solved by having some bash script that runs apt-get, assuming the user is on Ubuntu. Smarter scripts use hand crafted code to detect the user's platform and aggregate a set of dependencies on a few of the more popular platforms. Our approach is different: * Parse package format (devel/debug/normal library or executable) * Look up package managers that exist in PATH * Format parsed package with common package convention of package manager More on https://github.com/MycroftAI/pako |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python3-pako |
PackageRelease | bp153.1.15 |
PackageVersion | 0.2.3 |
SHA-1 | F96357451A5381C6FA76EF2BCEABF8F023E3B7D9 |
SHA-256 | 0D04A26BA60C8D2860A2C03618F5EC52D6CAA6E0D0A5E62F5F9936026252A06A |
Key | Value |
---|---|
MD5 | C40FFC37548034160E5433E0F2C0EFBE |
PackageArch | noarch |
PackageDescription | Often, scripts need to install system dependencies using the native package manager of the user's OS. Typically, this is solved by having some bash script that runs apt-get, assuming the user is on Ubuntu. Smarter scripts use hand crafted code to detect the user's platform and aggregate a set of dependencies on a few of the more popular platforms. Our approach is different: * Parse package format (devel/debug/normal library or executable) * Look up package managers that exist in PATH * Format parsed package with common package convention of package manager More on https://github.com/MycroftAI/pako |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python3-pako |
PackageRelease | lp152.1.1 |
PackageVersion | 0.2.3 |
SHA-1 | 44CCAF5CC3B4C6CB83A38F0744D033AD46B9B6D2 |
SHA-256 | 5C838C30FBC82C1C44B73CB16008CAC137ACE5EF1C42DC3FF9839154B22615CE |