Comment 6 for bug 3138

In fact, bug #31038 fix introduces a new approach:

uploads present in NEW are considered untrusted, they can be duplicated (same name/version) and the uniqueness will be only enforced in the transition to ACCEPTED.

Since *known* uploads are promoted to ACCEPTED automatically in the upload time (auto-approve), they will be rejected if the uniqueness is not respected.

So, we definately don't want to check version consistency against NEW.

Maybe storing possibly duplicated NEW uploads will let us in a risk condition, by wasting storage space and other resources, but I don't think this is the case right now.