Your message dated Sat, 12 Sep 2015 00:00:18 +0000
with message-id <e1zayes-0000wh...@franck.debian.org>
and subject line Bug#797981: fixed in magics++ 2.24.7-7
has caused the Debian Bug report #797981,
regarding magics++: ABI transition needed for libstdc++ v5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
797981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: magics++
Version: 2.24.7-5
Severity: serious
Justification: breaks ABI without a package rename
Tags: sid stretch
User: debian-...@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,
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.

In the case of magigs++, std::string appears in functions that are
explicitly exported, so it seems very likely that a transition is needed.
The transition normally consists of renaming the
affected library packages, adding a v5 suffix (libmagplus3v5).
The SONAME should not be changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. Please avoid doing this unless the new upstream version
is very low-risk.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of magics++:

* hdf5 is a C++ library, but magics++ does not appear to use the C++ part
  libhdf5-cpp-8 so that can perhaps be ignored
* netcdf has already been renamed
* libterralib has already been renamed
* boost has already been renamed via the 1.55 -> 1.58 transition
* Qt does not need renaming

so I think magics++ is ready to start its sub-transition in unstable.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
    S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg00000.html

--- End Message ---
--- Begin Message ---
Source: magics++
Source-Version: 2.24.7-7

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

Debian distribution maintenance software
pp.
Alastair McKinstry <mckins...@debian.org> (supplier of updated magics++ 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 11 Sep 2015 11:52:41 +0100
Source: magics++
Binary: libmagplus3v5 libmagics++-dev magics++ python-magics++ libmagics++-data 
libmagics++-metview-dev
Architecture: source all amd64
Version: 2.24.7-7
Distribution: sid
Urgency: medium
Maintainer: Alastair McKinstry <mckins...@debian.org>
Changed-By: Alastair McKinstry <mckins...@debian.org>
Description:
 libmagics++-data - Data files needed for magics++ library
 libmagics++-dev - Development files for ECMWF  plotting software MAGICS++
 libmagics++-metview-dev - Libraries needed for building MetView
 libmagplus3v5 - ECMWF meteorological plotting software library
 magics++   - Executables for the magics++ library
 python-magics++ - python support for Magics++
Closes: 797981
Changes:
 magics++ (2.24.7-7) unstable; urgency=medium
 .
   * ABI transition needed for libstdc++ v5, to libmagplus3v5.
     Closes: #797981.
   * Add Breaks/Replaces libmagplus3
Checksums-Sha1:
 10b82a06dfa35fd4c34b75eeecc6cef3610ff4f6 2592 magics++_2.24.7-7.dsc
 9ffc61fcf03ef7833eee4cfe047e473c7d037180 15128 magics++_2.24.7-7.debian.tar.xz
 247e8e4ec031b1d4a93994e2cd9389f51e99933f 28116218 
libmagics++-data_2.24.7-7_all.deb
 9bbf76b982d47f5db2b7276d0ad71d4071dd7de9 105138 
libmagics++-dev_2.24.7-7_amd64.deb
 7908f7555ddb61ff4801855406d152d2cfc7fe64 648806 
libmagics++-metview-dev_2.24.7-7_amd64.deb
 e865c5bee01ca854d45a88d4ffebe233eff1885a 2807546 
libmagplus3v5_2.24.7-7_amd64.deb
 da299992c7e90b3dafe550dee3d181f9853ff0e6 58784 magics++_2.24.7-7_amd64.deb
 742e5dc3e18d05627c53a53454959304b50d1cc3 56326 
python-magics++_2.24.7-7_amd64.deb
Checksums-Sha256:
 0e1ea0b7283d7e4dfce90d6a6772daa9a75e98da42b7ebc6fbec7ab99efead51 2592 
magics++_2.24.7-7.dsc
 2cb7f721da9796a6c614ce475bccef59c219c25e291315f31515b5389c5eafc4 15128 
magics++_2.24.7-7.debian.tar.xz
 2ed44aef6079d1a57e7b4d9d2603d71055503c302b2ea1e50567b327b3439fe5 28116218 
libmagics++-data_2.24.7-7_all.deb
 f48ad483208c33728636aa7c35747cfa84f29d64fdbaf3abad5cf38f213541de 105138 
libmagics++-dev_2.24.7-7_amd64.deb
 b1d7d3b5ab006bbc799cfe875bec4c6d9ec6db3e289ad2c93b7c8dd029cf3884 648806 
libmagics++-metview-dev_2.24.7-7_amd64.deb
 f8dfe8a9e001978c63f9d9e6e38e98af480aab9e6dd6e2d4126783c2c23ae7b2 2807546 
libmagplus3v5_2.24.7-7_amd64.deb
 f70340fa2dd8f726dd5092011679649988bdb0bdc972b3227a62f7c00b60e420 58784 
magics++_2.24.7-7_amd64.deb
 41c1ed6b524c92094210346195bc1d78dd8ee0445858212b869829fa7a8d3f34 56326 
python-magics++_2.24.7-7_amd64.deb
Files:
 246a09855c5fde31847668d42d5d4793 2592 science optional magics++_2.24.7-7.dsc
 90d62553151d9d30ef250ed8a23662f5 15128 science optional 
magics++_2.24.7-7.debian.tar.xz
 8d1656348c9147427a5d9bf84a4df684 28116218 science optional 
libmagics++-data_2.24.7-7_all.deb
 0a6f62f463551e7f63ea64c0ce8cd569 105138 libdevel optional 
libmagics++-dev_2.24.7-7_amd64.deb
 9d1ab18bf0eeffb7179b143695abd2f2 648806 libdevel optional 
libmagics++-metview-dev_2.24.7-7_amd64.deb
 4eee6862e193f80b706abf6408f1eb34 2807546 libs optional 
libmagplus3v5_2.24.7-7_amd64.deb
 28892b1d8513e8e766738f5d1a7913f7 58784 science optional 
magics++_2.24.7-7_amd64.deb
 39a352795f4d7b49f2913d4035ca434c 56326 python optional 
python-magics++_2.24.7-7_amd64.deb

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

iQIcBAEBCAAGBQJV8t+tAAoJEMvmu05dmtOlCmkQAIed1fgqkn5LNNnsQhCYgDs/
ly9NLyPGnnHFtRpCuJeNpEBolKgP/7uHDgD/OQDiYO1r/O3u4NObtcY0s5gUt+sr
WlmbKGpVEb4TMot8/CXAPagf0L7PliaTdE8RrVatRPsBi5sdFlC2ArB2USPlxeDA
usmN2C/YXDL3ZuyNUCHphIau+rUorXOBdbfh3pvH8PkQsW89M3enQ537EIqIRUbL
58GO28d3ANL80kcUoKJ5iJTN7TiUEPnE1klXp+1O61qMb7b2pNDxQLUKm/gwa/50
cAJ/gfR3aNPxbLVfwrF14h8LHp2r2jsbZ+Z+Astv51oY/1gt5/TWt2Z0RovdD16L
TK9J0bL53Z/drhZYfST+g9/9gz+0uBf1VF0gRfyPLc8jWQw12+ErFzotw131CPwk
1zeMSmU5apCtSGfzb9d+R2CLfYs5sIgoe44shgyK04uouMPfBo7BocXw8J7/oyjC
zi2lSR4F0A84SMS4OyMP0ddwKp9k1cn+ujMJUdxLGN1inHFKLt/OWfaDxVbIWD/J
zqvnm9wGyGsAfJVSlx70Ub6cIguLj++I46pWHvfzxT5DMDgaHoaIJ1Xh1CgkN6TO
qfp7hs0nKNmvDXTkG5wcnVwkiiQDtj163SFxGHrbntBMNlXMceeTjA082J//fWTx
k+YahhAH9fJ7aX28sw0y
=gBwC
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to