Debian Bug report logs - #790978
android-platform-build: library transition may be needed when GCC 5 is the default

Toggle useless messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: maintonly@bugs.debian.org

Subject: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Fri, 03 Jul 2015 13:08:51 +0000

Package: src:android-platform-build
Version: 21-4
Severity: important
Tags: sid stretch
User: debian-gcc@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
     https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   control@bugs.debian.org:
   
     user release.debian.org@packages.debian.org
     usertag <this issue> + transition
     block <this issue> by 790756
     reassign <this issue> release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition

Message #10 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Matthias Klose <doko@debian.org>, 790978@bugs.debian.org

Subject: Re: Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Tue, 11 Aug 2015 08:49:16 +0200

[Message part 1 (text/plain, inline)]

Control: severity -1 serious
Control: tag -1 confirmed

On Fri, Jul  3, 2015 at 13:08:51 +0000, Matthias Klose wrote:

>  - Rebuild the library using g++/g++-5 from experimental. Note that
>    most likely all C++ libraries within the build dependencies need
>    a rebuild too. You can find the log for a rebuild in
>      https://people.debian.org/~doko/logs/gcc5-20150701/
>    Search for "BEGIN GCC CXX11" in the log.
> 
>  - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
>    library API, and are used by the reverse dependencies of the
>    library.
> 
This function changes with the new libstdc++:

std::string pseudolocalize_string(const std::string& source);

android-libhost thus needs to be renamed.

(incidentally, the headers mention
std::string parent_dir(const std::string& path);
but the library doesn't seem to export that symbol)

Cheers,
Julien

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Julien Cristau <jcristau@debian.org>, 790978@bugs.debian.org

Subject: Re: Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Wed, 19 Aug 2015 08:01:55 +0100

On Tue, 11 Aug 2015 at 08:49:16 +0200, Julien Cristau wrote:
> This function changes with the new libstdc++:
> 
> std::string pseudolocalize_string(const std::string& source);
> 
> android-libhost thus needs to be renamed.

android-libhost is a semi-private library not in the default linker path,
and doesn't have a proper SONAME (Android doesn't really do ABI, the
upstream assumption is that you rebuild the entire OS image every time).
My understanding is that it is not meant to be renamed for any other
incompatible change either.

As such, maybe a sourceful upload of android-platform-build with
versioned Breaks on the only rdep (aapt), followed by a binNMU of
aapt's source package android-platform-frameworks-base, would be more
appropriate?

Longer term, stuff from upstream Android with no real ABI should probably
be a single source package (perhaps using dpkg-source 3.0 (quilt)'s support
for multiple orig tarballs) so that it can be rebuilt as a unit, and have
lockstep dependencies.

    S

Message #24 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Hans-Christoph Steiner <hans@eds.org>

To: Simon McVittie <smcv@debian.org>, 790978@bugs.debian.org, Julien Cristau <jcristau@debian.org>

Subject: Re: [Android-tools-devel] Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Wed, 19 Aug 2015 11:40:14 +0200

[Message part 1 (text/plain, inline)]

This should be addressed once we update all of the android-platform-* source
packages to the latest version from Google (5.1.1+r8).

Simon is right in that these are basically private libraries.  Upstream
statically links them into each executable.  That didn't seem very Debian-ish,
so instead I structured it as private shared libraries.  Nothing should link
to these android-lib* shared libraries that is not part of the Android source.

A single source package might make some things easier, but it would be about
8-12 gigs in size. That would make it very difficult for many people to work
with that source package.

.hc

[signature.asc (application/pgp-signature, attachment)]

Message #29 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Hans-Christoph Steiner <hans@eds.org>, 790978@bugs.debian.org, Julien Cristau <jcristau@debian.org>

Subject: Re: Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Wed, 19 Aug 2015 10:51:21 +0100

On 19/08/15 10:40, Hans-Christoph Steiner wrote:
> Simon is right in that these are basically private libraries.  Upstream
> statically links them into each executable.  That didn't seem very Debian-ish,
> so instead I structured it as private shared libraries.  Nothing should link
> to these android-lib* shared libraries that is not part of the Android source.

To be honest that sounds to me like a job for static libraries and
Built-Using. If shared libraries with a stable ABI are not feasible,
static libraries are probably a better fallback position; shared
libraries with an unpredictable ABI seem like the worst of both worlds.

    S

