NuGet Package does not contain a manifest
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the upload using Microsoft.Web.LibraryManager.Build versions 2.0.76 or 2.0.96 and the documented NuGet.Server setup, then inspect the reported PackageHelper.GetManifestStream and PackageFactory.Open stack trace. Done means identifying whether the package or NuGet.Server is responsible and restoring a successful push with the documented nuget command.
Written by the indexing model from the issue text.
Description
Hello,
for our internal build and deploy, we have set up our own NuGet server as described in
https://docs.microsoft.com/en-us/nuget/hosting-packages/nuget-server
Using NuGet.Server version 3.4.1 including latest versions of all dependencies, behind an Microsoft IIS 7 server.
To this server, I am unable to upload the package
Microsoft.Web.LibraryManager.Build
from
https://www.nuget.org/packages/Microsoft.Web.LibraryManager.Build/
(tested with version 2.0.76 and 2.0.96).
I receive the error message described below.
Because this is the only package, where this error occurs, I believe it is an error in the package itself, not in the NuGet.Server. So I created the issue here in this project.
Best regards
Daniel
Functional impact
Unable to use the package "Microsoft.Web.LibraryManager.Build".
Minimal repro steps
-
Download the NuGet package from the official gallery:
https://www.nuget.org/packages/Microsoft.Web.LibraryManager.Build/ -
Try to push it to the own server, e.g.
nuget push microsoft.web.librarymanager.build.2.0.76.nupkg -src http://localhost
Expected result
Package should be pushed to the NuGet Server.
Actual result
Error message in client:
Return code 406 (Not Acceptable)
Error message in log file of the server:
w3wp.exe Error: 0 : System.InvalidOperationException: Package does not contain a manifest.
bei NuGet.PackageHelper.GetManifestStream(Stream packageStream)
bei NuGet.OptimizedZipPackage.EnsureManifest()
bei NuGet.Server.Core.PackageFactory.Open(String fullPackagePath)
bei NuGet.Server.V2.Controllers.NuGetODataController.<UploadPackage>d__16.MoveNext()
...
- Dominant language
- C#
- Stars
- 486
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aspnet/LibraryManager
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aspnet/LibraryManager#824 · 1 comment · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
aspnet/LibraryManager#804 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
aspnet/LibraryManager#829 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/LibraryManager#820 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aspnet/LibraryManager#808 · 5 comments ·
All issues in aspnet/LibraryManager
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-azurefunctions#5197 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/microsoft-ui-reactor#1274 ·