android-platform-external-boringssl 13.0.0+r11-1ubuntu1 source package in Ubuntu
Changelog
android-platform-external-boringssl (13.0.0+r11-1ubuntu1) lunar; urgency=low * Merge from Debian unstable. Remaining changes: - Make sure to export the binaries in a known dwarf format, to avoid failures in dh_dwz and dh_strip with llvm-14 android-platform-external-boringssl (13.0.0+r11-1) unstable; urgency=medium * New upstream release 13.0.0+r11 * debian/patches: Remove backport patch. * debian/copyright: Update file list. * debian/sources.mk: Update by script. * debian/control: Add myself as uploader. -- Gianfranco Costamagna <email address hidden> Sat, 05 Nov 2022 15:52:21 +0100
Upload details
- Uploaded by:
- Gianfranco Costamagna
- Uploaded to:
- Lunar
- Original maintainer:
- Android tools Maintainer
- Architectures:
- armel armhf arm64 amd64 i386 ppc64el mipsel mips64el hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 riscv64 sh4 x32
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
android-platform-external-boringssl_13.0.0+r11.orig.tar.xz | 28.1 MiB | 202dd292e8041f670628fa49fcde164e60f0fec20c7fd0b9b66b1112852a579b |
android-platform-external-boringssl_13.0.0+r11-1ubuntu1.debian.tar.xz | 15.5 KiB | 421cbf210ce9759bfe63084db0f69d085cbd0edb6d4c294aedbe3777c9208886 |
android-platform-external-boringssl_13.0.0+r11-1ubuntu1.dsc | 3.0 KiB | c4e0c531aff6d4f6af906030aacdd5c314713b40a82e6bb1e1608a46884a7eea |
Available diffs
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.