On Mon, Mar 11, 2013 at 05:24:49PM -0500, Amit Kulkarni wrote: > On Mon, Mar 11, 2013 at 4:57 PM, Landry Breuil <[email protected]>wrote: > > > On Thu, Mar 07, 2013 at 06:21:38PM -0700, Brad Smith wrote: > > > CVSROOT: /cvs > > > Module name: ports > > > Changes by: [email protected] 2013/03/07 18:21:38 > > > > > > Modified files: > > > devel/boost : Makefile distinfo > > > devel/boost/patches: patch-Jamroot > > > > > patch-boost_archive_iterators_remove_whitespace_hpp > > > > > patch-boost_asio_detail_pipe_select_interrupter_hpp > > > patch-boost_asio_detail_socket_ops_hpp > > > patch-boost_detail_endian_hpp > > > patch-boost_throw_exception_hpp > > > patch-libs_filesystem_src_operations_cpp > > > patch-tools_build_v2_tools_gcc_jam > > > devel/boost/pkg: PLIST > > > Added files: > > > devel/boost/patches: patch-boost_archive_basic_archive_hpp > > > patch-boost_interprocess_detail_workaround_hpp > > > Removed files: > > > devel/boost/patches: patch-boost_function_function_template_hpp > > > > > patch-boost_interprocess_detail_transform_iterator_hpp > > > patch-boost_math_tools_config_hpp > > > patch-boost_wave_token_ids_hpp > > > patch-libs_random_random_device_cpp > > > > > > Log message: > > > Update to boost 1.53.0. > > > > > > Mostly from Amit Kulkarni. > > > > It seems openscad & pokerth are still broken even after the > > update/followup commits: > > /usr/local/include/boost/type_traits/detail/has_binary_operator.hp:50: > > Parse error at "BOOST_JOIN" > > > > monotone fails with: > > keys.cc:47: error: 'boost::shared_dynamic_cast' has not been declared > > keys.cc: In function 'boost::shared_ptr<Botan::RSA_PrivateKey> > > get_private_key(lua_hooks&, const rsa_keypair_id&, const > > base64<rsa_priv_key>&, bool)': > > keys.cc:266: error: 'shared_dynamic_cast' was not declared in this scope > > > > Landry > > > > > Sorry for the breakage. I will take a look tonight. In the meantime, can > you please mark them as broken?
The breakage is now known & reproducible, and it's been broken for 5 days - no point in marking it BROKEN if it's fixed soon imo. I think BROKEN is more for 'permanent' failures. Landry
