Looks like it's time to stabilize new Boost Arches, please test and mark stable =dev-util/boost-build-1.56.0 =dev-libs/boost-1.56.0-r1 Target keywords: alpha amd64 arm arm64 hppa ia64 ppc ppc64 sparc x86
amd64 stable
x86 stable
I'd appreciate if you could next time have the libreoffice-bin build as a blocker here. It takes a bit of time to do, and if it's not done yet at stabilization time all sorts of dependency hell break loose.
Side note, removing the blocker again since all affected arches have already gone ahead.... :(
Stable for HPPA PPC64.
This has broken stable =media-video/mkvtoolnix-6.6.0. See #554814
Stable on alpha.
ia64 stable
(In reply to Andreas K. Hüttel from comment #3) > I'd appreciate if you could next time have the libreoffice-bin build as a > blocker here. It takes a bit of time to do, and if it's not done yet at > stabilization time all sorts of dependency hell break loose. Have you think in adding a comment above "KEYWORDS" line in boost ebuild to remember that? Otherwise it's likely to be forgotten again in the future when months have passed and this is not remembered :( Thanks :)
ppc stable
arm stable
(In reply to Markus Meier from comment #11) > arm stable How did you get dev-libs/boost-1.56.0-r1 to build on ARM? I get compilation failures saying: libs/atomic/src/lockpool.cpp: In static member function 'static void boost::atomics::detail::lockpool::thread_fence()': libs/atomic/src/lockpool.cpp:127:5: error: 'thread_fence' is not a member of 'boost::atomics::detail' atomics::detail::thread_fence(memory_order_seq_cst); ^ libs/atomic/src/lockpool.cpp: In static member function 'static void boost::atomics::detail::lockpool::signal_fence()': libs/atomic/src/lockpool.cpp:138:5: error: 'signal_fence' is not a member of 'boost::atomics::detail' atomics::detail::signal_fence(memory_order_seq_cst); ^ The problem is detailed here: https://svn.boost.org/trac/boost/ticket/10446
sparc stable
Dear Maintainer (or who is mainly involved in this stable request), This is an auto-generated message that will move the current component to the new component Stabilization. To ensure that the stabilization will proceed correctly, please fill the fields "Atoms to stabilize" and "Runtime testing required" as described here: https://archives.gentoo.org/gentoo-dev/message/4b2ef0e9aa7588224b8ae799c5fe31fa
arm64 stabled -1.62.0-r1 in bug 590244, closing.