as subject says. if a package is masked in /usr/portage/profiles/package.mask, repoman doesn't allow to commit (to overlay) ebuilds depending on it, even if the masked package is manually unmasked in /etc/portage/package.unmask the errors given by repoman are obviously RDEPEND.bad, DEPEND.bad I think this shouldn't happen, cause I'm using repoman for commit stuff to an overlay, and also the ebuild dependency is in overlay.
sounds to me like repoman is working correctly ... there's also no real way to determine whether you're in "an overlay" or "the official tree" i'd say use the --force option to repoman and be done
repoman specifically ignores any files in /etc/portage on purpose.
(In reply to comment #0) > if a package is masked in /usr/portage/profiles/package.mask, repoman doesn't > allow to commit (to overlay) ebuilds depending on it, even if the masked > package is manually unmasked in /etc/portage/package.unmask As said, /etc/portage is a _local_ config but repoman is doing QA on the _repository_. I think what you really want is repoman to treat the overlay as a separate repository from the main tree, having independent package.mask settings rather than inheriting them. I think it's reasonable for us to support that type of behavior in the future when we have multiple repository support, if not by default then at least as an option.
