in dev-java/sun-jdk, repoman tells me ebuild.allmasked 1 dev-java/sun-jdk which is apearly wrong >=1.49 is package.masked, it should possible tell me that (i'm not totaly sure whats wrong, ferringb told me on irc its a bug "There is something funky going on w/ gvisible")
repoman is directly setting portage.groups around line 710; what is happening, is that portage.groups isn't being reset the system default, and this is getting flagged. So, either the check should be moved above the arch check, or portage.groups should be reset. Easy way to verify this is the issue is run cd ${PORTDIR}/dev-java/sun-jdk repoman scan --ignore-other-arches And watch ebuild.allmasked no longer appear :) This is kind of an oddball check imo. It shouldn't be limited to the users groups; in other words, portage.groups ought to be set to all arches (since it's entirely possible a dev may need to commit a syntax correction on an ebuild that isn't available on their arch).
Created attachment 35418 [details, diff] repoman-ebuild.allmasked.patch Resets portage.groups to keywords "*", eg ebuild.allmasked only is flagged when the ebuild isn't available for any arch, period (package.mask or no keywords). Also corrected the indentation.
I ran into this just committing net-p2p/dc-qt and net-p2p/limewire, though KEYWORDS is correctly set... using _pre17
I don't see a problem with those packages, all ebuilds there are masked as ~arch so the warning is valid.
you're right; I missunderstood the warning. I thought it was referring to masking a whole package in package.mask. Sorry for the confusion :-\.
commited this in pre14 (might have been pre15). Either way, it's fixed.
