i also had some problems with the nuget recently, mostly when updating to a new version. it seems to me that sometimes it does not update the filename in the csproj, which forced me to do all the changes manually and defeating the purpose of nuget automatisation.
maybe this has something to do with the way it is linked as a of a project, instead as a ?
<Import Project="..\packages\VVVV.PluginInterfaces.31.7.0-develop-avalon-e-159\build\net40\VVVV.PluginInterfaces.targets" Condition="Exists('..\packages\VVVV.PluginInterfaces.31.7.0-develop-avalon-e-159\build\net40\VVVV.PluginInterfaces.targets')" />
At the beginning of vvvv’s nuget feed you had both stable and alpha releases to pick from, for some time now you only have your rolling release. Most of the work I am doing is with the beta (currently 31.2x64), but there is no way to do that with nuget any more. Also if I do not update the references, a fresh clone from git will not pull the packages if the feed has been updated- old versions (that are referenced in the project) are never offered and hence a build or an update might fail.
Would it be possible to reintroduce stable versions that remain indefinitely in your feed? I would then update my libs in my projects only with the release of a new beta.