Created attachment 603734 [details] emerge --info When you install mbedtls 2.19.1 as of today, you get an installation that is internally inconsistent as the installed version.h claims "2.17": gert@blueNUC2:/usr/include/mbedtls$ equery b `pwd`/version.h * Searching for /usr/include/mbedtls/version.h ... net-libs/mbedtls-2.19.1 (/usr/include/mbedtls/version.h) gert@blueNUC2:/usr/include/mbedtls$ grep MBEDTLS_VERSION version.h #define MBEDTLS_VERSION_MAJOR 2 #define MBEDTLS_VERSION_MINOR 17 #define MBEDTLS_VERSION_PATCH 0 #define MBEDTLS_VERSION_NUMBER 0x02110000 #define MBEDTLS_VERSION_STRING "2.17.0" #define MBEDTLS_VERSION_STRING_FULL "mbed TLS 2.17.0" the version.h in the mbedtls 2.19.1 tarball is fine, but the ebuild also builds mbedcrypto, and the version used *there* has a mbedtls/version.h which is 2.17.0 >>> Emerging (1 of 1) net-libs/mbedtls-2.19.1::gentoo * mbedtls-2.19.1.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] * mbedcrypto-2.0.0.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] I've tried to find a page detailing mbedtls <-> mbedcrypto dependencies but failed - so I leave that to the ebuild maintainers to figure out...
Actually, I'm finding the same problem with 2.18.1. The whole mbedtls <-> mbedcrypto is quite annoying.
*** This bug has been marked as a duplicate of bug 705038 ***
