android-platform-external-boringssl 14.0.0+r11-4build1 source package in Ubuntu

Changelog

android-platform-external-boringssl (14.0.0+r11-4build1) noble; urgency=high

  * No change rebuild against frame pointers and time_t.

 -- Julian Andres Klode <email address hidden>  Mon, 22 Apr 2024 16:42:36 +0200

Upload details

Uploaded by:
Julian Andres Klode
Uploaded to:
Noble
Original maintainer:
Ubuntu Developers
Architectures:
armel armhf arm64 amd64 i386 ppc64el mipsel mips64el alpha arc hurd-amd64 hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 loong64 riscv64 sh4 x32
Section:
misc
Urgency:
Very Urgent

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc

Downloads

File Size SHA-256 Checksum
android-platform-external-boringssl_14.0.0+r11.orig.tar.xz 30.3 MiB 9d4851f48b1178596fec3b4f8a1394020ee1d64e713853ae42dd60ca5abb080b
android-platform-external-boringssl_14.0.0+r11-4build1.debian.tar.xz 26.8 KiB c4d0b7bbf9ad02648892b5ffe905c15ed8231bfb11be981ae69914db910175cf
android-platform-external-boringssl_14.0.0+r11-4build1.dsc 4.1 KiB b03dc1121fd9ed3744227e746194977b4e734575a58dfc46b7a01aa20744b4bf

View changes file

Binary packages built by this source

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

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