Zip files with same Relative File Path but different Aliases are combined across Installers
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Reproduce the issue with the provided wingetcreate update command and inspect how NestedInstallerFiles entries are grouped across the x64 and arm64 installer nodes. Verify that entries sharing a relative path but having different aliases remain within their original installer node, then confirm manifest validation succeeds.
Written by the indexing model from the issue text.
Description
Brief description of your issue
The latest manifest for Microsoft.DSC has an x64 portable zip installer and an arm64 portable zip installer. Both reference the same relative file path for the executable, but the portable command alias is different. When running wingetcreate update the entries get combined causing validation to fail
... (x64)
NestedInstallerFiles:
- RelativeFilePath: dsc.exe
PortableCommandAlias: dsc
... (arm64)
NestedInstallerFiles:
- RelativeFilePath: dsc.exe
PortableCommandAlias: dscarm64
Result after wingetcreate update:
... (x64)
NestedInstallerFiles:
- RelativeFilePath: dsc.exe
PortableCommandAlias: dsc
- RelativeFilePath: dsc.exe
PortableCommandAlias: dscarm64
... (arm64)
NestedInstallerFiles:
- RelativeFilePath: dsc.exe
PortableCommandAlias: dsc
- RelativeFilePath: dsc.exe
PortableCommandAlias: dscarm64
Steps to reproduce
wingetcreate update Microsoft.DSC --version 3.2.0 --urls 'https://github.com/PowerShell/DSC/releases/download/v3.2.0/DSC-3.2.0-x86_64-pc-windows-msvc.zip' 'https://github.com/PowerShell/DSC/releases/download/v3.2.0/DSC-3.2.0-aarch64-pc-windows-msvc.zip' 'https://github.com/PowerShell/DSC/releases/download/v3.2.0/DSC-3.2.0-Win.msixbundle'
Expected behavior
Entries would be preserved per installer node
Actual behavior
Entries are combined
Environment
Windows Package Manager Manifest Creator v1.12.8.0
Copyright (c) Microsoft Corporation. All rights reserved.
Operating System: Microsoft Windows NT 10.0.26200.0
System Architecture: X64
Winget-Create Directories Path
------------------------------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.WindowsPackageManagerManifestCreator_8wekyb3d8bbwe\LocalState\DiagOutputDir
User settings %LOCALAPPDATA%\Packages\Microsoft.WindowsPackageManagerManifestCreator_8wekyb3d8bbwe\LocalState\settings.json
Installer cache %TEMP%\wingetcreate
- 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 ·