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

[Update Request]: Python.Python.3.12 has incorrect metadata #151688

Open
Trenly opened this issue Apr 30, 2024 · 2 comments
Open

[Update Request]: Python.Python.3.12 has incorrect metadata #151688

Trenly opened this issue Apr 30, 2024 · 2 comments
Labels
Help-Wanted This is a good candidate work item from the community. Package-Metadata

Comments

@Trenly
Copy link
Contributor

Trenly commented Apr 30, 2024

What type of update are you requesting?

A change to the package metadata

Current Package Identifier

Python.Python.3.12

Package Version

3.12.0

Please describe the changes you would like to see

@SpecterShell - seems an update from Dumplings inserted some invalid AppsAndFeaturesEntries

@Trenly Trenly added Help-Wanted This is a good candidate work item from the community. Package-Update This package needs to be updated labels Apr 30, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage This work item needs to be triaged by a member of the core team. Package-Metadata and removed Package-Update This package needs to be updated Needs-Triage This work item needs to be triaged by a member of the core team. labels Apr 30, 2024
@SpecterShell
Copy link
Contributor

If you mean the & and the * in the installer manifest:

& is the anchor that defines the chunk and * is the alias that refer to those chunks. Both of them are part of YAML grammar.
Previously when generating the manifest, the same AppsAndFeaturesEntry object was assigned to both the user scope and the machine scope of installer entries, causing ConvertTo-Yaml to use anchor and alias for them. Anyway this feature has been disabled since then.

If you mean Python 2 is treated as Python 3.12 by WinGet client:

image
It seems to be a bug from WinGet that it can not distinguish Python 2 from Python 3.4 even if I have added UpgradeCode to Python 2 some days ago. For me after WinGet failed to distinguish it simply use Python 3.12 from install records for Python 2, and since they have different install technologies it can never be updated.

2024-04-30 22:25:56.887 [REPO] Found multiple matches for installed package [{A5F504DF-2ED9-4A2D-A2F3-9D2750DD42D6}] in source [Microsoft.Winget.Source_8wekyb3d8bbwe] when searching for [Query:[none] Include:ProductCode='{a5f504df-2ed9-4a2d-a2f3-9d2750dd42d6}'[Exact] Include:UpgradeCode='{6a965a0c-6ee6-4e3a-9983-3263f56311ec}'[Exact] Include:NormalizedNameAndPublisher='python'+'pythonsoftwarefoundation'[Exact] Include:NormalizedNameAndPublisher='python(x64)'+'pythonsoftwarefoundation'[Exact]]
2024-04-30 22:25:56.887 [REPO]   Checking match with package id: Python.Python.2
2024-04-30 22:25:56.887 [REPO]   Checking match with package id: Python.Python.3.4
2024-04-30 22:25:56.887 [REPO]   Found multiple packages with strong match fields
2024-04-30 22:25:56.887 [REPO]   Appropriate available package could not be determined
2024-04-30 22:25:56.887 [REPO]  ... using tracking package: Python.Python.3.12
2024-04-30 22:25:56.887 [REPO] Performing search: Query:[none] Filter:Id='Python.Python.3.12'[CaseInsensitive]
2024-04-30 22:25:56.894 [REPO]  ... adding available package: Python.Python.3.12

@Trenly
Copy link
Contributor Author

Trenly commented May 1, 2024

If you mean the & and the * in the installer manifest:

& is the anchor that defines the chunk and * is the alias that refer to those chunks. Both of them are part of YAML grammar. Previously when generating the manifest, the same AppsAndFeaturesEntry object was assigned to both the user scope and the machine scope of installer entries, causing ConvertTo-Yaml to use anchor and alias for them. Anyway this feature has been disabled since then.

Yeah, this is what I was referring to; I'm a bit skeptical that WinGet processes it correctly, but perhaps it does

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help-Wanted This is a good candidate work item from the community. Package-Metadata
Projects
None yet
Development

No branches or pull requests

2 participants