fsprojects / fsprojects/Paket

Can't run dotnet pack with sources/symbols when project uses Paket

Open
#2,689 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug sdk: dotnet/sdk up-for-grabs
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

I get an error when running dotnet pack with the --include-symbols and --include-source arguments.

\.paket\Paket.Restore.targets(100,5): error : The given path's format is not supported.

Everything works when dropping these arguments.
One strange thing that also happens is that if you build it with the arguments then the build without arguments also fails until you delete the symbols.nuspec file in the obj folder.

Repro steps

Repro:
PaketRepro.zip

  1. Extract the repo and go to the root Stuff.Repro
  2. Run dotnet pack --include-symbols or dotnet pack --include-source
Expected behavior

The command should output a nuget package for the project and one for the symbols

Actual behavior

Throws error \.paket\Paket.Restore.targets(100,5): error : The given path's format is not supported.

Known workarounds

None

Environment

Paket version: 5.91.0
.Net SDK version: 2.0.0
OS: Windows 10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce from the linked PaketRepro.zip in the Stuff.Repro root using dotnet pack --include-symbols and --include-source. Inspect .paket/Paket.Restore.targets around line 100 and the generated symbols.nuspec in obj. Done means both packages are produced without the path-format error, and a later pack without those options still works without manually deleting symbols.nuspec.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.