Open whyleee opened 8 months ago
@FlorianRappl does this ring a bell for you?
No - it also seems to be exclusive to AngleSharp.Diffing
.
If standard publish to NuGet.org works then I wonder if the issue might actually be with the NuGet feed of AppVeyor? Why open the bug here?
The issue seems to be with older NuGet tools which are most probably upgraded in NuGet.org. The similar https://github.com/dotnet/aspnet-api-versioning/issues/637 issue also mentioned NuGet Package Explorer didn't work at the time, although the latest version works for me.
//LICENSE
inclusion in [Content_Types].xml
looks like an error in NuGet package that may be tolerated by some NuGet tools.
I see AngleSharp
and AngleSharp.Css
NuGet packages doesn't include LICENSE
file, but AngleSharp.Diffing
includes it. Does it makes sense to exclude this LICENSE
file? This will align this package with others and fix support for older NuGet tools.
Yeah I think that should be possible - but its up to @egil (the other projects still refer to the license via the URL etc.).
Also maybe it makes sense now to release a 1.0 with a reference to AngleSharp 1.0 and the AngleSharp.Css 1.0 preview package?
Yeah I think that should be possible - but its up to @egil (the other projects still refer to the license via the URL etc.).
I have no preference here. Think you set up the deployment and build stuff here too, so I'm happy to be in sync with what the other anglesharp libs are doing.
Also maybe it makes sense now to release a 1.0 with a reference to AngleSharp 1.0 and the AngleSharp.Css 1.0 preview package?
Is it allow to release a none preview package that depends on a preview package? Or is it just frowned upon?
If we are allowed to do so, then it's fine with me.
If we are allowed to do so, then it's fine with me.
You mean technically allowed? I think it is - it should be. We can just try.
Let's try.
Can you help sync the build stuff to this repo. I have not used this setup before.
Yeah but not this week. I have time for this next week.
I'll take care of it - let's assign me here.
Thank you Florian, much appreciated!
Bug Report
Prerequisites
AngleSharp.Css
for CSS support)For more information, see the
CONTRIBUTING
guide.Description
We get a NuGet error when pushing latest "anglesharp.diffing.0.18.2.nupkg" package to our private NuGet feed in AppVeyor:
I found exactly same issue with another package: https://github.com/dotnet/aspnet-api-versioning/issues/637.
[Content_Types].xml
file in "anglesharp.diffing.0.18.2.nupkg" package has the same problem withLICENSE
file:Looking into another AngleSharp package "anglesharp.css.0.17.0" (also latest version)
[Content_Types].xml
file contents doesn't reveal this issue:Could you please fix NuGet package build, so it produces the valid metadata?
Steps to Reproduce
We use AppVeyor NuGet
Push-AppveyorArtifact
helper to push NuGet packages to the private feed (https://www.appveyor.com/docs/packaging-artifacts/#pushing-artifacts-from-scripts):More simple way to test:
[Content_Types].xml
file in the extracted folderExpected behavior: no
<Override PartName="//LICENSE" ContentType="application/octet" />
element.Actual behavior:
<Override PartName="//LICENSE" ContentType="application/octet" />
is present and breaks NuGet push.Environment details: reproduced at least in current AppVeyor environment that pushes NuGet packages with
Push-AppveyorArtifact
PowerShell cmdlet.Possible Solution
AngleSharp
andAngleSharp.Css
NuGet packages are ok - it seemsAngleSharp.Diffing
build script could be aligned with those projects to fix the issue.