[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#797618: marked as done (transition: opencolorio)

Your message dated Mon, 7 Sep 2015 14:13:56 +0200
with message-id <20150907121356.GA25387@betterave.cristau.org>
and subject line Re: Bug#796925: opencolorio: library transition needed with GCC 5 as default
has caused the Debian Bug report #796925,
regarding transition: opencolorio
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 owner@bugs.debian.org
immediately.)


-- 
796925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796925
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: opencolorio
Version: 1.0.9~dfsg0-3
Severity: serious
Justification: breaks reverse-dependencies
Tags: patch

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 opencolorio, std::string appears in header files that
get installed, so it seems very likely that a transition is needed.
The transition consists of renaming the library package, adding a
v5 suffix. A patch is available in Ubuntu,
<http://patches.ubuntu.com/o/opencolorio/opencolorio_1.0.9~dfsg0-3ubuntu2.patch>.

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.

In the case of opencolorio:

* there is a circular build-dep with openimageio which will need some
  care (Ubuntu temporarily disabled openimageio support in opencolorio,
  which seems a reasonable solution)
* boost, opencv, openexr already started their transitions
* Qt does not need a rename
* I think the rest are C and so do not need renames

so I think these two packages are ready to go.

The package is likely to be NMU'd in the near future if there is no
maintainer response, with a patch very similar to the one in Ubuntu. 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.

    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 Tue, Aug 25, 2015 at 22:29:06 +0200, Julien Cristau wrote:

> Source: opencolorio
> Version: 1.0.9~dfsg0-3
> Severity: serious
> Tags: sid stretch
> User: debian-gcc@lists.debian.org
> Usertags: libstdc++-cxx11
> 
libopencolorio1 is no longer in testing, closing.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: