Parents (Total: 20)

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

Key	Value
MD5	5D34F30CF6D0E836F3C698123D6B0B1B
PackageArch	armv7hl
PackageDescription	This package provides debug sources for package android-tools. Debug sources are useful when developing applications that use this package or when debugging this package.
PackageMaintainer	daviddavid <daviddavid>
PackageName	android-tools-debugsource
PackageRelease	3.mga7
PackageVersion	8.0.0_r4
SHA-1	0C8A1CE0CB7DC9D0ABF24A9F96BEB4CB4D4EB3F9
SHA-256	FBB08F29255218AFAE063B00A579A1FA4E2115974EA70F34C7A6C2200C4E62E1

Key	Value
MD5	0584B5441A0B653A96616DE1546F1CA6
PackageArch	aarch64
PackageDescription	This package provides debug sources for package android-tools. Debug sources are useful when developing applications that use this package or when debugging this package.
PackageMaintainer	daviddavid <daviddavid>
PackageName	android-tools-debugsource
PackageRelease	3.mga7
PackageVersion	8.0.0_r4
SHA-1	174224066DFE62D837A460EE61596AC6A171B18B
SHA-256	A2C3EC30D70260692F4EC317C2C3CAEF9A6915D734BEB3C4D501D46B195199AD

Key	Value
FileSize	181736
MD5	6CE7FE274F88888E4579D39576DCC073
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2
SHA-1	18DDCAB4081B9BA06A7BF95A6EAC2CB3E27F0223
SHA-256	87EED1F1549DB594739ABC910FF70CE911FB2FCD298E18FA46678326B2B64E43

Key	Value
FileSize	181380
MD5	F6A583A383341ACE7F0E5FCA1DEE5941
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2
SHA-1	1A4E06BE14E0104BDAF8A702E68CAFA792E8DB89
SHA-256	84C11538D9CC5A08288A238F7C7B13C42F81B12C9D857687F1961CFB6A00852D

Key	Value
FileSize	181732
MD5	A52AA81511D42A5A27B22E2D8D4EF2F9
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2
SHA-1	21F420A16ED981CD52F9E041595DB46C23B9F538
SHA-256	3B41FF6A8F4B054B5AB2B526EE9D4D2F75651D7372800BA3614672302498CD71

Key	Value
FileSize	181728
MD5	8161B99FF0E4E3E231A1ECBFC6AF7188
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2
SHA-1	23F6D28C831A95857C1B67C00D883A5B6B46510A
SHA-256	346E068301EE14E74D675634566D35BCF05983898313D08A95C03B03F71EF300

Key	Value
FileSize	181376
MD5	BA2FC3CC73C61A11433F654816139BE7
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2
SHA-1	2795E79B0E0CFCA27DCADA1836E4272919B03D11
SHA-256	76EBC6A9ADD2521035F8A74B845F8C4BA6775932C8C07FA5E522714AB4C892EA

Key	Value
FileSize	181916
MD5	9C44CC56DB4C7E9D48A7F43E4D2D980A
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2~18.04
SHA-1	3CF937382EAB99A192112EB0D522BCD8D07C6F3F
SHA-256	4DF57210826AAEA75C09813FA657DA8443943055519AF696ACDFC13C95B78E3A

Key	Value
FileSize	181732
MD5	54123735BB8A52F9E9784E70D70EEAC1
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2
SHA-1	4612648E44BDF52427289CD07EB8B94709383D88
SHA-256	EA00BD66EE76330CC5F844B278BAF2B5DCE78A725F4252EFDFC4344C6A8AE500

Key	Value
FileSize	181732
MD5	D135827934F4F72FFB0C1CE2D6999145
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel 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. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	8.1.0+r23-2
SHA-1	5FBC01226E4DB10A779E719921584EE9C4F4008B
SHA-256	DB185F57A572B801F7208A450B4722873098A7B24E736E532161723F66582E19