Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Packages are disappearing from dotnet-core feed after being published
See original GitHub issueNot a dup of #2936
Can someone take a look please?
https://dev.azure.com/dnceng/internal/_build/results?buildId=300660
##[error].packages\microsoft.dotnet.arcade.sdk\1.0.0-beta.19407.9\tools\Tools.proj(0,0): error NU1603: Tools depends on Microsoft.DotNet.SignTool (>= 1.0.0-beta.19407.9) but Microsoft.DotNet.SignTool 1.0.0-beta.19407.9 was not found. An approximate best match of Microsoft.DotNet.SignTool 1.0.0-beta.19408.2 was resolved.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:28 (27 by maintainers)
Top Results From Across the Web
Packages are missing after a successful dotnet publish
The publish command works fine but after it is run, I have to restore the project as there are missing packages.
Read more >NuGet Package Restore
NuGet Package Restore restores all of a project's dependencies that are listed in either a project file or a packages.config file.
Read more >Troubleshoot missing packages - Deployments
If the package exists in the external feed, check it hasn't been hidden/removed from the package feed's index. For example, in NuGet.org you...
Read more >How to Use NuGet Packages: The Ultimate Guide
Navigate to Tools > Options > NuGet Package Manager > General, and then select the Allow NuGet to download missing packages check box...
Read more >Installing .NET 6 on Ubuntu 22.04 (Jammy) · Issue #7699
We'll install .NET 6 with both feeds, from a clean state, and then point the various ways you can identify which feed you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I went through the delete script with @jcagme and we found that the cache was being reused between lock operations, which lead to delete working against older files, hence new packages were getting dropped.
I’ve added a helper to sleet to run delete operations in a single batch to avoid this and will also add some checks to that the virtual file system to help prevent this happening in the future if the library is used this way. https://github.com/emgarten/Sleet/pull/84
The problem here is limited to the current delete script that was being used, everything else is working correctly.
Yes, I think @riarenas is already (looking at) doing that and I’ll also jump in to get this sorted.