Bug#795645: libbotan-1.10-0: library transition needed now that GCC 5 is the default

2015-08-16 Thread Ondřej Surý
Now that I am on my computer instead of the phone with unfixed security
errors (just a random rant on Android security), I can add a previous
bug number: #790987

Cheers,
Ondrej

On Sun, Aug 16, 2015, at 08:10, Ondřej Surý wrote:
 Hi Scott, 
 
 as far as I know I already prepared the transition and reassigned it to
 release.d.o. Is this something new or just an oversight? 
 
 Ondřej 
 
 On August 16, 2015 12:52:36 AM GMT+02:00, Scott Kitterman
 deb...@kitterman.com wrote:
 Package: libbotan-1.10-0
 Version: 1.10.8-2
 Severity: important
 
 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 (note: this is the standard libstdc++6 bug template with
 some updates/additions):
 
  - 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.
 https://people.debian.org/~doko/logs/gcc5-20150701/botan1.10_1.10.8-2_unstable_gcc5.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
cont...@bugs.debian.org:

  user release.debian@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
 
 Additional information:
 
 A transition is needed.  Ovito will FTBFS unless both botan1.10 and
 qscintilla2 are updated (I discovered this preparing the qscintilla2
 transition).
 
 -- 
 Ondřej Surý


-- 
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server



Bug#795645: libbotan-1.10-0: library transition needed now that GCC 5 is the default

2015-08-16 Thread Ondřej Surý
Hi Scott, 

as far as I know I already prepared the transition and reassigned it to 
release.d.o. Is this something new or just an oversight? 

Ondřej 

On August 16, 2015 12:52:36 AM GMT+02:00, Scott Kitterman 
deb...@kitterman.com wrote:
Package: libbotan-1.10-0
Version: 1.10.8-2
Severity: important

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 (note: this is the standard libstdc++6 bug template with
some updates/additions):

 - 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.
https://people.debian.org/~doko/logs/gcc5-20150701/botan1.10_1.10.8-2_unstable_gcc5.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
   cont...@bugs.debian.org:
   
 user release.debian@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

Additional information:

A transition is needed.  Ovito will FTBFS unless both botan1.10 and
qscintilla2 are updated (I discovered this preparing the qscintilla2
transition).

-- 
Ondřej Surý



Bug#795645: libbotan-1.10-0: library transition needed now that GCC 5 is the default

2015-08-16 Thread Scott Kitterman
Then I just missed it.  I'll close this when I'm not on my phone.

Sorry for the confusion.

Scott K

On August 16, 2015 4:39:46 AM EDT, Ondřej Surý ond...@sury.org wrote:
Now that I am on my computer instead of the phone with unfixed security
errors (just a random rant on Android security), I can add a previous
bug number: #790987

Cheers,
Ondrej

On Sun, Aug 16, 2015, at 08:10, Ondřej Surý wrote:
 Hi Scott, 
 
 as far as I know I already prepared the transition and reassigned it
to
 release.d.o. Is this something new or just an oversight? 
 
 Ondřej 
 
 On August 16, 2015 12:52:36 AM GMT+02:00, Scott Kitterman
 deb...@kitterman.com wrote:
 Package: libbotan-1.10-0
 Version: 1.10.8-2
 Severity: important
 
 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 (note: this is the standard libstdc++6 bug template
with
 some updates/additions):
 
  - 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.

https://people.debian.org/~doko/logs/gcc5-20150701/botan1.10_1.10.8-2_unstable_gcc5.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
cont...@bugs.debian.org:

  user release.debian@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
 
 Additional information:
 
 A transition is needed.  Ovito will FTBFS unless both botan1.10 and
 qscintilla2 are updated (I discovered this preparing the qscintilla2
 transition).
 
 -- 
 Ondřej Surý


-- 
Ondřej Surý ond...@sury.org
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server


Bug#795645: libbotan-1.10-0: library transition needed now that GCC 5 is the default

2015-08-15 Thread Scott Kitterman
Package: libbotan-1.10-0
Version: 1.10.8-2
Severity: important

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 (note: this is the standard libstdc++6 bug template with
some updates/additions):

 - 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.
   
https://people.debian.org/~doko/logs/gcc5-20150701/botan1.10_1.10.8-2_unstable_gcc5.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
   cont...@bugs.debian.org:
   
 user release.debian@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

Additional information:

A transition is needed.  Ovito will FTBFS unless both botan1.10 and
qscintilla2 are updated (I discovered this preparing the qscintilla2
transition).