Parents (Total: 24)

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

Key	Value
FileSize	467472
MD5	FA5B5736F7912193F2DD41AED9B3ABDC
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2
SHA-1	1A4E7E5ABE2737557FF84F481B94B0D236AE3DC4
SHA-256	F292CAABFE11C95AEF2E53D08A98B406E79815348F8203AFE28C33EB01D711E0

Key	Value
FileSize	545608
MD5	DC0FA3DE6781E292D08780C161813353
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2
SHA-1	20AF0662B6A1D99C19959D05A3744A5389912E52
SHA-256	E9616C11931F58605FA709AC0843EA3FD9D54F84CB0200ED17F1F92649B0DBDC

Key	Value
FileSize	420128
MD5	ED675CB871B6287A74DF0CCE784CECE3
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2
SHA-1	26D561A12666FB43805304531C72A3A040490299
SHA-256	21C1D992B260D61A6016732FA0295678BB0F6D44D534D0A1BCE011FBF8FBAC04

Key	Value
FileSize	534748
MD5	527978F1D4E59F7A292072C3A02F6AA3
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2~18.04
SHA-1	2C7E64AD427B366280FE3BB4F3CC6AB0D30FA729
SHA-256	1D1C81CABA2BF12D369AB1C10F473108440306A26487ADB93A1D506263EBF0EA

Key	Value
FileSize	539980
MD5	7892561681F29746B8D8CD890421A5E5
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2~18.04
SHA-1	4E1747FA142D26A3C7A2006F896C43133A451982
SHA-256	8BE27477153FD4D2B807C41CA211F4F13526C0DDBA86E012144CAB233B31DA2C

Key	Value
FileSize	463672
MD5	D93453E3CF14341B67F3D42B91DD448A
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2
SHA-1	50F32966A6D74EF04B858DD43DB380D8C5F4F1D2
SHA-256	3A1AB5960890840844767E9E0FC49DFCE23E075665F1F66482EFCF3FAA4F2A74

Key	Value
FileSize	540264
MD5	BCB2833DA2FB636487406208E3D07D1F
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2
SHA-1	65484C6ACD76166DD07E89ABA31C10FA2CACB708
SHA-256	D9DBEAD0C2402A5F19DED8E915A62D28C115AED423882A03AEADB70D9B80CCBF

Key	Value
SHA-1	6967B1AC0AACBDE81C8C01EDD573F470F0AFD8E4
snap-authority	canonical
snap-filename	M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_379.snap
snap-id	M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_379
snap-name	scrcpy
snap-publisher-id	jQgc0rEVirS9Mk0Ud0UWWPFSwlGF3yVu
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2019-10-18T13:48:29.718028Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_379.snap

Key	Value
FileSize	416668
MD5	098E63CD65F25858AE726E6DCFC33117
PackageDescription	Google's internal fork of OpenSSL for the Android SDK The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl
PackageSection	libs
PackageVersion	8.1.0+r23-2
SHA-1	6BD8D1ADB16243C5E29750A21339E0A6DBBB3ED9
SHA-256	C59AA944A81565F3FA04CB3E0D29E959A4271C04E88F59BC207C42BACCB12A4C

Key	Value
SHA-1	7461E1E57F84A2E87220A7ED6FF5C0C8D8320649
snap-authority	canonical
snap-filename	M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_371.snap
snap-id	M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_371
snap-name	scrcpy
snap-publisher-id	jQgc0rEVirS9Mk0Ud0UWWPFSwlGF3yVu
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2019-10-18T13:48:29.718028Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/M7yvgnqOvyQj64bolfpawIAEwHv7dQ5G_371.snap