On Sat, 08 Jun 2013 15:11:12 -0400
Rich Mattes <richmattes(a)gmail.com> wrote:
Hi,
I noticed during a yum upgrade today that gcc-4.8.1 hit stable, but a
rebuild of llvm/clang wasn't available yet so my upgrade failed. I
went and looked at the bodhi update for 4.8.1[1]: it passed with +3
karma and got auto-pushed. I noticed that the depcheck test passed,
so I clicked on it and saw tons of errors from the yum depsolver[2].
It really looks like this test should not have passed with how many
issues were present.
Yeah, that looks like a test execution failure to me. It was marked as
PASS because it didn't end as a FAIL due to the test execution problem.
The full logs explain that the run as a whole was marked
NEEDS_INSPECTION due to the execution not completing cleanly.
Does depcheck just look at the dependencies for the update in
question? i.e., in this update gcc-4.8.1's dependencies are all
present, so things pass? If that's the case, I can see why autoqa
says it was OK, but I'd argue that it still should have failed since
so much other stuff depends on the older version of gcc, and that
other stuff would break as a result of the update request.
Unfortunately, we don't have a good way to treat specific packages
differently.
Anyway, I just wanted to bring it to your attention and see what you
think.
Thanks for bringing it to our attention. I think this might end up
being more fuel to the fire of "replace depcheck with something saner",
though. I have some ideas on how to do that, just need to find the time
to get it done or someone else who's interested in doing the work :-/
Tim