-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
New version: ArtifexSoftware.GhostScript version 10.02.0 #119663
New version: ArtifexSoftware.GhostScript version 10.02.0 #119663
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
f2413b9
to
13bd141
Compare
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
vedantmgoyal2009, 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 |
Hello @vedantmgoyal2009, The package manager bot determined there was an issue with the pull request. Make sure the manifest files are under the manifests\partition\publisher\appname\version directory and only one package version is being modified in your PR. The partition of the path must be the first letter of the publisher in lower-case. Example: For details on the error, see the details link below in the build pipeline. You may also try the Windows Package Manager Manifest Creator Template: msftbot/validationError/pullRequest |
/AzurePipelines run |
…daoDict.installer.yaml
Azure Pipelines successfully started running 1 pipeline(s). |
…daoDict.locale.zh-CN.yaml
/AzurePipelines run |
1 similar comment
/AzurePipelines run |
manifests/a/ArtifexSoftware/GhostScript/10.02.0/ArtifexSoftware.GhostScript.installer.yaml
Outdated
Show resolved
Hide resolved
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @vedantmgoyal2009, During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches? This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest. Please investigate a fix and resubmit the Pull Request. You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress. Template: msftbot/validationError/installation/unattended |
@vedantmgoyal2009, |
Hello @vedantmgoyal2009, This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. Template: msftbot/noRecentActivity |
No it is not. Since version 10.01.0 they disabled (because of security reasons) the silent install option (Source: https://artifex.com/news/ghostscript-10.01.0-disabling-silent-install-option). But it is essential that people wont install version 10.0.0 as main version because < 10.02.0 have massive vulnerabilities that allows remote code execution. (CVE-2023-43115) |
Pull request has been created with WinGet Automation 🚀