Message #34 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Hans-Christoph Steiner <hans@eds.org>

To: Simon McVittie <smcv@debian.org>, 790978@bugs.debian.org, Julien Cristau <jcristau@debian.org>

Subject: Re: Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Wed, 19 Aug 2015 13:14:18 +0200

[Message part 1 (text/plain, inline)]

All of the android-* packages must be updated to the latest version at the
same time.  It is more unpredictable to have android-* packages at different
upstream versions since no one is running that configuration, and upstream
does not do anything to support that (e.g. no versioned ABI, etc).  Therefore,
the ABI is guaranteed to be compatible since they'll all be built together.

In practice, this means that the process of updating to the latest upstream
version has to start from the most core packages, then progress to the ones
that depend on it.

That said, this private shared library arrangement allows for security patches
in the android shared code to be applied without having to rebuild everything.

[signature.asc (application/pgp-signature, attachment)]

Message #39 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Hans-Christoph Steiner <hans@eds.org>

Cc: Simon McVittie <smcv@debian.org>, 790978@bugs.debian.org

Subject: Re: Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Wed, 19 Aug 2015 23:23:21 +0200

[Message part 1 (text/plain, inline)]

On Wed, Aug 19, 2015 at 13:14:18 +0200, Hans-Christoph Steiner wrote:

> All of the android-* packages must be updated to the latest version at the
> same time.  It is more unpredictable to have android-* packages at different
> upstream versions since no one is running that configuration, and upstream
> does not do anything to support that (e.g. no versioned ABI, etc).  Therefore,
> the ABI is guaranteed to be compatible since they'll all be built together.
> 
> In practice, this means that the process of updating to the latest upstream
> version has to start from the most core packages, then progress to the ones
> that depend on it.
> 
> That said, this private shared library arrangement allows for security patches
> in the android shared code to be applied without having to rebuild everything.
> 
It does require that you version your dependencies appropriately,
though, so that a non-working combination is not installable.

Cheers,
Julien

[signature.asc (application/pgp-signature, inline)]

Message #44 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Emilio Pozuelo Monfort <pochu@debian.org>

To: 790978@bugs.debian.org

Subject: Re: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Fri, 30 Oct 2015 15:51:28 +0100

This is friendly ping wrt the libstdc++ ABI transition. Your package is listed
as needing a transition but has seen no action. It'd be good to get things going
so we can finish the transition soon.

Cheers,
Emilio

Message #51 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Hans-Christoph Steiner <hans@at.or.at>

To: Emilio Pozuelo Monfort <pochu@debian.org>, 790978@bugs.debian.org

Subject: Re: [Android-tools-devel] Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

Date: Tue, 17 Nov 2015 10:11:54 +0100

We are in the process of updating all of the android-platform-* packages.  It
is a large, complex suite so it takes time.  If you need to force the
transition, just go ahead and ignore this package.  The update is more or less
done, we are currently just wanting on this dependency in a different library
that we do not maintain:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793863

Message #60 received at 790978@bugs.debian.org (full text, mbox, reply):

From: Tobias Frost <tobi@debian.org>

To: 790978@bugs.debian.org

Subject: android-platform-build: diff for NMU version 21-4.1

Date: Fri, 08 Jan 2016 20:17:50 +0100

Control: tags 790978 + patch

Dear maintainer,

I've prepared an NMU for android-platform-build (versioned as 21-4.1). The diff
is attached to this message.

