*.failed files causing massive headache with some clients being unable to install/update

Description

There are two feeds (nuget.org) and an internal feed that both have different versions of System.Windows.Interactivity.

• The nuget.org package is deprecated (not sure if that matters).
• nuget.org has versions 1.0.0 and 1.0.1
• The internal feed has version 3.0.40218.0
• paket.dependencies specifies ~> 3.0, so the nuget.org packages should be disregarded completely

Repro steps

paket.dependencies:

framework: auto-detect
source https://nuget.org/api/v2
source https://internal.feed.local/httpAuth/app/nuget/v1/FeedService.svc

nuget System.Windows.Interactivity ~> 3.0

paket install tries to query nuget.org for ~> 3.0, but fails with this message:

Paket version 4.8.5
Resolving packages for group Main:
Paket failed with:
        There was a version conflict during package resolution.
  Could not resolve package System.Windows.Interactivity >= 3.0 < 4.0:
   - Available versions:
     - (1.0.1, [https://www.nuget.org/api/v2])
     - (1.0.0, [https://www.nuget.org/api/v2])

  Please try to relax some conditions or resolve the conflict manually (see http://fsprojects.github.io/Paket/nuget-dependencies.html#Use-exactly-this-version-constraint).

We tried reordering the source statements, but that didn’t help.

We were able to generate a paket.lock file in an earlier version of paket, something between Fri Feb 3 16:42:44 2017 +0100 (last commit on the lockfile) and today broke that feature.

[matthid]

Maybe I can help with debugging this (Skype “matthi dot d at live dot de”)? If not possible I’d suggest setting a breakpoint somewhere around the lines I posted above and see which path is taken for your package…

[agross]

Idea: bundler adds its version to the lock file (only when it changes). Paket should probably too. @forki