Ansible
PS DSC
Downloads:
228
Downloads of v 0.0.1:
228
Last Update:
04 May 2017
Package Maintainer(s):
Software Author(s):
- Slack Technologies
- Inc.
Tags:
slack admin- Software Specific:
- Software Site
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Slack Machine-Wide Installer
- Software Specific:
- Software Site
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
228
Downloads of v 0.0.1:
228
Maintainer(s):
Software Author(s):
- Slack Technologies
- Inc.
Slack Machine-Wide Installer
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.
- Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
- Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
- Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.
Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.
This package was rejected on 23 Jul 2017. The reviewer chocolatey-ops has listed the following reason(s):
Slack provides an alternate installer based on Microsoft Installer packages (MSI) for you to silently deploy the Slack Windows application to your organization via Group Policy / Microsoft System Center or Chocolatey in this case.
$packageName = 'Slack Machine-Wide Installer'
$fileType = 'msi'
$silentArgs = '/qn'
$validExitCodes = @(0)
try {
$packageUninstall = Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*$packageName*"} | Select-Object DisplayName, UninstallString
if($packageUninstall -and ![String]::IsNullOrEmpty($packageUninstall.UninstallString)){
[string]$uninstallString = $packageUninstall.UninstallString
$uninstallString = $uninstallString.ToLower()
if($uninstallString -like 'msiexec*'){
$uninstallString = $uninstallString.Replace('msiexec.exe', '').Replace('msiexec', '')
}
if($uninstallString -like '*/i*'){
$uninstallString = $uninstallString.Replace('/i', '')
}
# Use this instead
$msiArgs = "$uninstallString $silentArgs";
#Start-ChocolateyProcessAsAdmin "$msiArgs" 'msiexec' -validExitCodes $validExitCodes
Uninstall-ChocolateyPackage -packageName $packageName -fileType 'msi' -silentArgs $msiArgs -validExitCodes $validExitCodes
}
else{
throw "Unable to locate uninstallation information in registry"
}
}
catch {
throw $_.Exception
}Log in or click on link to see number of positives.
- SlackSetup.msi (729e066a580b) - ## / 57
- SlackSetup.msi (e86da6afa59b) - ## / 57
- slack.install.0.0.1.nupkg (c3a0d5a7cd86) - ## / 59
- SlackSetup.msi (efcfe295aa4b) - ## / 58
- SlackSetup.msi (6e88ba595565) - ## / 56
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.
Slack Technologies, Inc.
Slack is an app that is installed on each user’s local profile. While there are many benefits, one disadvantage to this approach is that the installer has to run in the context of that user (i.e., running the installer under your account or a service account has no effect on the intended user's account on the same machine).
To help make installing Slack on multiple machines easier, we provide an MSI that:
Places the standard installer under Program Files\Slack Machine Installer.
Creates a registry key that will run the installer with a --checkInstall flag when a user logs in.
Installs Slack silently if the app isn't installed when a user logs in. If it is installed or the user has chosen to uninstall it, we will exit.
The MSI installer runs on user login because the intended user account may not exist during imaging. Keep in mind, if you choose to uninstall the MSI, Slack will not be automatically removed from user accounts.
This package has no dependencies.
Ground Rules:
- This discussion is only about Slack Machine-Wide Installer and the Slack Machine-Wide Installer 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 Slack Machine-Wide Installer, 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.
LazarusRS (maintainer) on 23 Mar 2017 09:42:05 +00:00:
User 'LazarusRS' (maintainer) submitted package.
chocolatey-ops (reviewer) on 23 Mar 2017 10:15:45 +00:00:
slack.install 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.
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 23 Mar 2017 10:37:26 +00:00:
slack.install 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/12857fb1194697e7e5041836bee18e92 for details.
This is an FYI only. There is no action you need to take.
AdmiringWorm (reviewer) on 04 Apr 2017 22:39:17 +00:00:
if not, please update the owners field with your name/username.
Thanks,
Kim
chocolatey-ops (reviewer) on 24 Apr 2017 22:39:21 +00:00:
We've found slack.install v0.0.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.
LazarusRS (maintainer) on 04 May 2017 07:37:32 +00:00:
User 'LazarusRS' (maintainer) submitted package.
chocolatey-ops (reviewer) on 04 May 2017 08:10:03 +00:00:
slack.install 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.
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 04 May 2017 08:34:36 +00:00:
slack.install 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/bd2702ab3d6a6cc421d9b14e9a69bc99 for details.
This is an FYI only. There is no action you need to take.
flcdrg (reviewer) on 06 May 2017 05:18:41 +00:00:
Can you confirm whether you've contacted the maintainer of https://chocolatey.org/packages/slack? Potentially they might want to convert their package to a slack.portable down the track, but having this package would be a breaking change for existing users.
David
LazarusRS (maintainer) on 09 May 2017 07:53:41 +00:00:
I haven't contacted the maintainer of https://chocolatey.org/packages/slack. I am just trying to deploy the Slack provided tools for machine based installation of their software (as the release notes state), this deployment method is not mutually exclusive with the other Slack package. My assumption is that if Slack were to provide a portable version of their installer then this machine wide installer would also be updated to support that?
AdmiringWorm (reviewer) on 18 Jun 2017 19:24:55 +00:00:
Sorry about the delay for this package.
But honestly, because this is a
.installpackage this would require the other package to be made a meta package, otherwise this package would just be viewed as a duplicate of the other one.So please contact the maintainer of the other package, and try to work with him to make an updated package (or follow the triage process to take over maintaining the other slack package).
Thanks,
Kim.
chocolatey-ops (reviewer) on 08 Jul 2017 19:29:37 +00:00:
We've found slack.install v0.0.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.
chocolatey-ops (reviewer) on 23 Jul 2017 19:32:56 +00:00:
Unfortunately there has not been progress to move slack.install v0.0.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'.