update/new does not work when additional architecture are added for a package
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by running the reported wingetcreate update and new commands with the two talosctl Windows URLs to reproduce the failures. Trace the update/new command paths involved in package identifiers and architecture handling. Done means the manifest is updated with the additional architecture instead of either command failing with the reported errors.
Written by the indexing model from the issue text.
Description
Brief description of your issue
wingetcreate update/new does not work when additional architecture are added for a package
Steps to reproduce
Update
wingetcreate update --out $env:TEMP -t <token> https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-amd64.exe https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-arm64.exe
Fails with:
Version https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-arm64.exe does not exist for https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-amd64.exe in the Windows Package Manager repository.
New
wingetcreate new --out $env:TEMP -t <token> https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-amd64.exe https://github.com/siderolabs/talos/releases/download/v1.9.0/talosctl-windows-arm64.exe
Fails with:
We have detected that this package identifier already exists. If you intend to update an existing package, please use the update command.
Expected behavior
Wingetcreate should update the manifest and add in the new architecture
Actual behavior
Wingetcreate fails to update package
Environment
Windows Package Manager Manifest Creator v1.9.2.0
- Dominant language
- C#
- Stars
- 651
- Forks
- 114
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 3
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.
More from microsoft/winget-create
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/winget-create#705 ·
-
Issue-Feature Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/winget-create#680 ·
-
Duplicate Surfacing workflow fails on every run with "Blocked compile-agentic version: v0.83.4" OpenNeeds-Triage
Difficulty 3/5 1-2 days Newbie friendliness 68/100
microsoft/winget-create#706 ·
-
Issue-Feature Needs-Triage
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/winget-create#701 ·
-
Issue-Feature Needs-Triage
Difficulty 3/5 1-2 days Newbie friendliness 68/100
microsoft/winget-create#700 ·
All issues in microsoft/winget-create
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·