Description: ------------ This is not the same as bug #13425, but is closely related. Consider a package "XYZ". Consider a complex dep chain where at several points in the chain "XYZ" is a dependency. At some point(s) in that chain, the dependency on XYZ is a "simple" (unversioned) dependency. At some point(s) there is a <max> on a particular version XYZ. The <max> does not appear to completely exclude versions which exceed that <max> from the dependency resolution map, resulting in the exacerbation of other (related, but different) problems such as bug #13425. (Even if bug #13425 was fixed to only give a warning, the fact would remain that in some cases it would give bogus "warnings" about multiple versions meeting the installation dependency criteria, even though in reality all but 1 of those versions would be excluded via <min> or <max> criteria) I will try to get a good reproduction example for this.

Line 1334 of Downloader/Package.php (in mergeDependencies()) says: // detect versioning conflicts here Is that where the check should be?

Marking this as won't fix for the same reason as Bug #13425