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

Swift.Toolchain 5.5.3 #46123

Closed
wants to merge 2 commits into from
Closed

Swift.Toolchain 5.5.3 #46123

wants to merge 2 commits into from

Conversation

svanimpe
Copy link

@svanimpe svanimpe commented Feb 14, 2022

  • Have you signed the Contributor License Agreement?
  • Have you checked that there aren't other open pull requests for the same manifest update/change?
  • Have you validated your manifest locally with winget validate --manifest <path>?
  • Have you tested your manifest locally with winget install --manifest <path>?
  • Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.


I've generated these using YamlCreate and the manifest version is 1.1.0 instead of 1.0. I assume that's OK?

Microsoft Reviewers: Open in CodeFlow

@wingetbot
Copy link
Collaborator

Service Badge  Service Badge  

@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wingetbot wingetbot added Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed labels Feb 14, 2022
@ghost
Copy link

ghost commented Feb 14, 2022

Hello @wingetbot!

Because this pull request has the Validation-Completed label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost
Copy link

ghost commented Feb 14, 2022

@svanimpe,

The check-in policies require a moderator to approve PRs from the community.

Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission.

Copy link
Contributor

@OfficialEsco OfficialEsco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ohhnooo this installer writes the wrong version to the registry 🤦‍♂️

Name        : Swift
Publisher   : dt.compnerd.org
Version     : 0.0.0.0
ProductCode : {51a6ef4e-285a-44fe-8f21-cdf5a6ee7245}
Uninstall   : winget uninstall --id "{51a6ef4e-285a-44fe-8f21-cdf5a6ee7245}"

Hmm, this is a Burn installer, would this be something one of you guys fix? @jedieaston @Trenly

# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.1.0.schema.json

PackageIdentifier: Swift.Toolchain
PackageVersion: 5.5.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
PackageVersion: 5.5.3
PackageVersion: 0.0.0.0

# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.1.0.schema.json

PackageIdentifier: Swift.Toolchain
PackageVersion: 5.5.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
PackageVersion: 5.5.3
PackageVersion: 0.0.0.0

# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.1.0.schema.json

PackageIdentifier: Swift.Toolchain
PackageVersion: 5.5.3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
PackageVersion: 5.5.3
PackageVersion: 0.0.0.0

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I ask what exactly this does? I assume it's a workaround, and not the value we actually want here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, or is this a version number exposed by the installer (I'm not the maintainer of this installer), as explained here: #28544 (comment)

@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Feb 15, 2022
@jedieaston
Copy link
Contributor

Ohhnooo this installer writes the wrong version to the registry 🤦‍♂️

Name        : Swift
Publisher   : dt.compnerd.org
Version     : 0.0.0.0
ProductCode : {51a6ef4e-285a-44fe-8f21-cdf5a6ee7245}
Uninstall   : winget uninstall --id "{51a6ef4e-285a-44fe-8f21-cdf5a6ee7245}"

Hmm, this is a Burn installer, would this be something one of you guys fix? @jedieaston @Trenly

I looked into it last week. I spent like an hour trying to figure out how the heck the build scripts work but didn't get anywhere (it's like three repos, one of which is private so I can't see if they expose the version number to msbuild anywhere). If someone could drop something in the mailing list I bet they'd fix it.

@ghost ghost added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. labels Feb 18, 2022
@svanimpe
Copy link
Author

If I may also ask for some advice: Am I following the correct procedure here for patch version upgrades? That is: Should I create them as new versions with new manifests? Or should I edit the existing 5.5 manifest to point to 5.5.3? I'm not sure how the updater works, so I figured it may be best to create a new manifest for each version.

@OfficialEsco
Copy link
Contributor

If I may also ask for some advice: Am I following the correct procedure here for patch version upgrades? That is: Should I create them as new versions with new manifests? Or should I edit the existing 5.5 manifest to point to 5.5.3? I'm not sure how the updater works, so I figured it may be best to create a new manifest for each version.

You should create a new Manifest for each version yes, if it Auto updates you CAN delete and create a new manifest for the new version in the same PR (will be counted as Move and Modify as long as its in the same Software folder)

But we only do that for urls that don't contain versions like Spotify
Since we can't remember every software that auto updates its best to make a brand new manifest for urls with versions

@denelon denelon removed the Needs-Attention This work item needs to be reviewed by a member of the core team. label Feb 18, 2022
@denelon
Copy link
Contributor

denelon commented Feb 18, 2022

It looks like we have 5.5 as the latest version in the repository currently. Unfortunately, without the package properly reporting the version to Windows Apps & Features, the Windows Package Manager would not be able to recognize this as an upgrade.

@OfficialEsco what are your thoughts about PRs like this where the package doesn't report the correct version, or doesn't report one at all? Should we block on the related issue below? It's the feature where the client begins to understand the "AppsAndFeatures" entry in the manifest.

What additional label would make sense in that case? "Version" or "Apps-and-Features"? or something like that?

Related to:

@OfficialEsco
Copy link
Contributor

Yeah that makes sense, DisplayVersion-Isssue might be clearer than Apps-and-Features as Apps-and-Features issues can be solved by ProductCodes

@denelon denelon added Blocking-Issue Manifest validation is blocked by a known issue. Display-Version labels Feb 18, 2022
@denelon
Copy link
Contributor

denelon commented Feb 18, 2022

Sorry for the noise to come. I'm testing some additional automation.

@ghost
Copy link

ghost commented Feb 18, 2022

svanimpe,

This package does not report a version in Windows Apps & Features, or it reports an incorrect version.

This PR is blocked until support for correlation between values in Windows Apps & Features is supported:

@ghost
Copy link

ghost commented Feb 18, 2022

@svanimpe,

This package does not report a version in Windows Apps & Features, or it reports an incorrect version.

This PR is blocked until support for correlation between values in Windows Apps & Features is supported:

Copy link
Contributor

@ItzLevvie ItzLevvie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this PR still needed?

Developers of the Swift Toolchain have fixed their MSI version in latest releases: #57288

@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label May 3, 2022
@svanimpe
Copy link
Author

svanimpe commented May 3, 2022

I was unaware this had been fixed. So yes, we can close this!

@svanimpe svanimpe closed this May 3, 2022
@ghost ghost added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. labels May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Blocking-Issue Manifest validation is blocked by a known issue. Needs-Attention This work item needs to be reviewed by a member of the core team. Validation-Completed Validation passed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants