#### Strawberry Music Player

13

13

Maintainer(s):

Software Author(s):

• Jonas Kvinge
• 1
• 2
• 3

### Some Checks Are Exempted or Have Failed

Not All Tests Have Passed

Validation Testing Failed

Verification Testing Exemption:

Details

Scan Testing Successful:

No detections found in any package files

Details

This package was rejected on 07 May 2021. The reviewer chocolatey-ops has listed the following reason(s):

#### samon53 (maintainer) on 13 Oct 2020 03:23:22 +00:00:

User 'samon53' (maintainer) submitted package.

#### samon53 (maintainer) on 13 Oct 2020 03:49:35 +00:00:

User 'samon53' (maintainer) submitted package.

#### chocolatey-ops (reviewer) on 13 Oct 2020 04:21:45 +00:00:

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

• If you are going to use copyright in the nuspec, please use more than 4 characters. More...
##### 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.

• The nuspec has been enhanced to allow 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...
• Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. 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.

• The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
• docsUrl - points to the location of the wiki or docs of the software
• mailingListUrl - points to the forum or email list group for the software
• bugTrackerUrl - points to the location where issues and tickets can be accessed
• projectSourceUrl - points to the location of the underlying software source
##### 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.

• If this is a brand new package that has never went through approval before, the reviewer will suggest a change to the package id. More...

#### samon53 (maintainer) on 16 Oct 2020 01:59:01 +00:00:

User 'samon53' (maintainer) submitted package.

#### chocolatey-ops (reviewer) on 16 Oct 2020 02:33:03 +00:00:

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

• If you are going to use copyright in the nuspec, please use more than 4 characters. More...
##### 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.

• The nuspec has been enhanced to allow 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...
• Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. 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.

• The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
• docsUrl - points to the location of the wiki or docs of the software
• mailingListUrl - points to the forum or email list group for the software
• bugTrackerUrl - points to the location where issues and tickets can be accessed
• projectSourceUrl - points to the location of the underlying software source
##### 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.

• If this is a brand new package that has never went through approval before, the reviewer will suggest a change to the package id. More...

#### chocolatey-ops (reviewer) on 22 Apr 2021 09:39:30 +00:00:

We've found strawberrymusicplayer v0.8.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:

• Resubmit fixes for this version.
• If the package version is failing automated checks, you can self-reject the package.

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 07 May 2021 09:41:15 +00:00:

Unfortunately there has not been progress to move strawberrymusicplayer v0.8.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'.

Description

Strawberry is a music player and music collection organizer. It is a fork of Clementine released in 2018 aimed at music collectors and audiophiles. It's written in C++ using the Qt toolkit.

tools\chocolateybeforemodify.ps1
# This runs in 0.9.10+ before upgrade and uninstall.
# Use this file to do things like stop services prior to upgrade or uninstall.
# NOTE: It is an anti-pattern to call chocolateyUninstall.ps1 from here. If you
#  need to uninstall an MSI prior to upgrade, put the functionality in this
#  file without calling the uninstall script. Make it idempotent in the
#  uninstall script so that it doesn't fail when it is already uninstalled.
# NOTE: For upgrades - like the uninstall script, this script always runs from
#  the currently installed version, not from the new upgraded package version.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';$packageName  = 'StrawberryMusicPlayer'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"$packageArgs = @{

packageName   = $packageName softwareName = 'StrawberryMusicPlayer*' unzipLocation =$toolsDir
fileType      = 'exe'
silentArgs    = "/S"
validExitCodes= @(0)
url32         = 'https://files.strawberrymusicplayer.org/StrawberrySetup-0.8.1-x86.exe'
checksum32    = 'B6AFDD673B237DF3FB88EE8268E00546D4F5DC6EE03DAFE673F700B4B6E013B6'
checksumType  = 'sha256'
url64         = 'https://files.strawberrymusicplayer.org/StrawberrySetup-0.8.1-x64.exe'
checksum64    = 'A6036B4736ED787F688FC1AEB26E908C9DEC3B392737BC3ED177AA365375567D'
checksumType64= 'sha256'
}
Install-ChocolateyPackage @packageArgs
tools\chocolateyuninstall.ps1
# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
#   $f='c:\path\to\thisFile.ps1' # gc$f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^]#.*','$1'} | Out-File$f+".~" -en utf8; mv -fo $f+".~"$f

## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements),
## AutoUninstaller should be able to detect and handle registry uninstalls without a chocolateyUninstall.ps1.
## See https://chocolatey.org/docs/commands-uninstall
## and https://chocolatey.org/docs/helpers-uninstall-chocolatey-package

## If this is an MSI, ensure 'softwareName' is appropriate, then clean up comments and you are done.
## If this is an exe, change fileType, silentArgs, and validExitCodes

$ErrorActionPreference = 'Stop'; # stop on all errors$packageArgs = @{
packageName   = $env:ChocolateyPackageName softwareName = 'StrawberryMusicPlayer*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique fileType = 'EXE' #only one of these: MSI or EXE (ignore MSU for now) # MSI silentArgs = "/S" validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx # OTHERS # Uncomment matching EXE type (sorted by most to least common) #silentArgs = '/S' # NSIS #silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup #silentArgs = '/s' # InstallShield #silentArgs = '/s /v"/qn"' # InstallShield with MSI #silentArgs = '/s' # Wise InstallMaster #silentArgs = '-s' # Squirrel #silentArgs = '-q' # Install4j #silentArgs = '-s -u' # Ghost # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. #silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK) # https://chocolatey.org/packages/autohotkey.portable #validExitCodes= @(0) #please insert other valid exit codes here }$uninstalled = $false # Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below, # take a dependency on "chocolatey-core.extension" in your nuspec file. # This is only a fuzzy search if$softwareName includes '*'. Otherwise it is
# exact. In the case of versions in key names, we recommend removing the version
# and using '*'.
[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') {
# The Product Code GUID is all that should be passed for MSI, and very
# FIRST, because it comes directly after /x, which is already set in the
# Uninstall-ChocolateyPackage msiargs (facepalm).
$packageArgs['silentArgs'] = "$($_.PSChildName)$($packageArgs['silentArgs'])" # Don't pass anything for file, it is ignored for msi (facepalm number 2) # Alternatively if you need to pass a path to an msi, determine that and # use it instead of the above in silentArgs, still very first$packageArgs['file'] = ''
} else {
# NOTES:
# - You probably will need to sanitize $packageArgs['file'] as it comes from the registry and could be in a variety of fun but unusable formats # - Split args from exe in$packageArgs['file'] and pass those args through $packageArgs['silentArgs'] or ignore them # - Ensure you don't pass double quotes in$file (aka $packageArgs['file']) - otherwise you will get "Illegal characters in path when you attempt to run this" # - Review the code for auto-uninstaller for all of the fun things it does in sanitizing - https://github.com/chocolatey/choco/blob/bfe351b7d10c798014efe4bfbb100b171db25099/src/chocolatey/infrastructure.app/services/AutomaticUninstallerService.cs#L142-L192 } 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."
$key | % {Write-Warning "-$($_.DisplayName)"} } ## OTHER POWERSHELL FUNCTIONS ## https://chocolatey.org/docs/helpers-reference #Uninstall-ChocolateyZipPackage$packageName # Only necessary if you did not unpack to package directory - see https://chocolatey.org/docs/helpers-uninstall-chocolatey-zip-package
#Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://chocolatey.org/docs/helpers-uninstall-chocolatey-environment-variable
#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://chocolatey.org/docs/helpers-uninstall-bin-file
## Remove any shortcuts you added in the install script.



Note: Include this file if including binaries you have the right to distribute.
Otherwise delete. this file.

===DELETE ABOVE THIS LINE AND THIS LINE===

From: <insert applicable license url here>


tools\VERIFICATION.txt

Note: Include this file if including binaries you have the right to distribute.
Otherwise delete. this file. If you are the software author, you can change this
mention you are the author of the software.

===DELETE ABOVE THIS LINE AND THIS LINE===

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

<Include details of how to verify checksum contents>
<If software vendor, explain that here - checksum verification instructions are optional>

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.

Discussion for the Strawberry Music Player Package