Depcheck conflicts should be ignored, but are not

[Kamil Paral]

> Hello,
> 
> This update:
> https://admin.fedoraproject.org/updates/tomcat-native-1.1.30-1.fc20
> ...has some expected conflicts which are flagged by depcheck:
> http://autoqa.fedoraproject.org/results/813107-autotest/virt04.qa/depcheck/results/tomcat-native-1.1.30.html
> 
> Now, according to
> https://fedoraproject.org/wiki/AutoQA_tests/Depcheck#Conflicts,
> "Errors caused by packages conflicting each other should be ignored at
> the moment" but clearly they are not ignored, because based on this
> "failure", bodhi did this: "Automatic push to stable based on karma
> has been disabled for this update due to failure of an AutoQA test".
> 
> What's the place to fix this, AutoQA or Bodhi, or the Wiki Depcheck doc?

Thanks for your email. I'm afraid the only way how to "fix this" is to wait until we release a completely new depcheck running on Taskotron.

We know that current depcheck utterly fails with packages containing Conflicts or Obsoletes flags. Despite these false negatives, it was decided to disable bodhi karma automatism for depcheck failures, because it hopefully produces more good than bad. So the documentation is correct in the sense that you should ignore the error and manually verify whether the package can be installed, but we should probably add a note that you need to manually push the update to stable in these cases.

Please feel free to adjust the explanation on the wiki, thanks a lot.