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

D4koon.WhatsappTray version 1.9.0.0 #82559

Conversation

medvedev125
Copy link
Contributor

@medvedev125 medvedev125 commented Oct 5, 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.2 schema?

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


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

@medvedev125
Copy link
Contributor Author

@microsoft-github-policy-service agree

@medvedev125
Copy link
Contributor Author

There is a related feature request in WhatsappTray project: D4koon/WhatsappTray#145

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

ghost commented Oct 6, 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 Oct 6, 2022

medvedev125,

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.

Template: msftbot/requiresApproval/moderator

- Architecture: x64
InstallerType: inno
InstallerUrl: https://github.com/D4koon/WhatsappTray/releases/download/v1.9.0/WhatsappTrayV1.9.0.0.exe
InstallerSha256: 6535FA20F12FD21C0ABD104E5594D4F0AE82528D4274D3470D9C1FBB3C403A18
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
InstallerSha256: 6535FA20F12FD21C0ABD104E5594D4F0AE82528D4274D3470D9C1FBB3C403A18
InstallerSha256: 6535FA20F12FD21C0ABD104E5594D4F0AE82528D4274D3470D9C1FBB3C403A18
ProductCode: "{1237D679-445B-4101-B7EC-B5081C5FA4A3}_is1"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Why we should add the ProductCode field? Where do you get this ID? And why "_is1"?
There is not in manifest of other apps. For example: https://github.com/microsoft/winget-pkgs/blob/master/manifests/w/WhatsApp/WhatsApp/2.2236.10/WhatsApp.WhatsApp.installer.yaml

I created this commit with the wingetcreate util. And if this field is obligated, than it's a bug in the wingetcreate.

Copy link
Contributor

@ItzLevvie ItzLevvie Oct 6, 2022

Choose a reason for hiding this comment

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

Why we should add the ProductCode field?

It's required for this package because the developer didn't add the publisher for this application.

It's used so that WinGet can properly map the application to winget list and make winget upgrade work.

You can take a look at https://github.com/microsoft/winget-pkgs/blob/master/doc/manifest/schema/1.2.0/installer.md

winget-create already does the ProductCode automatically for MSI installers, but for EXE installers, there's really no easy way other than to install the application to a virtual machine (VM) and monitoring the Windows Registry.

Where do you get this ID?

It's taken from the Windows Registry.

You can take a look at https://github.com/ItzLevvie/winget-pkgs-validate-and-install/blob/f4db043f8c11953c96c7976b90ec486f992933f6/Community%20Moderators%20-%202022-10-02%20-%20development.ps1#L185-L200

And why "_is1"?

That's just what Inno Setup does — which is what this application is wrapped around with to create an installer.

@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Oct 6, 2022
@ghost ghost assigned medvedev125 Oct 6, 2022
@ghost
Copy link

ghost commented Oct 6, 2022

Hello @medvedev125,

The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

@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 Oct 6, 2022
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.

Please see #82559 (comment)

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

ghost commented Oct 6, 2022

Hello @medvedev125,

The package manager bot determined changes have been requested to your PR.

Template: msftbot/changesRequested

@ItzLevvie
Copy link
Contributor

Close with reason: Replaced by PR 82817 to avoid having the pull request be stale;

@ghost ghost closed this Oct 8, 2022
@ghost ghost removed Needs-Attention This work item needs to be reviewed by a member of the core team. Needs-Author-Feedback This needs a response from the author. labels Oct 8, 2022
This pull request was closed.
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. Validation-Completed Validation passed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants