The Features module has, in the past, refused to revert (without any useful errors) if it meant removing a field instance. It has also been tripped up by trying to revert a content type that was already created before the feature was enabled, but was missing field instances.
As far as I am aware, those two specific problems got fixed. Or I could just have been lucky and never run into them again!
You're going to have to remove whatever hangups the Feature might be having by doing one of the following. I find that when Features is giving me trouble the solution can boil down to trying to make it do its job easier:
Add the missing field to the type that won't revert, by hand. The field is clearly not there yet, so simply adding a field named 'field_target_nodes' and then try to revert might do the trick. Fields can be added (if the Field UI core module is enabled) at Administer > Structure > Content types > Content-type-name.
Completely delete the offending content type and try to revert the feature, afterward. Consider even going as far as deleting each field from the type beforehand, to make sure everything is totally removed and anything that Features might be getting hung up on are out of the way. This will remove all data saved in the content type, all data saved in those fields, etc.
Alternately, if you can understand PHP, you can go a step further in #1 and pretend you're the features module. All of the settings options you'll need are all wrapped up in the features include file(s), and they're actually quite easy to read and understand. If you set the fields up the way they're "supposed" to be initially, it should remove any future revert issues.
Additional side questions: What version of Features are you running? What version of wiki commons? Following up on goron's question in the comment would be helpful, too.