At the moment we can only run the test again the rpms which are generated by mock.
This means that we are reviewing a package B which depends on A which we just approved, the mock build will still not work as the package A is still not in the repo.
We need a way to go around this.
Technically you can do mock build yourself (with mock install dependency.rpm) and then run fedora-review with --nobuild but you are right. Should be easier :-)
I do my mock builds on a separate machine and it would be great to be able to integrate that work flow somehow.
I'm trying to start to look at this. First issue I come across with --nobuild is it is trying to extract the sources into /var/lib/mock/fedora-rawhide-i386/root/builddir/build/sources which doesn't exist and isn't writable on my system. I'd like to just use the current directory or maybe a different temp dir. But I'm not sure the best way to pass a value for extract_dir to Source.extract().
Replying to [comment:7 orion]:
I'm trying to start to look at this.
Cool :)
First issue I come across with --nobuild is it is trying to extract the sources into /var/lib/mock/fedora-rawhide-i386/root/builddir/build/sources which doesn't exist and isn't writable on my system. I'd like to just use the current directory or maybe a different temp dir. But I'm not sure the best way to pass a value for extract_dir to Source.extract().
This is a different issue than this ticket, would you care to open a specific ticket to track it down?
Issue 36 filed.
Fixed in my branch (yet to be published) using --prebuilt command line switch together with -n
Is this branch available anywhere for testing?
Yup, it's merged in current master as of today (sorry for late reply).
Fixed in eee12a2, closing. PLease feel free to reopen this issue if you feel it's not solved.
Preferably, use current master when testing; there are some bugfixes applied after the initial commit.
Login to comment on this ticket.