Can Paket resolve dependencies without finding the right packages?

I will explain my thought. For example, package A requires sub-dependency: package B version 1.
A package B requires subdependence: package B versions from 1 to 2.

In this case, "Paket" will take package B version 1. Am I right?

But I need the package manager to simply give an error saying that it cannot find package B of version 2.

Where it can be used: we have a build system that collects web services in different directories. At the same time, we place the shared libraries in a shared directory.
Thus, we guarantee to ourselves that all web services work with the same versions of libraries, even in subdependencies.
For us it is important.

Question: Does Paket do this?
Thank. P.S. I used google translate.

P.P.S. We are now working with "Nuget" and he does not know how and does not even want to be able to.
The result is that the assembly can build first with the libraries of some versions, and then in the next assembly, "Nuget" may decide to apply a different packet resolution strategy and the assembly will assemble with libraries of other versions. And it turns out only at the testing stage. It looks like a powder keg.

The issue names no files, tests, or entry points. First clarify the intended dependency-resolution rule and whether the request is a question or a proposed change; then inspect Paket's resolver behavior and define a reproducible package scenario whose result distinguishes successful resolution from the requested error.