Debian Bug report logs - #791117
libecap: 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: libecap: library transition may be needed when GCC 5 is the default

Date: Fri, 03 Jul 2015 13:11:20 +0000

Package: src:libecap
Version: 1.0.0-1
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 #12 received at 791117-maintonly@bugs.debian.org (full text, mbox, reply):

From: Luigi Gangitano <luigi@debian.org>

To: Matthias Klose <doko@debian.org>, 791117-maintonly@bugs.debian.org

Cc: pkg-squid-devel@lists.alioth.debian.org

Subject: Re: Bug#791117: libecap: library transition may be needed when GCC 5 is the default

Date: Wed, 5 Aug 2015 20:52:31 +0200

Since libecap3 1.0.1 has been in the archive for just a couple of weeks and its only reverse dependency (squid 3.5.6) has not transitioned to testing yet, we don’t plan to change SONAME or package name and just rebuild the package with GCC5.

A new squid package will be uploaded just afterwards and both package will transition at the same time to testing.

--
Luigi Gangitano -- <luigi@debian.org> -- <gangitano@lugroma3.org>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26
GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5  0F6D 0284 F20C 2BA9 7CED

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

From: Matthias Klose <doko@debian.org>

To: Luigi Gangitano <luigi@debian.org>, 791117-maintonly@bugs.debian.org

Cc: pkg-squid-devel@lists.alioth.debian.org

Subject: Re: Bug#791117: libecap: library transition may be needed when GCC 5 is the default

Date: Wed, 05 Aug 2015 21:02:31 +0200

On 08/05/2015 08:52 PM, Luigi Gangitano wrote:
> Since libecap3 1.0.1 has been in the archive for just a couple of weeks and its only reverse dependency (squid 3.5.6) has not transitioned to testing yet, we don’t plan to change SONAME or package name and just rebuild the package with GCC5.
> 
> A new squid package will be uploaded just afterwards and both package will transition at the same time to testing.

then please request a binNMU, or do a new upload soonish

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

From: Luigi Gangitano <luigi@debian.org>

To: Matthias Klose <doko@debian.org>

Cc: 791117-maintonly@bugs.debian.org, pkg-squid-devel@lists.alioth.debian.org

Subject: Re: Bug#791117: libecap: library transition may be needed when GCC 5 is the default

Date: Wed, 5 Aug 2015 21:07:14 +0200

> Il giorno 05/ago/2015, alle ore 21:02, Matthias Klose <doko@debian.org> ha scritto:
> 
> On 08/05/2015 08:52 PM, Luigi Gangitano wrote:
>> Since libecap3 1.0.1 has been in the archive for just a couple of weeks and its only reverse dependency (squid 3.5.6) has not transitioned to testing yet, we don’t plan to change SONAME or package name and just rebuild the package with GCC5.
>> 
>> A new squid package will be uploaded just afterwards and both package will transition at the same time to testing.
> 
> then please request a binNMU, or do a new upload soonish

The package is ready, will upload in a couple of hours. I’m testing transition scenarios for both libecap3 and squid.

Regards,

L

--
Luigi Gangitano -- <luigi@debian.org> -- <gangitano@lugroma3.org>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26
GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5  0F6D 0284 F20C 2BA9 7CED

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

From: Luigi Gangitano <luigi@debian.org>

To: 791117-close@bugs.debian.org

Subject: Bug#791117: fixed in libecap 1.0.1-2

Date: Wed, 05 Aug 2015 21:35:27 +0000

Source: libecap
Source-Version: 1.0.1-2

