https://qa-reports.gentoo.org/output/gentoo-ci/a329b8162/output.html#dev-libs/leveldb The static-libs flag is no longer present in the current version due to upstream build system changes. Please stop depending on it as it blocks removal of the old version.
Ping. Please solve this, or I'll p.use.mask static-libs on leveldb.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d8d3d3e9b30bbeb1d04c0fc458afe14e8d49f345 commit d8d3d3e9b30bbeb1d04c0fc458afe14e8d49f345 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2018-05-27 12:37:30 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-06-13 07:21:04 +0000 profiles/base: Mask revdeps of app-arch/snappy[static-libs] Closes: https://bugs.gentoo.org/651604 Closes: https://bugs.gentoo.org/651606 profiles/base/package.use.mask | 8 ++++++++ 1 file changed, 8 insertions(+)
Is the use.mask for USE=static on qemu necessary? To my untrained eyes, the qemu ebuild says you cannot build with USE=static if snappy is selected, and makes no request for snappy to have static-libs anywhere. As you can tell I rely on qemu[static]
The only alternative *I* have is masking USE=snappy which will make some other people unhappy. Anything else is up to qemu maintainers.
(In reply to David Flogeras from comment #3) > Is the use.mask for USE=static on qemu necessary? To my untrained eyes, the > qemu ebuild says you cannot build with USE=static if snappy is selected, and > makes no request for snappy to have static-libs anywhere. As you can tell I > rely on qemu[static] Unmasked as https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=aaf4ec2591ab9874e0e7efb89a83ecd3d39f514e. Please file a bug against qemu maintainers to fix it faster next time.
