Closed bchavez closed 7 years ago
Meh, thanks for tracking that down with them. I de-listed all the Baseline versions < 1.0 before we switched to using dotnet pack
and a different set of problems
Thanks so much @jeremydmiller for your help. Maybe I need to wait for some cache or index to get updated because it doesn't seem to have worked yet. sigh :disappointed:
Are you okay with the NuGet team nuking the NuGet Baseline
packages with versions < 1.0 if it comes down to it?
I'm going to report back to https://github.com/NuGet/NuGetGallery/issues/4494 in a few hours or so.
The Baseline
NuGet issue has been finally put to rest and resolved.
https://github.com/NuGet/NuGetGallery/issues/4494#issuecomment-339439985
Hey, I finally heard back from the people in the NuGet Ivory tower :tokyo_tower:. They say the solution to resolving this annoying NuGet issue with
Baseline
is to delist theBaseline
packages that contain the error. The crux of the issue is an emptyid
string in the "dependencies" part of the NuGet.nuspec
as shown below:Anyway, I've tried very hard to convince the NuGet team that they need to fix this issue because it really turns out to be their problem but they just now closed my issue: https://github.com/NuGet/NuGetGallery/issues/4494. Their response is to ask the package author to delist the specific NuGet package versions that are affected by the "empty id string" dependency.
So, let's try it and maybe we can finally put this damn issue to rest. If it fails, I'll be back in their front yard.
The following
Baseline
versions that need to be delisted are:Thanks, Brian
/cc @jeremydmiller @CoreyKaylor
For reference, the past issues that others have encountred this issue are: here, here, and here.