Ansible
PS DSC
Downloads:
153
Downloads of v 1.16.1:
153
Last Update:
12 Jun 2019
Package Maintainer(s):
Software Author(s):
- Blizzard
Tags:
starcraft- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Mailing List
- Software Issues
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
starcraft (Install)
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Mailing List
- Software Issues
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
153
Downloads of v 1.16.1:
153
Maintainer(s):
Software Author(s):
- Blizzard
Tags:
starcraftstarcraft (Install)
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
This package was rejected on 02 Aug 2019. The reviewer chocolatey-ops has listed the following reason(s):
StarCraft is a military science fiction media franchise, created by Chris Metzen and James Phinney and owned by Blizzard Entertainment. The series, set in the beginning of the 26th century, centers on a galactic struggle for dominance among four species—the adaptable and mobile Terrans, the ever-evolving insectoid Zerg, the powerfully enigmatic Protoss, and the "god-like" Xel'Naga creator race—in a distant part of the Milky Way galaxy known as the Koprulu Sector. The series debuted with the video game StarCraft in 1998. It has grown to include a number of other games as well as eight novelizations, two Amazing Stories articles, a board game, and other licensed merchandise such as collectible statues and toys.
$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$toolsDir\commonEnv.ps1"
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = 'starcraft*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
}
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below
if ($packageArgs['fileType'] -eq 'MSI') {
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
$packageArgs['file'] = ''
} else {
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
Remove-Item $lnkDesktop -force
Remove-Item $startMenuDir -recurse -force
Get-ChildItem -Exclude characters,save "$installLocation" | Remove-Item -Recurse -Force
$installLocation = "$ENV:LocalAppData\Programs\StarCraft"
$lnkDesktop = "$ENV:UserProfile\Desktop\StarCraft.lnk"
$startMenuDir = "$ENV:AppData\Microsoft\Windows\Start Menu\Programs\StarCraft"
Log in or click on link to see number of positives.
- starcraft.zip (d33f76b80ebb) - ## / 59
- starcraft.zip (d6458497fae8) - ## / 59
- starcraft.1.16.1.nupkg (61ca87f54031) - ## / 59
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
This package has no dependencies.
Ground Rules:
- This discussion is only about starcraft (Install) and the starcraft (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or starcraft (Install), or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
n3rd4i (maintainer) on 29 May 2019 18:43:30 +00:00:
User 'n3rd4i' (maintainer) submitted package.
n3rd4i (maintainer) on 29 May 2019 18:44:20 +00:00:
User 'n3rd4i' (maintainer) submitted package.
n3rd4i (maintainer) on 29 May 2019 18:47:19 +00:00:
User 'n3rd4i' (maintainer) submitted package.
n3rd4i (maintainer) on 29 May 2019 18:52:21 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 29 May 2019 19:26:01 +00:00:
starcraft has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 29 May 2019 23:33:18 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/920a93707d81747592e3a023f8338e57 for details.
This is an FYI only. There is no action you need to take.
n3rd4i (maintainer) on 30 May 2019 11:39:49 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 30 May 2019 12:14:11 +00:00:
starcraft has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
n3rd4i (maintainer) on 30 May 2019 12:19:22 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 30 May 2019 12:54:29 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 30 May 2019 15:47:53 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/3392330f72d44f2a8ae0aec62661bcab for details.
This is an FYI only. There is no action you need to take.
n3rd4i (maintainer) on 01 Jun 2019 13:41:52 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 01 Jun 2019 14:16:10 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 01 Jun 2019 15:26:18 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/051407456000236a214df0d3a37e8434 for details.
This is an FYI only. There is no action you need to take.
gep13 (reviewer) on 06 Jun 2019 06:55:05 +00:00:
Can you change the download link to be https rather than http?
n3rd4i (maintainer) on 08 Jun 2019 17:11:30 +00:00:
User 'n3rd4i' (maintainer) submitted package.
n3rd4i (maintainer) on 08 Jun 2019 17:11:54 +00:00:
updated after review comments.
chocolatey-ops (reviewer) on 08 Jun 2019 17:45:05 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 08 Jun 2019 18:18:46 +00:00:
starcraft has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/6126f4ea7cf05c6215124310e3bc7dd1 for details.
The package status will be changed and will be waiting on your next actions.
n3rd4i (maintainer) on 09 Jun 2019 09:53:12 +00:00:
it is unclear to me why:
n3rd4i (maintainer) on 09 Jun 2019 10:14:54 +00:00:
running this in the test environment works as intended
n3rd4i (maintainer) on 09 Jun 2019 16:07:52 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 09 Jun 2019 16:42:41 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 09 Jun 2019 17:06:51 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/aa1fc8d1c096f93600126ac6a20940b9 for details.
This is an FYI only. There is no action you need to take.
n3rd4i (maintainer) on 09 Jun 2019 18:52:47 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 09 Jun 2019 19:28:18 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
n3rd4i (maintainer) on 09 Jun 2019 19:35:07 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 09 Jun 2019 20:08:24 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 09 Jun 2019 20:54:27 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/449c160b8a0a3c91aaa6b726eda1e486 for details.
This is an FYI only. There is no action you need to take.
Pauby (reviewer) on 10 Jun 2019 08:44:29 +00:00:
I'm concerned about the high number of viruses detected inside. Have you any insight into why this is?
Pauby (reviewer) on 10 Jun 2019 08:57:04 +00:00:
I forgot to add - Can you use a static CDN for your <iconUrl> - githack.com and jsdelivr.com are popular.
n3rd4i (maintainer) on 10 Jun 2019 10:34:02 +00:00:
That particular file I could exclude from the package installation
n3rd4i (maintainer) on 10 Jun 2019 10:34:33 +00:00:
Also, one could try to use a different official package which in turn is:
n3rd4i (maintainer) on 10 Jun 2019 10:57:04 +00:00:
User 'n3rd4i' (maintainer) submitted package.
n3rd4i (maintainer) on 10 Jun 2019 10:58:07 +00:00:
Updated based on review comments
n3rd4i (maintainer) on 10 Jun 2019 11:15:58 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 10 Jun 2019 11:51:41 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 10 Jun 2019 11:54:25 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/5684dcbbd778d8ef9075121bc4d18b79 for details.
This is an FYI only. There is no action you need to take.
n3rd4i (maintainer) on 10 Jun 2019 12:08:28 +00:00:
The following warnings are note relevant:
WARNING: '%localappdata%\Programs\StarCraft\StarCraft.exe,1' does not exist. A default icon will be used.
WARNING: '%localappdata%\Programs\StarCraft\StarCraft.exe,1' does not exist. A default icon will be used.
The "second" icon indication is a valid "command" for the bundled icons inside an executable.
IMO this should be allowed by the chocolatey installer and not warned, because it exists and is valid.
n3rd4i (maintainer) on 10 Jun 2019 12:08:50 +00:00:
not* relevant.
Pauby (reviewer) on 11 Jun 2019 09:51:17 +00:00:
Hi,
The icon I was referring to is the <iconUrl> inside your .nuspec file. Can you please see my previous mdoeration comment about it?
With regards to the virus scanning, all I'm looking for is to get it passing Virus Total (so however you want to do that). Alternatively if you can provide me with some information from the authors regarding it I can take a look.
I would suggest not using the 8GB version of the software unless that is the only way this can be done and you caveat the package description with those details.
Thanks.
n3rd4i (maintainer) on 11 Jun 2019 20:05:35 +00:00:
User 'n3rd4i' (maintainer) submitted package.
n3rd4i (maintainer) on 11 Jun 2019 20:14:07 +00:00:
The game icon based on review comments to png.
I've been in contact (by email) with the upstream package owners. They say there must be a false positives and they did not update the package in years. Even so they will look into the matter, I've sent them link to the virus scanner results.
2.1 Upstream source: https://iccup.com/sc_start.html
2.2 Contact page: https://iccup.com/en/contacts.html
I also believe that changing this to 8GB version wont work because:
I hope this clarify things a bit.
I don't know how to continue unless the admins/upstream-package-owners could do something about the package to remove the false positives?
chocolatey-ops (reviewer) on 11 Jun 2019 20:38:51 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...chocolatey-ops (reviewer) on 11 Jun 2019 22:15:45 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/f7f043e57e3b7d5264d9435c71878f5d for details.
This is an FYI only. There is no action you need to take.
Pauby (reviewer) on 12 Jun 2019 13:00:37 +00:00:
Hi,
I'm not sure I understand your comments regarding the <iconUrl>.
With regards to the virus scanning results I'm not happy passing this with so many scanners flagging malware. Hopefully the upstream maintainers can look into this and resolve.
n3rd4i (maintainer) on 12 Jun 2019 16:26:56 +00:00:
User 'n3rd4i' (maintainer) submitted package.
n3rd4i (maintainer) on 12 Jun 2019 16:49:19 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 12 Jun 2019 17:23:22 +00:00:
starcraft has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 12 Jun 2019 19:18:43 +00:00:
starcraft has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/6fe0fb51787eb7b5ed85e85fbf421520 for details.
This is an FYI only. There is no action you need to take.
mkevenaar (reviewer) on 17 Jun 2019 09:58:04 +00:00:
Hi,
could you verify that this is the official distibution point for Blizzard Entertainment's Starcraft? I haven't checked the full package.
n3rd4i (maintainer) on 17 Jun 2019 18:26:35 +00:00:
This is NOT the official distribution point for StarCraft. As I've stated in my previous comments:
Now maybe there could be some hacky way with AutoHotkey to bypass such installation but some time needs to be spent with this which I want to avoid if this is possible for the 3 reasons I've already stated before.
None of those problem exists with this "slim-version-package". The only problem stated also by previous reviewers is that this version contains some, what the owner/creators of this upstream zip package call "false positives". Which in turn that I was looking into the contents of the package myself I could only find one potential (only 1 not 10) "APM_check/bwchart.exe" which from multiple engines (10) is reported as unsafe, but local antivirus does not report anything. Also, I removed the potential unsafe "APM_check/*" folder completely from the install of this chocolatey package myself in the install file (could be reviewed of course).
The owners of the upstream package said to me by email that they will look into the issue but they still believe its just false positives and I dont see much reaction after that.
Now this bring back the question, is it enough to mitigate the issues by removing the "potential" harmful executables from the upstream package in chocolatey package? IMO the removal of those files from install should be enough. Otherwise I need to reconsider this package for the official one which has the stated problems on its own.
Maybe we could think of some agreement after all?
mkevenaar (reviewer) on 17 Jun 2019 18:35:05 +00:00:
Hi,
could I ask you to reach out on gitter (via the "open chat" on the right bottom) and reach out to me so we can discuss this? My username is mkevenaar.
Thanks
Maurice
mkevenaar (reviewer) on 17 Jun 2019 18:38:17 +00:00:
I have send you a message.
n3rd4i (maintainer) on 25 Jun 2019 21:10:59 +00:00:
The original SC1 installer keeps changing the hash every time I download it, can such issue be resolved somehow or skipped the hash check? (probably that does not stand from a security perspective)
Link:
https://battle.net/download/getInstallerForGame?version=LIVE&gameProgram=STARCRAFT
Pauby (reviewer) on 27 Jun 2019 15:15:54 +00:00:
The checksums are mandatory I'm afraid.
Does the checksum change EVERY time you download it. Or does it change daily / hourly?
n3rd4i (maintainer) on 27 Jun 2019 16:19:01 +00:00:
> Does the checksum change EVERY time you download it. [...] ?
Yes.
Pauby (reviewer) on 28 Jun 2019 10:19:31 +00:00:
That is very strange. But perhaps they embed some sort of tracking ID in the package?
But I'm not sure how you would get around that.
My suggestion is sto aks in the Gitter channel (https://gitter.im/chocolatey/choco) as another maintainer may have come across this issue?
chocolatey-ops (reviewer) on 18 Jul 2019 10:21:44 +00:00:
We've found starcraft v1.16.1 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
n3rd4i (maintainer) on 23 Jul 2019 17:26:39 +00:00:
I have the same issue as this package:
https://chocolatey.org/packages/battle.net/1.16.3.2988
Pauby (reviewer) on 24 Jul 2019 08:49:34 +00:00:
I've updated the battle.net packge with a comment. I'm not really sure how we can move forward though?
chocolatey-ops (reviewer) on 02 Aug 2019 10:23:25 +00:00:
Unfortunately there has not been progress to move starcraft v1.16.1 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.