If I autounmask a program, and it has deps which need unmasking, autounmask will unmask all versions of the dep that will satisfy the program building. This is not ideal, as it (often in my experience) will result in -9999 versions being built when there are release versions available which would suffice. Reproducible: Always Steps to Reproduce: 1. Autounmask a program with a DEP that has multiple masked/keyworded versions 2. eg. fluxbox-9999 3. Actual Results: All versions that match the DEP will be unmasked or keyworded eg. # --- # BEGIN: x11-wm/fluxbox-9999 # --- =x11-wm/fluxbox-9999 ~x86 =sys-apps/util-linux-2.16 ~x86 =sys-devel/libtool-2.2.6a ~x86 =sys-devel/libtool-2.2.4 ~x86 # --- # END: x11-wm/fluxbox-9999 # --- Expected Results: Only one version of the DEP is required - so only one should be unmasked. Ideally, this would be one that is keyworded, not masked. (maybe the lowest possible version that matches?). It should definitely not unmask -9999 when there is a release version available.
As on the prior bug 279000 this may be an upstream issue.
(In reply to comment #1) > As on the prior bug 279000 this may be an upstream issue. > Wrong bug link? Afaik, upstream is ian@gentoo.org, with no website/project page.
(In reply to comment #2) > (In reply to comment #1) > > As on the prior bug 279000 this may be an upstream issue. You probably meant bug 279600
Ok, sorry for the mistake on related bugs, leaving to maintainers.
package no longer in tree
