Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Title Field Ignored When Creating Packages with Package Builder and with Choco New Command #384

Open
sync-by-unito bot opened this issue Mar 14, 2024 · 1 comment
Labels
0 - Backlog Where tickets start after being triaged. This means the ticket has targeted milestone/labels. Bug Tickets that represent defects/bugs. Customer LicensedExtension Issues affecting the Chocolatey Licensed Extension (chocolatey.extension)

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Mar 14, 2024

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 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)

  1. Right-click an installer and select Create Chocolatey package...
  2. Fill out the Title field with anything
  3. Select Generate
  4. Open the .nupkg and view the .nuspec
  5. 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.

Related Issues and Tickets

Zendesk Ticket 21438
Zendesk Ticket 23040

┆Issue is synchronized with this Gitlab issue by Unito

@sync-by-unito sync-by-unito bot added 0 - Backlog Where tickets start after being triaged. This means the ticket has targeted milestone/labels. Bug Tickets that represent defects/bugs. LicensedExtension Issues affecting the Chocolatey Licensed Extension (chocolatey.extension) labels Mar 14, 2024
@pauby pauby added the Customer label Mar 14, 2024
@IvanMagd
Copy link

IvanMagd commented Jul 3, 2024

Owner field is ignored also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - Backlog Where tickets start after being triaged. This means the ticket has targeted milestone/labels. Bug Tickets that represent defects/bugs. Customer LicensedExtension Issues affecting the Chocolatey Licensed Extension (chocolatey.extension)
Projects
None yet
Development

No branches or pull requests

2 participants