android-platform-external-boringssl 8.1.0+r23-3 source package in Ubuntu

Changelog

android-platform-external-boringssl (8.1.0+r23-3) unstable; urgency=medium

  [ Kai-Chung Yan (殷啟聰) ]
  * d/copyright: Refer to the Apache-2.0 in the commons-licenses

  [ Roger Shimizu ]
  * d/watch: Update rule to get new upstream version

  [ Hans-Christoph Steiner ]
  * fix adb crashes on startup on armhf (Closes: #933865)

 -- Hans-Christoph Steiner <email address hidden>  Thu, 08 Oct 2020 19:35:08 +0200

Upload details

Uploaded by:
Android tools Maintainer
Uploaded to:
Sid
Original maintainer:
Android tools Maintainer
Architectures:
armel armhf arm64 amd64 i386 ppc64el
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Groovy release universe misc

Downloads

File Size SHA-256 Checksum
android-platform-external-boringssl_8.1.0+r23-3.dsc 2.0 KiB 4d53419d2e392eab0a7fe9774326da822c7dfe723b6239008737a886f93897ed
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz 19.4 MiB 51eb22c5f68ce49e35a1726623a257e8e89b29c23bf374a3420a8ac88afe2078
android-platform-external-boringssl_8.1.0+r23-3.debian.tar.xz 8.3 KiB ff5d57d6d8286b5b20265eefd7faf56c7b025fcbaaf7fda9ea6e3f6ee0cfbacb

No changes file available.

Binary packages built by this source

android-libboringssl: 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.

android-libboringssl-dbgsym: debug symbols for android-libboringssl
android-libboringssl-dev: 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.