-
Notifications
You must be signed in to change notification settings - Fork 684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Normalize readme entry path prior to extraction #727
Comments
+1 Edit: |
loic-sharma#727: Normalize readme entry path prior to extraction
Is there any progress? Due to this issue, the package cannot be restored |
I currently run into this issue. I found out that, for example, packages mimekit.4.2.0 and mailkit.4.2.0 run into this issues. Therefor I cannot restore my projects in a docker container for deployment anymore. |
I use BaGet as a NuGet mirror and I get the same issues when getting some packages from NuGet. |
There is a fork, that is fairly maintained and seems to be active with merging pull requests: BaGetter. Last commit is pretty recent and adds dotnet 8 support. I haven't migrated to it yet, having a locally built image with required fixes, so can't say from experience about it's stability, but the issue with the "readme" paths is solved there. |
Thanks for your reply @SergeyFilippov ! |
The packages with "\" character in readme node cannot be pushed to BaGet on Linux.
Similar to the issue #517 it is impossible to push a package with "\" character inside of "readme" node of nuspec file.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It is possible to upload or download this kind of packages.
The text was updated successfully, but these errors were encountered: