Hide Forgot
Description of problem: maven2-plugin-surefire <= 2.0.4 is obsoleted by maven2 maven2-plugin-surefire 2.3 is provided by maven-surefire-maven-plugin I am unable to make yum see the virtual provide of maven2-plugin-surefire 2.3 by maven-surefire-maven-plugin. Version-Release number of selected component (if applicable): yum-3.2.24-1.fc11.noarch $ sudo yum --enablerepo=rawhide install maven2-plugin-surefire Loaded plugins: presto, refresh-packagekit Setting up Install Process Package maven2-plugin-surefire-2.0.4-11.19.fc11.x86_64 is obsoleted by maven2-2.0.8-2.fc12.noarch which is already installed Nothing to do $ rpm -q --obsoletes maven2 maven2-plugin-jxr <= 0:2.0.4 maven2-plugin-surefire <= 0:2.0.4 ^^^^^^^^^^ ... $ sudo yum --enablerepo=rawhide install maven-surefire-maven-plugin ... Installed: maven-surefire-maven-plugin.noarch 0:2.3-7.7.fc12 $ rpm -q --provides maven-surefire-maven-plugin maven2-plugin-surefire = 0:2.3-7.7.fc12 ^^^^^^^^^^^^^^ maven-surefire-maven-plugin = 0:2.3-7.7.fc12
okay - the issue here we debugged on irc if you --disablerepo='*' --enablerepo=rawhide then this command works as promised ditto if you specify the full provide. this is b/c of the presence of a real maven2-plugin-surefire pkg in the f11 repo. So yum is seeing that, then noticing that maven2 is installed and already obsoletes it and stopping. I'm looking into it further.
to make life a bit more complicated: yum install foo tries to find the best foo it can. so which is a better foo: bar, which obsoletes foo or baz which provides foo = 12.0 we've always said obsoletes trump provides. if so then we're working correctly, currently, it just feels a bit weird. I'm going to close this notabug- but it sure feels weird.