ceph is FTBFS due to a change in Boost Asio. I'll file a PR this morning.
usr/include/boost/asio/async_result.hpp:651:9: error: no type named 'completion_handler_type' in 'class boost::asio::async_result<boost::asio::basic_yield_context<boost::asio::executor>, void(boost::system::error_code, ceph::buffer::v15_2_0::list)>'
651 | completion_handler_type;
| ^~~~~~~~~~~~~~~~~~~~~~~
On Thu, Feb 23, 2023 at 6:04 AM Kaleb Keithley <kkeithle@xxxxxxxxxx> wrote:
On Thu, Feb 23, 2023 at 8:19 AM Jakub Jelinek <jakub@xxxxxxxxxx> wrote:On Thu, Feb 23, 2023 at 01:11:13PM +0000, Jonathan Wakely wrote:
> On Thu, 23 Feb 2023 at 13:03, Richard W.M. Jones wrote:
> > Do you know anything about what's happening with Ceph?
>
> No idea, sorry.
Ceph is likely #2169364 aka https://gcc.gnu.org/PR108773 , still unresolved
GCC bug.Doubtful. That's from building early snapshots of what will become ceph-18. Thus far ceph-17 hasn't hit the ICE.right now the issue is with the bundled boost building with Python-3.11. There are a lot of moving parts.--Kaleb
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
