mirror of
https://github.com/quamotion/dotnet-packaging.git
synced 2026-02-15 21:35:27 +00:00
Cannot package before publish. #53
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @claunia on GitHub (Jun 21, 2019).
@qmfrederik oh you here also! 😃
May be related to #90 and #97, even a duplicate, not entirely sure.
Solution is a aspdotnetcore 2.2 package with a netcoreapp2.2 library.
Nuget for packaging added only to the main package.
If I add it to the library also:
They just stop there
Now, if I do
first, then
in the first case it keeps complaining about CreateDeb missing, but continues.
in the second case, no complains or warnings, it just works.
@claunia commented on GitHub (Jun 21, 2019):
Also if I publish with two different RIDs (or a dozen), creating the package only works with the latest published RID.
@qmfrederik commented on GitHub (Jun 24, 2019):
@claunia It's a small world indeed 😄
Yes, I think this is a variant of the other issues, in that you need to do a restore before you can run
dotnet deb.We should probably update the .NET utilities to do an implicit restore if required. That should fix these issues.
For multiple RIDs, that's odd, because we use it to publish to different RIDs all the time.
Do you have a small sample project you can share?
@claunia commented on GitHub (Jun 24, 2019):
Unfortunately I don't have a small project, but it's easy to check:
Ubuntu 16.04 .deb generation fails, only 18.04 is generated.
Meanwhile
Both .deb packages are generated correctly.
@qmfrederik commented on GitHub (Nov 22, 2019):
@claunia If you're still into this, can you give the latest version a try? You should no longer be required to run
dotnet restoreordotnet publishbefore runningdotnet deb, but it would be good to get confirmation 😄