Arch Linux User Repository

Check out https://wiki.archlinux.org/title/Makepkg#Signature_checking. Basically, if you use makepkg directly, you'll have to manually import all keys into your user GPG keyring. You can do that by running gpg --import keys/pgp/*.

Some AUR helpers like yay are able to do that for you. If you encounter server errors, configure GPG to use a better server. Most PGP servers today are unreliable. I recommend hkps://keyserver.ubuntu.com.

I've been using yay, but my gpg was only using keyserver hkps://keys.openpgp.org. Setting hkps://keyserver.ubuntu.com as an additional keyserver in ~/.gnupg/gpg.conf fixed the issue for me. Thank you!

Check out https://wiki.archlinux.org/title/Makepkg#Signature_checking. Basically, if you use makepkg directly, you'll have to manually import all keys into your user GPG keyring. You can do that by running gpg --import keys/pgp/*.

Some AUR helpers like yay are able to do that for you. If you encounter server errors, configure GPG to use a better server. Most PGP servers today are unreliable. I recommend hkps://keyserver.ubuntu.com.

Did the pubkey change? I get a Botan-2.19.5.tar.xz ... FAILED (unknown public key 6211EBF1EFBADFBC)

now compile. tnx.

As others have pointed out, this does not build. Here's the full error output I got: https://pastebin.com/KyuLuY4W

src/lib/utils/socket/socket.cpp:128:20: error: ‘io_service’ in namespace ‘boost::asio’ does not name a type; did you mean ‘use_service’?
128 |       boost::asio::io_service m_io;
|                    ^~
|                    use_service

Does not build:

src/lib/utils/socket/socket.cpp:128:20: error: ‘io_service’ in namespace ‘boost::asio’ does not name a type; did you mean ‘use_service’?
  128 |       boost::asio::io_service m_io;

and more.

I'm having trouble building this with the latest version of boost. For example:

src/lib/utils/socket/socket.cpp: In member function ‘void Botan::{anonymous}::Asio_Socket::check_timeout()’:
src/lib/utils/socket/socket.cpp:118:50: error: no matching function for call to ‘boost::asio::basic_waitable_timer<std::chrono::_V2::system_clock>::expires_at()’
  118 |          if(m_tcp.is_open() && m_timer.expires_at() < std::chrono::system_clock::now())
      |                                ~~~~~~~~~~~~~~~~~~^~
src/lib/utils/socket/socket.cpp:118:50: note: there is 1 candidate
In file included from /usr/include/boost/asio/steady_timer.hpp:19,
                 from /usr/include/boost/asio/basic_socket_streambuf.hpp:30,
                 from /usr/include/boost/asio/basic_socket_iostream.hpp:24,
                 from /usr/include/boost/asio.hpp:43,
                 from src/lib/utils/socket/socket.cpp:20:
/usr/include/boost/asio/basic_waitable_timer.hpp:480:15: note: candidate 1: ‘std::size_t boost::asio::basic_waitable_timer<Clock, WaitTraits, Executor>::expires_at(const time_point&) [with Clock = std::chrono::_V2::system_clock; WaitTraits = boost::asio::wait_traits<std::chrono::_V2::system_clock>; Executor = boost::asio::any_io_executor; std::size_t = long unsigned int; time_point = std::chrono::time_point<std::chrono::_V2::system_clock, std::chrono::duration<long int, std::ratio<1, 1000000000> > >]’
  480 |   std::size_t expires_at(const time_point& expiry_time)
      |               ^~~~~~~~~~

It looks like this usage of expires_at was deprecated and removed in boost 1.87: https://www.boost.org/doc/libs/1_86_0/doc/html/boost_asio/reference/basic_waitable_timer/expires_at.html vs https://www.boost.org/doc/libs/1_87_0/doc/html/boost_asio/reference/basic_waitable_timer/expires_at.html