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

Malwarebytes.Malwarebytes version 4.4.6.232 #30069

Closed
wants to merge 2 commits into from
Closed

Malwarebytes.Malwarebytes version 4.4.6.232 #30069

wants to merge 2 commits into from

Conversation

GarethTheNerd
Copy link
Contributor

@GarethTheNerd GarethTheNerd commented Oct 11, 2021

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


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-Domain Policy-Test-2.8 Needs-Attention This work item needs to be reviewed by a member of the core team. labels Oct 11, 2021
@ghost ghost assigned jamespik Oct 11, 2021
@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Oct 12, 2021
…alwarebytes.locale.en-US.yaml


Change version number

Co-authored-by: Levvie - she/her <[email protected]>
@ghost ghost removed Needs-Author-Feedback This needs a response from the author. Validation-Domain Needs-Attention This work item needs to be reviewed by a member of the core team. Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Policy-Test-2.8 labels Oct 12, 2021
@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

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.

You'll have to update the version folder as well, otherwise, the package will not pass pipelines.

@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Oct 12, 2021
@wingetbot wingetbot added the Manifest-Validation-Error Manifest validation failed label Oct 12, 2021
@ghost
Copy link

ghost commented Oct 12, 2021

Hello @GarethTheNerd,
The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.0 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode (https://code.visualstudio.com/) to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator Preview.

For details on the specific error, see the details link below in the build pipeline.

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

PackageIdentifier: Malwarebytes.Malwarebytes
PackageVersion: 4.4.6.232
Copy link
Contributor

Choose a reason for hiding this comment

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

Malwarebytes have some weird versioning so the url and ARP dosn't match

Suggested change
PackageVersion: 4.4.6.232
PackageVersion: 4.4.8.137

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

PackageIdentifier: Malwarebytes.Malwarebytes
PackageVersion: 4.4.6.232
Copy link
Contributor

Choose a reason for hiding this comment

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

Malwarebytes have some weird versioning so the url and ARP dosn't match

Suggested change
PackageVersion: 4.4.6.232
PackageVersion: 4.4.8.137

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

PackageIdentifier: Malwarebytes.Malwarebytes
PackageVersion: 4.4.6.232
Copy link
Contributor

Choose a reason for hiding this comment

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

Malwarebytes have some weird versioning so the url and ARP dosn't match

Suggested change
PackageVersion: 4.4.6.232
PackageVersion: 4.4.8.137

Architecture: x86
InstallerType: exe
Scope: machine
InstallerUrl: https://data-cdn.mbamupdates.com/web/mb4-setup-consumer/offline/mb4-setup-consumer-4.4.6.232-1.0.1474-1.0.45650.exe
Copy link
Contributor

Choose a reason for hiding this comment

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

We have had multiple issues with this link and i'm pretty sure i remember the previous installer getting removed once the new version is releases which is why we use the redirect url

Suggested change
InstallerUrl: https://data-cdn.mbamupdates.com/web/mb4-setup-consumer/offline/mb4-setup-consumer-4.4.6.232-1.0.1474-1.0.45650.exe
InstallerUrl: https://data-cdn.mbamupdates.com/web/mb4-setup-consumer/MBSetup.exe

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks. Those links fail to install for me on multiple machines. I believe that is the online installer. Not sure if the upgrade behaviour needs to be changed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will look into it later 🙂

Copy link
Contributor

Choose a reason for hiding this comment

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

I thiiiiiiink i found a redirect url for the offline installer, but people reported issues on that one too..
This is the first time i've heard people have issues with the Online installer, would you mind posting a issue next time?

Currently the upgrade behavior is Install which runs the installer with the silent argument, the other upgrade behavior we can use is uninstallPrevious which uninstall the software then runs the installer with the silent argument, if Malwarebytes have a different upgrade switch you can add that under InstallerSwitches as Upgrade: <argument>

Copy link
Contributor

@OfficialEsco OfficialEsco Oct 12, 2021

Choose a reason for hiding this comment

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

Ahh yeah this is the redirect link https://downloads.malwarebytes.com/file/mb4_offline to the offline installer

@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 12, 2021
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.

#30069 (comment)

You can set the PR in DRAFT mode until you've made changes to the package.

@ghost ghost added the Needs-Author-Feedback This needs a response from the author. label Oct 13, 2021
@GarethTheNerd GarethTheNerd marked this pull request as draft October 13, 2021 09:04
@ghost ghost removed the Needs-Author-Feedback This needs a response from the author. label Oct 13, 2021
@OfficialEsco
Copy link
Contributor

I've updated Malwarebytes to 4.4.8.137 so you can maybe test winget upgrade if you haven't updated yet? And report a problem if there is one.
If you find a better url you can just update the URL in the new manifest :)

@ghost ghost mentioned this pull request Nov 6, 2021
@ghost ghost closed this in #34173 Nov 6, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Manifest-Validation-Error Manifest validation failed Needs-Attention This work item needs to be reviewed by a member of the core team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants