The armhf failure from Debian #1111250 is fixed in 5.0~alpha2.145.g12d031cf8+dfsg-5, but that version can't build in stonking: every build is in dependency wait on libboost-system-dev, which no longer exists since Boost 1.89 removed the system library (stonking has Boost 1.90). This is Debian RC bug #1127287, which has no fix; swift-im has been removed from Debian testing.
Dropping libboost-system-dev and the boost_system check in BuildTools/SCons/SConstruct wouldn't be enough: Swiften uses Boost.Asio APIs removed in Boost 1.87 (boost::asio::io_service is used 44 times across 23 files, plus address::from_string, resolver::iterator and null_buffers). Building it would require porting the networking layer to io_context. Upstream (https://github.com/swift/swift) has had no commits since January 2020. swift-im hasn't been in the release pocket since plucky and nothing build-depends on libswiften-dev, so removing it has no impact. Archive admins: please remove swift-im 5.0~alpha2.145.g12d031cf8+dfsg-5 from stonking-proposed. No blocklist needed, a fixed Debian upload can sync later. ** Summary changed: - swift-im ftbfs in unstable + Remove swift-im from stonking-proposed (needs libboost-system-dev and pre-1.87 Boost.Asio APIs) ** Changed in: swift-im (Ubuntu) Status: New => Confirmed ** Changed in: swift-im (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2121357 Title: Remove swift-im from stonking-proposed (needs libboost-system-dev and pre-1.87 Boost.Asio APIs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift-im/+bug/2121357/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
