When creating a package, the Title field's value is not respected at creation time.
What is Expected?
Whatever is entered in the Title field within Package Builder or passed with the Title=<value> option when running choco new should appear between the title tags in the .nuspec file, and passed accordingly to the Name and Package Title fields in Chocolatey Central Management.
How Did You Get This To Happen? (Steps to Reproduce)
Right-click an installer and select Create Chocolatey package...
Fill out the Title field with anything
Select Generate
Open the .nupkg and view the .nuspec
Title will be Package ID and (Install) instead of the value entered before compiling
Alternatively, Stephen provided code to the customer:
choco new --file='C:\temp\7zip_x64.msi' --build-package --output-directory='c:\temp' Title='7zip'
This ended up providing the same result as the above step using Package Builder, as evidenced in the ticket.
System Details
Operating System: Server 2022
Windows PowerShell Version: 5.1
Chocolatey CLI Version: 2.2.2
Chocolatey Licensed Extension version: 6.1.3
Chocolatey License type (Professional / Business / ?): BusinessTrial
Terminal/Emulator:
Output Log
N/A
Workarounds
After the package is created, you can open the .nupkg and edit the .nuspec file between the title tags with anything you want and save it, then install the package and this will appear as intended when the machine checks in to CCM.
What You Are Seeing?
When creating a package, the Title field's value is not respected at creation time.
What is Expected?
Whatever is entered in the Title field within Package Builder or passed with the
Title=<value>option when runningchoco newshould appear between the title tags in the .nuspec file, and passed accordingly to the Name and Package Title fields in Chocolatey Central Management.How Did You Get This To Happen? (Steps to Reproduce)
Alternatively, Stephen provided code to the customer:
choco new --file='C:\temp\7zip_x64.msi' --build-package --output-directory='c:\temp' Title='7zip'This ended up providing the same result as the above step using Package Builder, as evidenced in the ticket.
System Details
Output Log
N/A
Workarounds
After the package is created, you can open the .nupkg and edit the .nuspec file between the title tags with anything you want and save it, then install the package and this will appear as intended when the machine checks in to CCM.
Related Issues and Tickets
Zendesk Ticket 21438
┆Issue is synchronized with this Gitlab issue by Unito