nuget.exe pack with both -symbols and -suffix give incorrect name to symbol package
Open
Nobody has claimed this yet.
Functionality:Pack
help wanted
Priority:2
Type:Bug
- Dominant language
- HTML
- Stars
- 1.6k
- Forks
- 276
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 1
Description
Steps
- Create a .nuspec on disk.
- Make sure there are some files to pack (
nuget.exe packwon't make an empty package). - Run
nuget.exe pack path\to\my.nuspec -symbols -suffix beta
Expected
Two nupkgs, one ending in beta.nupkg and the other ending in beta.symbols.nupkg.
Actual
The symbols package's file name has the version number without the suffix. The .nuspec inside the package seems fine though.
Example
nuget.exe pack VS.Redist.NuGet_VS15.nuspec -symbols -suffix BETA
Attempting to build package from 'VS.Redist.NuGet_VS15.nuspec'.
Successfully created package 'C:\Users\jver\Desktop\foo\VS.Redist.NuGet_VS15.3.5.160923.1438-BETA.nupkg'.
Successfully created package 'C:\Users\jver\Desktop\foo\VS.Redist.NuGet_VS15.3.5.160923.1438-bar.symbols.nupkg'.
Tried on latest dev and 3.5.0-rc1.
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.
Research direction
Start by reproducing the issue with the provided nuget.exe pack ... -symbols -suffix BETA command and compare the two generated filenames. Trace the pack and symbols-package naming path used by this command; done means both output packages retain the suffix, including the .symbols.nupkg file.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100