Regards.
diff -Nru android-platform-build-21/debian/changelog android-platform-build-21/debian/changelog
--- android-platform-build-21/debian/changelog	2014-11-25 13:02:07.000000000 +0100
+++ android-platform-build-21/debian/changelog	2016-01-08 20:16:32.000000000 +0100
@@ -1,3 +1,11 @@
+android-platform-build (21-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuilt for GCC-5 Transistion (Closes: #790978), adding
+    a break against current aapt as suggested in the BTS.
+
+ -- Tobias Frost <tobi@debian.org>  Fri, 08 Jan 2016 20:16:32 +0100
+
 android-platform-build (21-4) unstable; urgency=low
 
   * include Breaks: and Replaces: to allow for proper upgrading
diff -Nru android-platform-build-21/debian/control android-platform-build-21/debian/control
--- android-platform-build-21/debian/control	2014-11-25 12:51:32.000000000 +0100
+++ android-platform-build-21/debian/control	2016-01-08 20:15:41.000000000 +0100
@@ -44,6 +44,7 @@
 Section: libs
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
+Breaks: aapt (<= 21-2)
 Description: Android utility library for cross-platform tools
  Library providing utility functions to Android related tools. This is needed
  purely to get various Android utilities working.

Message #67 received at 790978-close@bugs.debian.org (full text, mbox, reply):

From: Tobias Frost <tobi@debian.org>

To: 790978-close@bugs.debian.org

Subject: Bug#790978: fixed in android-platform-build 21-4.1

Date: Fri, 08 Jan 2016 19:33:45 +0000

Source: android-platform-build
Source-Version: 21-4.1

We believe that the bug you reported is fixed in the latest version of
android-platform-build, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 790978@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost <tobi@debian.org> (supplier of updated android-platform-build package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 08 Jan 2016 20:16:32 +0100
Source: android-platform-build
Binary: zipalign android-libhost android-libhost-dev
Architecture: source amd64
Version: 21-4.1
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer <android-tools-devel@lists.alioth.debian.org>
Changed-By: Tobias Frost <tobi@debian.org>
Description:
 android-libhost - Android utility library for cross-platform tools
 android-libhost-dev - Android utility library for cross-platform tools - headers
 zipalign   - Align zip/jar/apk along byte boundaries
Closes: 790978
Changes:
 android-platform-build (21-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuilt for GCC-5 Transistion (Closes: #790978), adding
     a break against current aapt as suggested in the BTS.
Checksums-Sha1:
 e458e768bda8895d5e62fdbe5876032dc6b4fa8a 2275 android-platform-build_21-4.1.dsc
 c9774a29d9d231ffc819917acafdbd17a5e1f776 9464 android-platform-build_21-4.1.debian.tar.xz
Checksums-Sha256:
 f5c5ee24d72841e4a1945d27220d1145e54ef8ca569e619b3951cb8952665a8a 2275 android-platform-build_21-4.1.dsc
 1052c661af654ad000ff210a474e9769e4c6432f46e450fb24124e276145f12f 9464 android-platform-build_21-4.1.debian.tar.xz
Files:
 ab95e1089d3e442f610133cd4ff3a685 2275 devel extra android-platform-build_21-4.1.dsc
 b62c486de2b436574136359342c8ac3f 9464 devel extra android-platform-build_21-4.1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWkAuVAAoJEJFk+h0XvV02F1IQALg3GWM1hE6vBf711oOqRXAB
te+daGgGA0UribJCsxngl+i4+gEKiTP+141LrOtNJYzoVa5JFYrcJjb5psf1COdb
Aa4BNuj4y4j5kcJVsrl66/c/QDkKKEth5WysBVflSlMhSXlUxHLIWEV4ArLP6u/E
ynehmG2m/TzuHZhWGKssR5wqCxjuFZ5Cmf5WH3vo/CxdiUWMCJQnC0vYlYX229zp
cek5wdfgQE2k80zWEmKN8l28Nyd2dh8Dc7A2sho5YNdEsX1Y79djCFe4Si+l40TP
VwG9WwYQMseMsZEE+UAuqTwlwveAs6yLO7+JNAbCpTJr5YP1zpCh7tAloJfKhksJ
nGfUTfmKqQdhknNYb+utQi7JOOEUA8lKbGpPWdjZieafu961dmmD8+ntlqMKlzEB
TZ+0mKt7cVJ1W2qUTLzL4pfdZv1nauYwPP6Bq0Aw13C0lOaFoeqOzUUewnzAPSod
HQqYAGcWS9bYCk5h9RmcnZ1t0D+VdU37V67K6SCG6MDxx0xtSl+EbA4c+LOCuS1R
Mw8m2mdrtKhz0Em3rzmo8egpymrA6h5kj3saH5zCeLZ1Av++yQQPAIKmxPulugQY
Jq+PmpMmzyD8cWqfPddVUrTNShtQ4w8OWT6T3IpmdJ7wYwGAAI9wSh3stbTAVFPA
I3qTJ+2yKlUc0BCuYpB3
=KdY1
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.