Your message dated Wed, 2 Sep 2015 19:40:24 +0100
with message-id <55e74298.5090...@debian.org>
and subject line Re: [Debichem-devel] Bug#797743: gromacs: ABI transition
needed for libstdc++ v5
has caused the Debian Bug report #797743,
regarding gromacs: 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.)
--
797743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gromacs
Version: 5.0.6-1
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 gromacs, std::string appears in installed headers,
so it seems very likely that a transition is needed.
The transition normally consists of renaming the affected library packages,
adding a v5 suffix (.4v5, etc.). The SONAME should not be changed.
However, gromacs already does not package its shared library according to
Policy ยง8.1, so it will likely also need a versioned Breaks on
versions of votca-csg that do not depend on a separated shared library.
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 gromacs:
* boost started its transition with 1.58
* everything else looks like a C ABI
so I think this is ready to go.
The package is likely to 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 ---
On 02/09/15 19:03, Nicholas Breen wrote:
> On Wed, Sep 02, 2015 at 09:09:25AM +0100, Simon McVittie wrote:
>> In the case of gromacs, std::string appears in installed headers,
>> so it seems very likely that a transition is needed.
>
> Isn't this just #791061 again?
You're right, there was already a bug (but for whatever reason, it
didn't end up on the Titanpad where the release team are tracking this
stuff).
> To the best of my knowledge, nothing external uses those.
They looked like they were intended to be public API to me, but you know
this code better than I do (I'd never seen it before this morning).
Closing, then. If you later discover that there should have been a
transition after all, you can do one at that point; it's not as if there
are many rdeps.
Sorry for the noise,
S
--- End Message ---
