bcurran3 / chocolateypackages Goto Github PK

please add any extra arguments (https://github.com/chocolatey/choco/wiki/CommandsInstall#packagesconfig) used during package installation when exporting

example:

choco feature enable -n=useRememberedArgumentsForUpgrades
choco install git --packageparameters "/GitOnlyOnPath /NoAutoCrLf /NoShellIntegration /NoGitLfs"
choco install tortoisegit --installarguments "ADDLOCAL=ALL REMOVE=MoreIcons,CrashReporter"

expected packages.config:

<?xml version="1.0" encoding="utf-8"?>
<packages>
   <package id="git" packageParameters="/GitOnlyOnPath /NoAutoCrLf /NoShellIntegration /NoGitLfs" />
   <package id="tortoisegit" installArguments="ADDLOCAL=ALL REMOVE=MoreIcons,CrashReporter" />
</packages>

actual packages.config:

<?xml version="1.0" encoding="utf-8"?>
<packages>
   <package id="git" />
   <package id="tortoisegit" />
</packages>

(Self inflicted feature request.)

Add argument to designate a website to download a packages.config file from and then install the packages from that file (only?).

Should be fairly simple to add, just need to figure out best way to parse the arguments.

I think uTorrent just updated, could you update your checksum?
Thanx

Hash value check fails when installing google-backup-and-sync:

Error - hashes do not match. Actual value was 'F289DDCCAFB7B0EAB59255C620D280E3B99EEB2B9114C51848B6B5A6D9923FB4'.
ERROR: Checksum for 'C:\Users\Foo\AppData\Local\Temp\chocolatey\google-backup-and-sync\3.36.6884.5911\installbackupandsync.exe' did not meet '2C2EA0D23D37AB0A5511D4F926EF961493CB55210FBDDC5899607FD9788B7854' for checksum type 'sha256'.

Thanks for maintaining this package!

The updated package for version 7.07 has just been approved, but currently version 7.08 is already out and downloaded. Upgrading / installing with --ignore-checksums works.

Hi @bcurran3,
The use of aliases for extensions is not allowed if they are replacing original methods. Please find a different method for handling this. We want to ensure you don't break licensed editions and adding overriding aliases does this.

https://www.telerik.com/download/fiddler

@bcurran3
You choco-cleaner is really nice and does a great job.

Although, have you considered creating a CCleaner entry alongside choco-cleaner for users who want to clean Chocolatey through CCleaner instead.

Thanks

https://github.com/MoscaDotTo/Winapp2

https://forum.piriform.com/topic/32310-winapp2ini-additions/?page=1

Checksum fails.
Chekcing the downloaded zip it has 0.10.2.0 .EXE inside instead of the 0.10.0.0

Her is the log with --ignore-checksums active.

install winaero-tweaker -y --ignore-checksums
Chocolatey v0.10.11
Installing the following packages:
winaero-tweaker
By installing you accept licenses for the packages.
Progress: Downloading winaero-tweaker 0.10.1.0... 100%

winaero-tweaker v0.10.1.0 [Approved]
winaero-tweaker package files install completed. Performing other installation steps.
Attempt to get headers for https://winaero.com/e107_files/downloads/winaerotweaker.zip failed.
  The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://winaero.com/e107_files/downloads/winaerotweaker.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden."
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
WARNING: Ignoring checksums due to feature checksumFiles turned off or option --ignore-checksums set.
WARNING: Ignoring checksums due to feature checksumFiles turned off or option --ignore-checksums set.
Extracting C:\Users\username\AppData\Local\Temp\chocolatey\winaero-tweaker\0.10.1.0\winaero-tweakerInstall.zip to C:\ProgramData\chocolatey\lib\winaero-tweaker\tools...
C:\ProgramData\chocolatey\lib\winaero-tweaker\tools
Installing winaero-tweaker...
WARNING: May not be able to find 'C:\ProgramData\chocolatey\lib\winaero-tweaker\tools\WinaeroTweaker-0.10.1.0-setup.exe'. Please use full path for executables.
ERROR: Exception calling "Start" with "0" argument(s): "The system cannot find the file specified"
The install of winaero-tweaker was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\winaero-tweaker\tools\chocolateyinstall.ps1'.
 See log for details.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - winaero-tweaker (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\winaero-tweaker\tools\chocolateyinstall.ps1'.
 See log for details.

It would be great if I could insert package parameters manually into the packages.config. When updating the packages.config file the backup script should retain the parameters as long as the package is still installed. The script could inform me about those parameters during the backup so I can verify their relevance.

This issue is similar to issue #7.

First of all, great idea to have that as a chocolatey package.
Friendly issue to let you know v 1.0.2 is out

Irfanview can be uninstalled silently without the ahk script, if $silentArgs is changed to just '/silent'

See the last part of http://www.irfanview.com/faq.htm#Q69

Thanks for hosting all these packages!

I'm referring to the Choco Package List Backup chocolatey package.

choco-package-list-backup.ps1 contains backup logic and configuration. What happens when I update the package? Does this file get overridden? Do I lose what customization I have made?

Putting tags in for competing products is very bad form for Chocolatey packages - we want relevant results when we are searching for dropbox, not something that is competing and not actually filling that need.

This is useful for packages like dropbox, that already implement automatic upgrades.

Running choco upgrade for these packages is useless. So they should be pinned.

Hi! Installation of resilio-sync-home package is throwing a checksum error. Please update the package per https://github.com/bcurran3/ChocolateyPackages/blob/master/resilio-sync-home/readme.md :)

Currently the newest version is 4.5.2 while the choco package is 4.5.1, so the checksums don't match. Thanks in advance :).

Hi,

Please update the Chocolatey package to include a new version for openHAB 2.4.0 Stable (without addons :))

The issue with the addons has been fixed, so it's also ok to include them back into the package if you want but they have 174MB size and they are not really needed.

Thanx and Happy Holidays!

Please remove from tools\ChocolateyInstall.ps1 the steps to download and deploy the addons file (openhab-addons-2.3.0.kar) since there are issues with the Karaf FeatureInstaller (it installs ALL addons auto-magically) causing massive errors.

Ref: openhab/openhab-distro#729

Thanx!
Angelos

Currently the newest version is 4.5.1 while the choco package is 4.1.0, so the checksums don't match.

Discussion started at chocolatey/choco#544 (comment)

Intent:
Create a helper that, when used, would check a program's exit code and in the case of common MSI abortions; i.e. 1603, would create a scheduled task to further attempt (once) an installation of that package upon reboot.

Method - needs to be tested, but most likely would work.
schtasks.exe /create /f /tn Retry%ChocolateyPackageName% /ru SYSTEM /sc ONSTART /tr "choco install %ChocolateyPackageName% && schtasks.exe /delete /f /tn Retry%ChocolateyPackageName%"

Thoughts:
Would need some sort of flag so that subsequent failures don't enter an infinite loop attempting reinstallation at reboot forever. Could be implemented by dumping a simple RETRY.YES in the package's lib folder (Rob will hate that idea.) or possibly create a chocolatey-fastanswers.extension registry key somewhere to be checked, i.e. packagename could be set as a subkey with a packagename=1 to attempt reinstallation and Set-RetryAfterReboot would delete it and NOT configure the scheduled task to try again under that condition that it's already been retried.

Usage:
Get-PendingReboot
Install-ChocolateyPackage @packageArgs
Set-RetryAfterReboot

Note:
This would be a package for the community repository and "normal" users, and would be noted that it may not be compatible with some business environments using other management programs.

Appears the 'pre-release' versions of YakYak can change without the revision numbers changing.
Latest version (1.4.4) now currently has a sha256 checksum of: 050692e070912ce1c86a54cf717118f5d4f37d5dcac4d11d90b148bef379cd67

This is causing choco to fail.

would be nice :-)

