android-platform-external-boringssl 13.0.0+r24-1 source package in Ubuntu

Changelog

android-platform-external-boringssl (13.0.0+r24-1) unstable; urgency=medium

  [ Debian Janitor ]
  * Use correct machine-readable copyright file URI.
  * Bump debhelper from old 12 to 13.
  * Update standards version to 4.6.1, no changes needed.

  [ Roger Shimizu ]
  * New upstream release 13.0.0+r24
  * debian/*.lintian-overrides: Update to make more accurate.
  * debian/copyright:
    - Remove non-existing entries.
    - Fix typo.

 -- Roger Shimizu <email address hidden>  Mon, 16 Jan 2023 02:04:16 -0800

Upload details

Uploaded by:
Android tools Maintainer
Uploaded to:
Sid
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 Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
android-platform-external-boringssl_13.0.0+r24-1.dsc 3.9 KiB 74a2088517fa5cede9dc085e99589ce7e3b1bdd516198a479991c99dfc4db198
android-platform-external-boringssl_13.0.0+r24.orig.tar.xz 28.1 MiB 583b7aeee1fca68b8244d086cea6fca23bd19d517bd63f0b9de714e048f92a7d
android-platform-external-boringssl_13.0.0+r24-1.debian.tar.xz 15.8 KiB ea59ea1fde96b997f3bc6c1cda3da000ec52071684f8e62592783868fa1bc4ff

Available diffs

No changes file available.

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.