We believe that the bug you reported is fixed in the latest version of
libecap, 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 791117@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luigi Gangitano <luigi@debian.org> (supplier of updated libecap 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: SHA512

Format: 1.8
Date: Wed, 05 Aug 2015 23:00:33 +0200
Source: libecap
Binary: libecap3-dev libecap3
Architecture: source amd64
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Luigi Gangitano <luigi@debian.org>
Changed-By: Luigi Gangitano <luigi@debian.org>
Description:
 libecap3   - eCAP library
 libecap3-dev - eCAP development libraries
Closes: 791117
Changes:
 libecap (1.0.1-2) unstable; urgency=medium
 .
   * debian/control
     - Rebuilt for GCC5.0 transition (Closes: #791117)
Checksums-Sha1:
 014f4cdc43b73120b1b983c0a10e8c48cf7b1e60 1773 libecap_1.0.1-2.dsc
 f0326b6452a1353d36ce1225bd5e549a6d5ca8a1 3088 libecap_1.0.1-2.debian.tar.xz
 f20c915230e2273b23144498ccdb79a1ff97b68f 30238 libecap3-dev_1.0.1-2_amd64.deb
 5e23f39590573fb9418baaba93bdf99a80388d81 20306 libecap3_1.0.1-2_amd64.deb
Checksums-Sha256:
 13c0886609621d266a8c9d52892e8f134f4cf65dd9ea48ea1ccb07890fd99a62 1773 libecap_1.0.1-2.dsc
 d29b3c570c14d35ac80c8245b4f05cc3e62c98374b4119932f488e8940d0c3ea 3088 libecap_1.0.1-2.debian.tar.xz
 4ad64dcdf065e8605b8694b74d3853b45ea605018b75ce403da0da4d542abd9f 30238 libecap3-dev_1.0.1-2_amd64.deb
 bea493a1cb5f36a9d0a783b740cb50365173bcf4ac5a4ae6d027dd7fac10c3a9 20306 libecap3_1.0.1-2_amd64.deb
Files:
 ab220207232ae80df8d7781a6b9807b1 1773 libs extra libecap_1.0.1-2.dsc
 264479392f7a267116dd39d5a436964e 3088 libs extra libecap_1.0.1-2.debian.tar.xz
 5795a3510bda018b8f9a7a75528b95f7 30238 libdevel extra libecap3-dev_1.0.1-2_amd64.deb
 1d02f202996441c02f4a2cffedf086da 20306 libs extra libecap3_1.0.1-2_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVwnrmAAoJEAKE8gwrqXztRSwQAIJ2GpzHEvJFrIz4hHpGqyz5
WZHmNmCSmoyiFt/0Q8D46R/JozZs/3R7kenZZ7nDpwsI5znxh8RNXt+a0cRD9aQf
DoEHD8dCwwaKamSdZG9W5yQQHGBSXJcqdXNcoac2jUrKKpgUgTYIA1oaHWyYfcxJ
yV40u4wti1UY8+MYCFFCxFS8BNjmqMPLL8N/S0U1foMOsbCrD6QWfn9s0GUAjddy
2hN0sDaAwQcZAFISuaIoLg32b4TDbccGkoqmXZZ2tFf8UHLNBo8OgnE3ePY+n0Tc
PhP86mFtW7z5UkJ8OqP5MH+sLXjs3YcA5LMgKho5XquzpUH0VeEvDtq5gQ90Go6z
v22A8ouG2wvNAtYDWu8ZLF/LoDCSw3EXstNaTvAOi0quVWsKYuFosysFk5X31OSU
HWYWRVSmNqZKpaM2gkndo9A8TevJxUo7/7n9mPGx5NjG5RdFCtu6frnHWVG0tI5D
8qkTgdXy5T7ERqLBYUHfuuBRRDIO8VHK+w7T9cNV6pQSlgBxsRqS49oz9gazPJFV
llG28DJzVPBrfSAvqIWF1OKm9M1GL+T+7U+WVoIz6AoowlZwT+KKtl2vk04c0yPe
UYIj2deSCIvV7PLR15k3LOSGM/1W3w7DyNDVFkdoBfSihobZnglcrtUubupd5F72
GTXjXxkUs9XkGRIRCq8R
=hSfl
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.