Could you add a feature - check if dependencies of package are resolved and package can be installed? Currently, I and few other people are using Petr's script, but it would be great to have wider user base.
http://ppisar.fedorapeople.org/betterfedora/resolvedeps
Hm... During a normal run of f-r, the package both built and installed. If the installation fails e. g., due to unresolved deps the error messages are visible, but no other actions are taken. Doesn't this fulfill your requirements? Or is it something I miss?
Note that it should be simple to run the script as a shell plugin as documented on the wiki. That would be a path to try the script in a fedora-review context. But I certainly miss something here...
and... so far we gave avoided hard dependencies on Koji - practically speaking f-r should work also for e. g., rpmfusion packages. But this could be handled with some checks I guess, just returning 'Not applicable' if the package can't be located. The general solution would still be to use yum-downloader to download the deps and probe them locally. Much more work, but should work for anything yum could find.
Well... 0.3 is already released, and this will not make it for .0.4. Moving to future
You might be right, that fedora-review is already doing it. I wanted to try, but it fails with ugly backtrace, so I'll look at it later.
If your package builds in mock and fedora-review fails with ugly backtrace, that's certainly a bug. What's the package?
Ok, I have review. I see as comment in text file:
perl-Modern-Perl-1.20121103-1.fc19.noarch.rpm (rpmlib, GLIBC filtered):
perl >= 1:5.010_000 perl(:MODULE_COMPAT_5.16.2) perl(IO::File) perl(IO::Handle) perl(feature) perl(mro) perl(strict) perl(warnings)
It would be helpfull if the script could also validate if the installation passed in rawhide (or something else based on plugin).
fedora-review always tries to install the package. If you have this line in the review:
[x]: Package installs properly.
it has installed the package without problems. Otherwise, there should be error messages attached. The installation is done in the same mock root as the build, reflected in the bottom of the report (look for 'Buildroot used:'). You can change that using -m/--mock-root option.
Does this solve your needs, or am I (as usual...) still missing something?
EDIT: I ran fedora-review for myself on perl-Modern-perl using -m fedora-rawhide-1386. Conclusions:
Thanks, my problem is solved.