RepoMan scours the neighborhood... dependency.bad [fatal] 2 net-libs/gnutls/gnutls-3.4.17.ebuild: DEPEND: ~hppa(default/linux/hppa/13.0) ['dev-util/valgrind'] net-libs/gnutls/gnutls-3.4.17.ebuild: RDEPEND: ~hppa(default/linux/hppa/13.0) ['dev-util/valgrind'] Note: use --without-mask to check KEYWORDS on dependencies of masked packages Note: use --include-dev (-d) to check dependencies for 'dev' profiles Please fix these important QA issues first. RepoMan sez: "Make your QA payment on time and you'll never see the likes of me."
Hi hppa, I would like to mask out the test-full USE of gnutls as I initially requested if there are keyword issues for these optional packages. I am unsure we can keyword valgrind. Thanks!
This is how you solve the issue: # euses -cs valgrind app-arch/lz4:valgrind - Enable usage of dev-util/valgrind in tests app-editors/zile:valgrind - Enable usage of dev-util/valgrind in tests dev-libs/efl:valgrind - Enable usage of dev-util/valgrind in debug dev-qt/qt-creator:valgrind - Add support for memory debugging using dev-util/valgrind dev-util/mdds:valgrind - Add support for memory debugging using dev-util/valgrind dev-vcs/cssc:valgrind - Enable usage of dev-util/valgrind in tests mail-client/claws-mail:valgrind - Add support for memory debugging using valgrind media-gfx/blender:valgrind - Add support for memory debugging using dev-util/valgrind media-libs/mesa:valgrind - Compile in valgrind memory hints media-libs/vigra:valgrind - Enable valgrind in make check media-sound/xmms2:valgrind - Run unit tests under valgrind. net-dialup/accel-ppp:valgrind - Compile in valgrind hints net-irc/epic5:valgrind - Compile against dev-util/valgrind headers to improve memory-leak checking when running epic5 under valgrind. net-mail/notmuch:valgrind - Depend on dev-util/vagrind for test suite x11-libs/cairo:valgrind - Built-in support to mark memory regions x11-libs/libdrm:valgrind - Compile in valgrind memory hints USE=valgrind is already masked on all architectures that valgrind does not support. The gnutls build system already knows about it, too.
are you sure? I just checked and I did not see mask of valgrind in hppa, also repoman complained.
~/git/gentoo/profiles $ grep -rw valgrind arch/amd64-fbsd/todo/package.use.mask:# dev-util/valgrind arch/amd64-fbsd/todo/package.use.mask:dev-libs/eina valgrind arch/sparc/use.mask:valgrind arch/ia64/use.mask:valgrind arch/sparc-fbsd/use.mask:# valgrind hasn't been ported to sparc-fbsd yet arch/sparc-fbsd/use.mask:valgrind arch/hppa/use.mask:# # dev-util/valgrind has not been ported to HPPA. arch/hppa/use.mask:valgrind arch/arm/package.use.stable.mask:<=dev-util/valgrind-3.10.1 mpi arch/x86-fbsd/use.mask:# valgrind hasn't been ported to fbsd yet arch/x86-fbsd/use.mask:valgrind arch/alpha/use.mask:valgrind arch/alpha/package.use.mask:# Mask USE=test since it implies USE=valgrind
Sorry, I did not check this properly. Fixing.
OK, fixed. Sorry for the mess, I did not know about the valgrind USE. Thought to request to unmask gnutls USE. I hope that now we can stabilize gnutls easily.
Thanks.
