I have a package dependency situation as follows:
Error:

Attempting to gather dependency information for package 'PkgB.2.0.414' with respect to project 'test Nuget Package Usage', targeting '.NETFramework,Version=v4.5'
Attempting to resolve dependencies for package 'PkgB.2.0.414' with DependencyBehavior 'Lowest'
Unable to resolve dependency 'PkgC.1.0.0'. Source(s) used: 'nuget.org', 'Company Package source', 'Local testing', 'Microsoft and .NET', 'Microsoft Visual Studio Offline Packages'.

Situation A:
PkgA=>PkgC

Situation B:
PkgB=>PkgA=>PkgC

When I install situation A it works. When I install situation B it works. But if I install A then B it fails to find Pkg C even though its already installed and working fine.

Keep in mind the following environment:

These are all packages that install fine individually and separately.
This problem **only** happens using a NuGet feed server.
I don't have this problem using a package share as the source of installation.

Sources:
I've looked at NuGet documentation for versioning and the nearest algorithm, but I don't see how I would be violating it.

<https://docs.nuget.org/ndocs/consume-packages/dependency-resolution#dependency-resolution-in-nuget-3-x>

And I don't see how specifying versions would matter either.
<https://docs.nuget.org/ndocs/create-packages/dependency-versions#dependency-versions>

My own conclusion:

It seems like the issue is in the feed server and how it finds the dependencies. I'm looking at the NuGet.Server source on git but haven't noticed anything yet. I'll probably end up bringing down the source and figuring it out.

Shouldn't this situation work regardless of the type of feed source? 

Edit:

This is a private nuget feed and private nugets that aren't in any repo that I can share publicly. 

I used the version >= notation referenced here to build the reference tree throughout the situations. 

```
<!-- Accepts any version 6.1 and above -->
<dependency id="ExamplePackage" version="6.1" />

```