ran on powershell core 6.1

>C:\ProgramData\chocolatey\bin\choco-cleaner.ps1
Choco-Cleaner.ps1 v0.0.5 (08/22/2018) - deletes unnecessary residual Chocolatey files to free up disk space
Copyleft 2017-2018 Bill Curran (bcurran3@yahoo.com) - free for personal and commercial use
Get-WmiObject : The term 'Get-WmiObject' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\ProgramData\chocolatey\bin\choco-cleaner.ps1:33 char:20
+      $FreeBefore = Get-WmiObject Win32_LogicalDisk -Filter "DeviceID= ...
+                    ~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (Get-WmiObject:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Choco-Cleaner Summary:
 * Deleting unnecessary Chocolatey _processed.txt (WTF?) file...
 * Deleting unnecessary Chocolatey .ignore files...
 * Deleting unnecessary Chocolatey .old files...
 * Deleting unnecessary Chocolatey cache files...
 * Deleting unnecessary Chocolatey config backup files...
 * Deleting unnecessary Chocolatey lib-bad package files...
 * Deleting unnecessary Chocolatey lib-bkp package files...
 * Deleting unnecessary Chocolatey extracted file logs...
 * Deleting unnecessary Chocolatey log files...
 * Deleting unnecessary Chocolatey package embedded archive files in toolsDir...
 * Deleting unnecessary Chocolatey package embedded archives and executables in .nupkg files...
 * Deleting unnecessary Chocolatey package embedded license files...
 * Deleting unnecessary Chocolatey package embedded Microsoft installers...
 * Deleting unnecessary Chocolatey package embedded various read me files...
 * Deleting unnecessary Nuget cache files...
Get-WmiObject : The term 'Get-WmiObject' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\ProgramData\chocolatey\bin\choco-cleaner.ps1:129 char:19
+      $FreeAfter = Get-WmiObject Win32_LogicalDisk -Filter "DeviceID=' ...
+                   ~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (Get-WmiObject:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Choco-Cleaner finished deleting unnecessary Chocolatey files and saved you 0 KB!
Found Choco-Cleaner.ps1 useful?
Buy me a beer at https://www.paypal.me/bcurran3donations
Become a patron at https://www.patreon.com/bcurran3

I think you might owe me a jammy?

Following on from #59 - after some messing around, I found everything works fine as long as I'm under an Adminstrator Command Prompt. If I use any wsl-related command (e.g. wsl, bash, ubuntu1804) from my normal user account, I still get:

Error: 0x80040305 Press any key to continue...

I've tried using the Admin prompt to create a new wsl account and setting it as default (i.e. ubuntu1804 config --default-user <new_user>) - thinking the non-Admin account couldn't log in as wsl root. But it doesn't help.

Note: I was confused about wslpath.exe. Turns out it's wsl-side in /bin/wslpath.

I've just discovered these packages, and this is an awesome idea.

It would be great to have some logs to check what packages have been upgraded recently (or to know if a package have problems to upgrade). Just the choco upgrade all output should be enough.

Requesting, per the readme, for the Q-Dir package to be updated.

The latest XTUSetup.exe from https://downloadmirror.intel.com/24075/eng/ is failing sha256 checksum when installing via Chocolately.

"Error - hashes do not match."

First, thanks for the great tool. I used your backup tool to create a packages.config file which came in very handy when I set up my new PC. However, I have a couple packages installed that I couldn't tell/remember what they were by looking at the ID. So I looked them up in Chocolatey-gui, and in addition to the package ID, I could also see that Title, Summary, and other package details were displayed. This got me poking around, and I found the other info in the .nuspec files for each package. I decided it would be nice to have some of this extra info in the packages.config.

I started by trying to load the packages.config file created by your tool as XML, thinking I would just append the extra attributes, but it seems that there must be some bad XML in your output (I got an "invalid character" error). So I decided to create my own using the .Net XmlWriter class and looping through the choco list -lo output and adding the desired info from each .nuspec to the file. Then I decided it would be nice to have this in a more readable format, so I used the .Net XslCompiledTransform class to generate the HTML for a "pretty" doc of installed packages.

My script and .xslt file are here:

https://github.com/JohnStefanko/chocolatey

If you like my ideas, feel free to use anything from my Chocolatey repository in your backup tool.

The newest version is 1.13.3

Hello!

Visual BCD developer changed download URL for MSI package or maybe there is a typo. Please update chocolateyinstall.ps1:

- $url = 'https://www.boyans.net/VisualBcd5/VisualBcd_0.9.3.1.msi'
+ $url = 'https://www.boyans.net/VisualBcd4/VisualBcd_0.9.3.1.msi'

Love your script -- was a much more robust version of one I'd written some time ago. Thanks for putting it on Nuget.

I'd love to be able to prepend the date or possibly the date/time to the $ConfigFile.

I updated the script to do this for myself. If you're open to the change, let me know here and I'll do a PR to implement and set behind an option that defaults to false so that existing users don't have something change on them.

The idea is that with $PrependDate set to true, the output would be 2018-02-07_packages.config.

it would be a nice feature to set the execution time also for choco-cleaner and choco-package-list-backup like you can for choco-upgrade-all-at via packageParameters= resp. --params=.

so you can create a packages.config-file once with all the times in it and don't have to rework the tasks every time after installing.

I'd like to request that after modules are installed, and additional command be executed to create a shortcut on the public profile's desktop which, when double-clicked, launches a PowerShell session and imports the module so that it behaves the same way the legacy ".exe" installer did. I've done some testing and got this to work in my test environment.

Additionally, the dependency for PowerShell ≥ 5.0 fails as no PowerShell "5.0" version is listed in the chocolatey package repo. This would need to be changed to "5.0.10586.20161201" to work correctly.

Latest package version is still 0.199 from Summer 2018. 0.205 was released December 26, 2018.

Just what it says in the title, really. The actual checksum of the downloaded file (as of 9/5/2017) was 6FC3C5ACD8E002485619C29B3E160AE7E8AAD298E7142BC3E16550F7EE4BD299.

Would be open to Netgear ProSAFE Plus Utility (prosafe-plus-utility)?

I have made the following updated versions of how copying to Dropbox and Google FS is handled. The reasons for this is that:

• On one of my PCs the dropbox folder is located in a non-default position which choco-package-list-backup did not find. While I was at it I added support for both personal and business Dropbox accounts.
• Google Drive has been deprecated so I have replaced it with support for Google Drive File Stream.

Dropbox

The current Dropbox handling is replaced with the following:

# Check for Dropbox paths
if (Test-Path $Env:AppData\Dropbox\info.json)
{
    $DropboxPersonal = ((get-content $Env:AppData\Dropbox\info.json) -join '`n' | ConvertFrom-json).personal.path
    $DropboxBusiness = ((get-content $Env:AppData\Dropbox\info.json) -join '`n' | ConvertFrom-json).business.path
}
elseif (Test-Path $Env:LocalAppData\Dropbox\info.json)
{
    $DropboxPersonal = ((get-content $Env:LocalAppData\Dropbox\info.json) -join '`n' | ConvertFrom-json).personal.path
    $DropboxBusiness = ((get-content $Env:LocalAppData\Dropbox\info.json) -join '`n' | ConvertFrom-json).business.path
}

# Backup Chocolatey package names on local computer to packages.config file in Personal Dropbox directory if it exists
if ($UseDropbox -match "True" -and ($DropboxPersonal) -and (Test-Path $DropboxPersonal))
   {
    $SavePath = "$DropboxPersonal\$SaveFolderName\$Env:ComputerName"
    Write-PackageConfig
   }
   
# Backup Chocolatey package names on local computer to packages.config file in Business Dropbox directory if it exists
if ($UseDropbox -match "True" -and ($DropboxBusiness) -and (Test-Path $DropboxBusiness))
   {
    $SavePath = "$DropboxBusiness\$SaveFolderName\$Env:ComputerName"
    Write-PackageConfig
   }

I have based the code on the information found here:
https://www.dropbox.com/help/desktop-web/locate-dropbox-folder#programmatically

Google Drive File Stream

The current Google Drive handling is replaced with the following:

# Backup Chocolatey package names on local computer to packages.config file in Google Drive FS "My Drive" directory if it exists
$GoogleFSmountpoint = (Get-ItemProperty -path Registry::HKEY_CURRENT_USER\Software\Google\DriveFS\Share).MountPoint
if ($UseGoogleDrive -match "True" -and ($GoogleFSmountpoint) -and (Test-Path "${GoogleFSmountpoint}:\My Drive"))
{
    $SavePath = "${GoogleFSmountpoint}:\My Drive\$SaveFolderName\$Env:ComputerName"
    Write-PackageConfig
   }

I have based the code on the information found here:
https://support.google.com/a/answer/7644837?hl=en

You are free to use/change/discard this code as you please. As for tests, well, "It works on my machine..."

Newer versions of Firefox have changed how local extensions get installed and rendered all of my "-firefox" extensions obsolete.

I spent some time trying to figure out a new way via some info I found on the web, but I wasn't successful.

Any links on how to do it would be appreciated.

i totally got the idea behind the pseudo-supersession of choco-upgrade-all-at-startup by choco-upgrade-all-at (because of a possible slowdown of the boot/reboot), but wouldn't it make sense to activate the setting "execute task as soon as possible after a missed appointment" at least in tasks with relatively short execution-time like choco-cleaner and choco-package-list-backup?

Hi,

We are using your chocolatey package to keep our windows servers vmware-tools up to date. Thank you for the package by the way 😃

We have a Jenkins job that runs every month and updates the vmware-tools package on all servers in case there is an update.

Jenkins uses an Ansible Playbook that looks like this:

tasks:
  - name: updating vmware-tools via chocolatey
    win_chocolatey:
      name: vmware-tools
      state: latest

With the newest vmware-tools package you uploaded to chocolatey I'm getting the following error when installing the package via ansible.

2018-08-16 11:59:52,836 1784 [DEBUG] - Finishing 'Start-ChocolateyProcessAsAdmin'
2018-08-16 11:59:52,977 1784 [INFO ] - vmware-tools has been installed.
2018-08-16 11:59:53,211 1784 [ERROR] - ERROR: Exception calling "CreateToastNotifier" with "1" argument(s): "Die Benachrichtigungsplattform ist nicht verfügbar.

Die Benachrichtigungsplattform ist nicht verfügbar. => The notification platform is not available

This seems to come from the following line that has been added with commit 15dce7b

Show-ToastMessage "$packageName installed." "Version $env:packageVersion."

Is there another way you can output the message ? Show-ToastMessage does not seem to work via the winrm connection ansible uses propably because it is not a graphical environment. Maybe something simple like Write-Host ?

(Self inflicted feature request.)

Add ability to run choco-package-list-backup as a scheduled task (most likely just weekly) similar to choco-upgrade-all-at, choco-persistent-packages, and choco-optimize-at.

Hi. The install works for me but the associated tools (e.g. wslpath.exe, ubuntu.exe) are missing.

The following error is thrown when upgrading the vnc-viewer package to 6.19.107 using Chocolatey:

ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot create a file when that file already exists.

Log file available at: https://gist.github.com/lefte/3628702a97aaf63c06150755da9138b0

Please update with current/correct checksum. Thank you!

Giving how you made a commit 10 minutes ago, I think you're already on this, but just in case you don't see it.

I've got this line in my choco-package-list-backup.ps1 script at line 84 (I just installed choco-package-list-backup 2018.04.24):

Write-Host "choco-package-list-backup.ps1 v$CPLBver" - backup Chocolatey package list(s) locally and to the cloud -ForegroundColor white

This produces a powershell syntax error because of the lack of quotes.

s : The term 's' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\ProgramData\chocolatey\bin\choco-package-list-backup.ps1:84 char:87
+ ... list-backup.ps1 v$CPLBver" - backup Chocolatey package list(s) locall ...
+                                                                 ~
    + CategoryInfo          : ObjectNotFound: (s:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

This might still be an issue with a very recent commit.

choco-package-list-backup determines the location of the users Documents folder using the $env:UserProfile variable. If the user has moved his Documents folder to another location, like I have, then the backup files are written to the wrong location. Using [Environment]::GetFolderPath("MyDocuments") resolves the actual location of the folder.

I pinged you on chocolatey.org about releasing version R545 of snappy-driver-installer but between then and you pushing a new version they released versions R1741 and 1.17.4.2 . Other users are now saying that these new versions includes adware though.

So digging into this, I found out that at some point in the last 6 months the original lead developer handed the site/software off to some unknown company and that company has decided to monetize this software while still advertising it as free and open source software. What worse is they have turned off access to the original SVN repo so you can't even see or verify what kind of adware they are putting in these new versions and they are still saying it's GPL-v3 while having no actual source code available. The automated chocolatey virus scanner also changed for the new version, it went from 0/58 to 12/59.

Luckily I also found one of the developer helping during the transition did not like what the new company was doing and decided to maintain his own free and open source fork. Which he just called "snappy driver installer origin", he also explained more about the situation on this about page.

So the old and potentially malicious snappy driver installer is from this site:

http://www.sdi-tool.org/

While the new snappy driver installer origin can be found on this site:

http://snappy-driver-installer.org/

I'm not really sure what would be the best way to handle this on chocolatey. Should we just made a new chocolatey pkg called snappy-driver-install-origin and then unpublish just the new 1.17.4.2 version or maybe just deprecate the entire snappy-driver-installer? Or would you want to keep publishing the new forked versions under snappy-driver-installer since there is no version overlap?

why is for all tasks created by your scripts the setting activated to "end the task, if its execution takes longer than 3 days"?
wouldn't it make more sense to set it to something like 2 hours?