Parents (Total: 30)

The searched file hash is included in 30 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	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	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	229524
MD5	0CC63A7025E886B11A87F4A5DB8D59FB
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-5
SHA-1	163FDA67838EB122B321A070F2CF00694934601D
SHA-256	1752C0442FE3479AFDC3FDF8DBFAF8C8CB68819DC6A6D7D4C3C3D96328A3489B

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	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

Key	Value
FileSize	535720
MD5	BF17346E9072D1A79C6480F58C470CCC
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-5
SHA-1	236240BBEDDA7B6CC599DEA4753EFF3B5B26E266
SHA-256	7E1B04C861C0F023561A92D1FCB9A6DC01D4436E3D5968AEE9CACF8F9038EC23

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	589904
MD5	5B1287381596E88A1F2076717636505B
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-5
SHA-1	2CFB6D89708A5370EE4F3EF4D69C7ED8AB73B4F7
SHA-256	DE593B141E80816DF357B842A8841F82D73148AC86A434399ADC49B3D60FDEBE

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