I don't see the reasons for making "ebuild.notadded" warning not to be fatal since, anyway, people won't be able to commit later: RepoMan scours the neighborhood... >>> Creating Manifest for /home/pacho/gentoo-x86/x11-themes/light-themes ebuild.badheader 1 x11-themes/light-themes/light-themes-0.1.93-r3.ebuild: Invalid Gentoo Copyright on line: 1 ebuild.notadded 1 x11-themes/light-themes/light-themes-0.1.93-r3.ebuild Note: use --include-dev (-d) to check dependencies for 'dev' profiles !!! The following files are in your local tree but are not added to the master !!! tree. Please remove them from the local tree or add them to the master tree. ./light-themes-0.1.93-r3.ebuild Thanks!
it should only be fatal when using `repoman commit`. just doing checking (like `repoman full`) shouldn't fail.
In that case I guess it's not a big problem since it will die anyway. I was thinking a bit more on getting the "red" error at "repoman full" stage (sometimes I miss it as some packages have lots of other "soft" (yellow) warnings due things like -j1 usage and so... Then, if you prefer to get this closed as wontfix, no problem :)
(In reply to Pacho Ramos from comment #2) having repoman fail when you try to commit w/ebuild.notadded is reasonable as it's very very unlikely that's what the dev wants. on the other hand, having it fail when you're just doing a check is very very unlikely what the dev wants. i think implementing this behavior makes sense. now someone just needs to do it :).
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.
