I submitted a Pull Request to update MacPorts' libtorrent to 0.16.22 here:

https://github.com/macports/macports-ports/pull/34531

GitHub Continuous Integration checks passed OK!

It's up to someone else with commit access to merge it.

As with the lesson learned with 0.16.20, I will wait until this Pull Request is merged before submitting a Pull Request for rtorrent to 0.16.22 (I have that diff prepared and tested locally already) so that the necessary library is updated prior to the tool which depends upon the library!

Release notes for rtorrent 0.16.22 can be found here:
https://github.com/rakshasa/rtorrent/releases/tag/v0.16.22

You'll note "gzip.h: fix build with Clang (less than symbol goes here) 17 [as snac strips things after that symbol thinking it is an HTML angle bracket] by @aeiouaeiouaeiouaeiouaeiouaeiou" which was submitted via another MacPorts contributor after my previous Pull Requests were merged, fixing builds on older versions of OS X. The Port Health is looking a LOT better:

https://ports.macports.org/port/libtorrent/details/

For libtorrent at least.

For rtorrent? Still room for improvement (essentially everything older than Big Sur appears to be failing on the buildbots): https://ports.macports.org/port/rtorrent/details/

I thought about adding myself as a maintainer; yet in keeping in alignment with the "not taking on more responsibilities until I am no longer homeless" I think maybe, I will just keep a watchful eye and update as I see changes, rather than shoulder more burden for the time being? I'm 3 days behind upstream, that's still better than a lot of professional paid developers who have homes seem to manage.

#libtorrent #MacPorts #OpenSource #rtorrent #BitTorrent #torrent #p2p #TUI #ncurses