Ansible
PS DSC
Downloads:
52
Downloads of v 0.3.0:
31
Last Update:
30 Apr 2022
Package Maintainer(s):
Software Author(s):
- Aarush Goyal
- Ishan Bhardwaj
Tags:
borzoi git github multirepo- Software Specific:
- Software Site
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
borzoi (Install)
- Software Specific:
- Software Site
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
52
Downloads of v 0.3.0:
31
Maintainer(s):
Software Author(s):
- Aarush Goyal
- Ishan Bhardwaj
borzoi (Install)
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Aarush Goyal, Ishan Bhardwaj. The inclusion of Aarush Goyal, Ishan Bhardwaj trademark(s), if any, upon this webpage is solely to identify Aarush Goyal, Ishan Bhardwaj goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
WARNING
This package was rejected on 25 May 2022. The reviewer mkevenaar has listed the following reason(s):
Description
Borzoi helps you to easily replicate and share file structure.
Files
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>
tools\LICENSE.txt
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>
LICENSE
<Insert License Here>
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://docs.chocolatey.org/en-us/choco/commands/uninstall
## and https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateypackage
## 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 = 'borzoi*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
fileType = 'EXE_MSI_OR_MSU' #only one of these: MSI or EXE (ignore MSU for now)
# MSI
silentArgs = "/qn /norestart"
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://community.chocolatey.org/packages/autohotkey.portable
#validExitCodes= @(0) #please insert other valid exit codes here
}
# 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."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
## OTHER POWERSHELL FUNCTIONS
## https://docs.chocolatey.org/en-us/create/functions
#Uninstall-ChocolateyZipPackage $packageName # Only necessary if you did not unpack to package directory - see https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyzippackage
#Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyenvironmentvariable
#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://docs.chocolatey.org/en-us/create/functions/uninstall-binfile
## Remove any shortcuts you added in the install script.
tools\chocolateyinstall.ps1
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\borzoi.exe
md5: 669BFF06B2F462B1D0735714E1AFAFA3 | sha1: 14CD5F7099F404FB161CE4A4D40C022B6119B261 | sha256: 17A975B8A22F9DCA33518929A92E818BCF1F998911FD2294FF3EF3054BBE104D | sha512: D54A1A51BA37F914FA957E036BA8F381438DECDBDE8BE0B968089A419942CD71530D94D06D26C78C4E23B2E6F13F40112F5E2BE3EC32A07211D4F5657EABC229
Virus Scan Results
Log in or click on link to see number of positives.
- borzoi.0.3.0.nupkg (52770767a70e) - ## / 64
- borzoiInstall.EXE (17a975b8a22f) - ## / 67
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.
Dependencies
This package has no dependencies.
Discussion for the borzoi (Install) Package
Ground Rules:
- This discussion is only about borzoi (Install) and the borzoi (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 borzoi (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.
theishanbh (maintainer) on 30 Apr 2022 09:08:24 +00:00:
User 'theishanbh' (maintainer) submitted package.
chocolatey-ops (reviewer) on 30 Apr 2022 09:43:49 +00:00:
borzoi 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.
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 30 Apr 2022 09:52:19 +00:00:
borzoi has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/4786b8574274e062a8b9d00568afe9f9 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 30 Apr 2022 10:05:45 +00:00:
borzoi has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it
This is not enough detections to prevent the approval of this package version.
TheCakeIsNaOH (reviewer) on 17 May 2022 14:00:46 +00:00:
Hi, there are some items that should be addressed:
chocolateybeforemodify.ps1is unused in this package, it should be removed.packageSourceUrlis for the source for the Chocolatey package (e.g. the.nuspec,chocolateyinstall.ps1, etc), not for where the source for the software that the package installs is.LICENSE.txtVERIFICATION.txtwith explicit steps on how to verify the included.exeis the same as the.exepublished by the project. Example: https://github.com/chocolatey-community/chocolatey-coreteampackages/blob/master/automatic/7zip.install/legal/VERIFICATION.txtThanks, TheCakeIsNaOH
theishanbh (maintainer) on 24 May 2022 21:04:42 +00:00:
Hey, so I have addressed all the issues that you have mentioned. But the problem is that, we were not publishing the .exes before. We are now at version 0.7.0. And I dont have the .exe published for 0.3.0. So you will be unable to verify the package using steps mentioned in VERIFICATION.txt. And when I tried pushing the 0.7.0 version, I was unable to.
Scanner Status Change - Virus Scanner has been set to rerun
chocolatey-ops (reviewer) on 25 May 2022 03:07:00 +00:00:
borzoi has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it
This is not enough detections to prevent the approval of this package version.
theishanbh (maintainer) on 25 May 2022 05:56:30 +00:00:
I request you to reject the package. At the time of pushing version=0.3.0, we did not publish .exe so that the package can be verified. But the reviewer asked me to provide a way of verification. We started publishing .exe, since version=0.7.0. So we are stuck, as we are unable to push version 0.7.0 without either getting 0.3.0 approved (which is not possible because it cant be verified) or getting it rejected. So I request you to reject it.
mkevenaar (reviewer) on 25 May 2022 05:57:49 +00:00:
Rejected on users request
Status Change - Changed status of package from 'submitted' to 'rejected'.