Parents (Total: 15)

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

Key	Value
FileSize	229384
MD5	DACE74053B5204E9364557645BF8268D
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	13~preview2-3
SHA-1	057B15825C0D6B81F13F69CA24198A48944FD79E
SHA-256	FB84B312C4805AEF3187979B253507C859AD03797625114E06C482ED7BED7AF4

Key	Value
FileSize	543556
MD5	F695439A326C00F2DCBD8B535216B6E7
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	13~preview2-3
SHA-1	8AD8CFE2A257E6A1023027233676B7109B51CE77
SHA-256	2429F9B185A7DED92310B0166C9C9CBC8A86DDD6083C7DBC03F81E21A99DB0C2

Key	Value
FileSize	229384
MD5	E541A987CA0B8921F39C94E0BBD200BB
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	13~preview2-3
SHA-1	5AC733EB15CB00352D70F183F8CAFA57C3E39B8D
SHA-256	E257AE8CF018B5555FFFA884EA126F04CE2522DD4BC06677BF0ECA53669A34FA

Key	Value
FileSize	229384
MD5	61B02032406499E2E9E9A2EFAA716B9E
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	13~preview2-3
SHA-1	160FD521CA19C287ADFE4F5924F3258DD6C9FC8D
SHA-256	5933705B873219C75369DC9BC37D0E4AB77BCC754F523AB07D9FE0FC3C5A8BB8

Key	Value
FileSize	66784
MD5	E29EBC0631C6A5F7FD0891CFD2085FED
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	16A81A95E6DDA7B89D13C63C1E50D916E87196AE
SHA-256	D953406A861EE5F34E437D53B26D09DE915512285424A91B10B158BC182D7A6E

Key	Value
FileSize	229388
MD5	87383CEEB8A47E7663FA78EE40F8A058
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	13~preview2-3
SHA-1	292DFD6810EC042D001369DD511E3C44C614E4C6
SHA-256	5037A7E9EA7AFDDE5EEF0C1B5E66909DD6E0AE34F64FCF1CAC8CE9302BD13367

Key	Value
FileSize	229388
MD5	DB305F2D5A71732D86594EE3BFCCCBA5
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	13~preview2-3
SHA-1	36E97D2F2A031D8D3703435A61A653D077DEDB68
SHA-256	1C33F6AF40EF0132AA84242DD1DFF19B582C7C1E66DB282BF55D32692A73CF3E

Key	Value
FileSize	65700
MD5	BD854DADA7144A3CFFE06096C1FFB089
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	3A97D0645DB4D6984A23B34C23B4E721CA2DDE79
SHA-256	54A0B7FCF8E8DE72B83FCFA9A86CD569917A1CC90E97FEF1470E94942F0E1E51

Key	Value
FileSize	680296
MD5	2E42E97E99148ABAFFEB347CC2B4F4EC
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	13~preview2-3
SHA-1	455DDA5110F27E04EA2410A261C0980E838BB64E
SHA-256	00F10F9C1788EFDB66911FBFD7637C83CA2A67BBD66B521C42564B5F069501AB

Key	Value
FileSize	532864
MD5	006583C4375BED068B9EC71FB59D35E3
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	13~preview2-3
SHA-1	9FFBEC3661595D5DB74BE253680D12F010E914C9
SHA-256	F6600FCD27D8E8D44AE772D7CA691F706BA84DB50B0CEF23DE9A55BF3F41E499

Key	Value
FileSize	71784
MD5	05A66906CAD25F8E234DAA512AEE1B8B
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	AB87F9CF5CCB5E56D73378CB4FFD4BCB60EF335D
SHA-256	5EA334BEBD2A42E7F9A81943B9703E14FE607ABFEC45CD5BA1E05D71AFE9ABA6

Key	Value
FileSize	527092
MD5	669C3C9093C596394C66215F0B23D8AD
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	13~preview2-3
SHA-1	C5A191874558B0D734AF2BD56D67A8A2A89A3148
SHA-256	09F0209B48E9A35E071A86E9794460E33403199864668047A13D9C9C3A4272B2

Key	Value
FileSize	588888
MD5	853CE1FB3DBF4689FE1D65E749173BE6
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	13~preview2-3
SHA-1	7D96C65F406D13AC3AEF4CAFB9E5AEC8F5391A9E
SHA-256	502483D4DB6ABD4C399B4FDE021BCF057B49D8B48A8AA4C2C244B0087EABAF43

Key	Value
FileSize	70980
MD5	1D031D6AF3EE9FDCF8B63E42BCD669C8
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	11C9257A8D4963D2B611B632DD6CC86BDFAC4594
SHA-256	D1C2A2A200A700A6C0BA3CD1627B83A419F60B5659E990ECBDB549DB832347AF

Key	Value
FileSize	65176
MD5	57E50E656D86B9BB77C8D72B747788B4
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - tool 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 boringssl command line tool.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-boringssl
PackageSection	utils
PackageVersion	13~preview2-3
SHA-1	221E119930399689E35B712FF11054EEA6C9200E
SHA-256	D656675E518221CEC323726037EFF8D575000977FEC676711829ADA714203792