Opening an issue to discuss what to do next with DraftSight 2019 and beyond.

DraftSight 2019 for Windows® is offered in paid versions only.

Once you download and install DraftSight 2019 (free 30-day trial or purchased version), you will no longer be able to redownload or access any previous free version of DraftSight (2018 or earlier).

All free versions of DraftSight (2018 or earlier) will cease to run after 12/31/2019.

https://www.3ds.com/products-services/draftsight-cad-software/download-draftsight/

Hi. I hope you are well and thanks again for maintaining this package. I wrote this in the Chocolatey comments section but in case you didn't get notified, I figured I'd open an issue here. I just wanted to let you know I keep getting this ("common" Chocolatey) error when attempting to upgrade:

ERROR: Cannot process argument transformation on parameter 'file'. Cannot convert value to type System.String.
The upgrade of barrier was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\barrier\tools\chocolateyinstall.ps1'.
See log for details.

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

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

This is the log error:

2020-07-28 11:43:38,043 160164 [ERROR] - ERROR: Cannot process argument transformation on parameter 'file'. Cannot convert value to type System.String.
2020-07-28 11:43:38,047 160164 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\barrier\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '''] exited with '-1'.

Describe the bug
The Download of the rsat package with internalize runs into an error.
I think the problem comes from https://github.com/teknowledgist/Chocolatey-packages/blob/master/manual/rsat/tools/chocolateyinstall.ps1#L62 and choco try to replace the link and fails.

To Reproduce
Steps to reproduce the behavior:

1. Run choco.exe download rsat -r --no-progress --internalize --force --source=https://chocolatey.org/api/v2/
2. See error

Expected behavior
Download RSAT and run the internalize

Error

RSAT v2.1809.0.20210815 (forced) [Approved]
Found internalizable Chocolatey functions. Inspecting values for remote resources.
Found 'https://www.microsoft.com/download/confirmation.aspx?id=28972' for replacement.
Found 'https://www.microsoft.com/download/confirmation.aspx?id=39296' for replacement.
Found 'https://www.microsoft.com/download/confirmation.aspx?id=45520' for replacement.
Found 'https[^' for replacement.
Encountered error downloading package rsat v:
System.UriFormatException: Ungültiger URI: Das URI-Format konnte nicht bestimmt werden.
   bei System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   bei chocolatey.licensed.infrastructure.app.commandresources.RemoteDownloader.get_remote_file_name(String url, String userAgent, String defaultName, PSHost host)
   bei chocolatey.licensed.infrastructure.app.commands.ProChocolateyDownloadCommand.process_downloaded_package(IPackage package, String downloadLocation, ChocolateyConfiguration configuration)
   bei chocolatey.infrastructure.app.nuget.NugetCommon.<>c__DisplayClass14.<GetPackageManager>b__11(Object s, PackageOperationEventArgs e)
   bei NuGet.PackageManager.OnInstalled(PackageOperationEventArgs e)
   bei NuGet.PackageManager.Execute(IPackage package, IPackageOperationResolver resolver)
   bei NuGet.PackageManager.InstallPackage(IPackage package, Boolean ignoreDependencies, Boolean allowPrereleaseVersions)
   bei chocolatey.licensed.infrastructure.app.commands.ProChocolateyDownloadCommand.download_packages(String packageName, String packageVersion, String downloadLocation, ChocolateyConfiguration configuration)

The package fails to work on systems with Office 365 deployed because the error action is stop and that reg path doesn't exist on click-to-run instead of MSI installs of office.

Last couple of months I've been installing DraftSight 2019 SP0 from Chocolatey and manually entering the license. Been a couple weeks since I had to do an installation but today I did the install and when I run DraftSight I get an error dialog:

So I fired up and Windows 10 Enterprise 90-day eval in vagrant and can duplicate the problem.

I'm not sure what has changed as the digital signatures inside the install script still matches the downloaded installer but I cannot enter my licenses now.

Seen this happen myself today and also by others in comments at https://community.chocolatey.org/packages/FiraCode#discussion

WARNING: An error occured installing 'C:\Users\<username>\AppData\Local\Temp\chocolatey\FiraCode\variable_ttf\FiraCode-VF.ttf'
WARNING: Exception: The requested operation cannot be performed on a file with a user-mapped section open.

WARNING: The requested operation cannot be performed on a file with a user-mapped section open.

6 fonts were installed.
WARNING: 1 submitted font paths failed to install.

Not sure if there's a way to work around it, but mentioning it here.

mcr-r2014b and mcr-r2015a packages do not work if cinst is run with --forcex86 option.
Here is, for example, the error message returned after running cinst -dvy --forcex86 mcr-r2014b:

ERROR: Cannot process argument transformation on parameter 'file'. Cannot convert value to type System.String.
 at <ScriptBlock>, C:\ProgramData\chocolatey\lib\mcr-r2014b\tools\chocolateyinstall.ps1: line 45
at <ScriptBlock>, C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1: line 49
at <ScriptBlock>, <No file>: line 1

Here is the command used to find the setup.exe file among the extracted file of MCR installer:

$Installer = (Get-ChildItem $WorkSpace -Include 'setup.exe' -Recurse).fullname

The 32 bits install fails because the win32 MCR installer contains two setup.exe files instead of a single one in the 64 bits MCR installer.

The installation skips with the following warning

Here is my $osInfo output:

Version            : 10.0.19043
ProductType        : 3
Caption            : Microsoft Windows 10 Enterprise for Virtual Desktops
OperatingSystemSKU : 175
BuildNumber        : 19043

It looks like Artifex dropped gsview from their website. The URL in https://github.com/teknowledgist/Chocolatey-packages/blob/master/manual/gsview/tools/chocolateyInstall.ps1 gives a 404. I found it elsewhere on the internet with a matching SHA2-256 sum. I'm not sure if there are any official hosts, of the exe or the source (or if the source exists, even).

automatic/tableau-public/tools/chocolateyinstall.ps1 seems to have an outdated Checksum.
I get:
ERROR: Checksum for 'C:\[...]\TableauPublicDesktop-64bit-2022-1-0.exe' did not meet 'b43f93f9a3051ca22284b86359bbf8c6b385bdd5053d8fb8bc68a27939eae389' for checksum type 'sha256'.

Package id: studio

Current package version: 2.22.11.4
Version to update to: 2.22.12.1

fastcopy.portable v3.86 [Approved]
fastcopy.portable package files upgrade completed. Performing other installation steps.
ERROR: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'File'. Specified method is not supported.
The upgrade of fastcopy.portable was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\fastcopy.portable\tools\chocolateyInstall.ps1'.
 See log for details.

Log:

2020-02-01 13:29:12,903 159996 [DEBUG] - Running 'ChocolateyScriptRunner' for fastcopy.portable v3.86 with packageScript 'C:\ProgramData\chocolatey\lib\fastcopy.portable\tools\chocolateyInstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\fastcopy.portable', installArguments: '', packageParameters: '',
2020-02-01 13:29:12,904 159996 [DEBUG] - Running 'C:\ProgramData\chocolatey\lib\fastcopy.portable\tools\chocolateyInstall.ps1'
2020-02-01 13:29:12,919 159996 [ERROR] - ERROR: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'File'. Specified method is not supported.
2020-02-01 13:29:12,935 159996 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\fastcopy.portable\tools\chocolateyInstall.ps1' -installArguments '' -packageParameters '''] exited with '-1'.

Hi there,

There is a new release since July 1 2019:
https://github.com/rizonesoft/Notepad3/releases/tag/RELEASE_5.19.630.2381

Describe the bug
The actual Checksum values for 10.2.1 published on the Nessus download page do not match the checksum values provided in the nessus-agent package. The error message shows that actual Checksum value of the downloaded .msi matches the Nessus published value and not the value in the nessus-agent package.

To Reproduce
choco install nessus-agent

Expected behavior
Successful install of package without providing any specific checksum parameters.

Error Message
Here are the published Checksums from the Nessus download page

nessus-agent v10.2.1
nessus-agent package files install completed. Performing other installation steps.
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
Error - hashes do not match. Actual value was '6ECF9CAC910B301FD74A5D22DD5480EB8ED972504AB785AA8799BE1334D1B3A5'.
Downloading nessus-agent 64 bit
  from 'https://www.tenable.com/downloads/api/v1/public/pages/nessus-agents/downloads/17738/download?i_agree_to_tenable_license_agreement=true'

Download of NessusAgent-10.2.1-x64.msi (-1 B) completed.
Error - hashes do not match. Actual value was '6ECF9CAC910B301FD74A5D22DD5480EB8ED972504AB785AA8799BE1334D1B3A5'.
ERROR: Checksum for 'C:\Users\----\AppData\Local\Temp\chocolatey\nessus-agent\10.2.1\NessusAgent-10.2.1-x64.msi' did not meet 'e59a4f3506f77b1ecdde7f92d287fa79368298146ac7487638ceb27056d6e144' for checksum type 'sha256'. Consider pass
the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary.
The install of nessus-agent was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\nessus-agent\tools\chocolateyinstall.ps1'.

Thanks

Package id: nessus-agent

Current package version: 10.3.0
Version to update to: 10.3.1

Ok, so I use this for the inconsolata package on chocolatey. When I submitted the newer version using this module a few months ago it worked great. Now when I try to uninstall using Uninstall-ChocolateyFont I get the following error:

WARNING: An error occured removing 'Inconsolata-Regular.ttf'.
ERROR: You cannot call a method on a null-valued expression.
inconsolata uninstall not successful.
Error while running 'C:\ProgramData\chocolatey\lib\inconsolata\tools\chocolateyUninstall.ps1'.
See log for details.
inconsolata not uninstalled. An error occurred during uninstall:
inconsolata uninstall not successful.

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

Failures

• inconsolata (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\inconsolata\tools\chocolateyUninstall.ps1'.
  See log for details.

The chocolatey.log adds:

2019-12-13 19:42:35,632 3272 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\inconsolata\tools\chocolateyUninstall.ps1' -installArguments '' -packageParameters '''] exited with '-1'.
2019-12-13 19:42:35,642 3272 [DEBUG] - Calling command ['"C:\WINDOWS\System32\shutdown.exe" /a']
2019-12-13 19:42:35,703 3272 [DEBUG] - Command ['"C:\WINDOWS\System32\shutdown.exe" /a'] exited with '1116'

Have you seen this before? I don't understand what's going on.

While the above error was from an uninstall on a non-existant font. I'm also getting the same error trying to upgrade an existing font. Is there a particular methodology you're supposed to use during upgrades that I'm not following?

Here's my entire chocolateyInstall.ps1 for the inconsolata package:

$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$url1 = 'https://github.com/googlefonts/Inconsolata/raw/v3.000/fonts/ttf/Inconsolata-Regular.ttf'
$url2 = 'https://github.com/googlefonts/Inconsolata/raw/v3.000/fonts/ttf/Inconsolata-Bold.ttf'

Get-ChocolateyWebFile `
  -PackageName $env:ChocolateyPackageName `
  -FileFullPath $toolsDir\Inconsolata-Regular.ttf `
  -Url $url1 `
  -Checksum '127875D255D4C5973CA57267A43BB9D1C04397E6C7D236984A595B6CDCB12B7C' `
  -ChecksumType SHA256 `

Get-ChocolateyWebFile `
  -PackageName $env:ChocolateyPackageName `
  -FileFullPath $toolsDir\Inconsolata-Bold.ttf `
  -Url $url2 `
  -Checksum '263FAA57F6C00C43A04E77DF7ABD5CB5CD4AAE9F93507002C1217E02641FC7E6' `
  -ChecksumType SHA256 `


Install-ChocolateyFont $toolsDir -multiple

I've tried changing the last bit to the following but that just uninstalls the fonts and still errors out trying to install the new one:

Uninstall-ChocolateyFont Inconsolata-Regular.ttf
Uninstall-ChocolateyFont Inconsolata-Bold.ttf
Install-ChocolateyFont $toolsDir -multiple

What am I missing?

Seems like the installation of Tabular Editor 2.14.2 is hanging.

Have tried manually running the choco install tabular-editor -y command from an elevated command prompt locally, but it hangs every time: (have also tried it via Azure DevOps, same issue)

C:\WINDOWS\system32>choco install tabular-editor -y
Chocolatey v0.10.10
Installing the following packages:
tabular-editor
By installing you accept licenses for the packages.
Progress: Downloading tabular-editor 2.12.4... 100%

tabular-editor v2.12.4 [Approved]
tabular-editor package files install completed. Performing other installation steps.
Installing tabular-editor...

https://github.com/teknowledgist/Chocolatey-packages/blob/master/automatic/wiztree/wiztree.nuspec#L16

LICENSE.text should be LICENSE.txt

Describe the bug
Wrong link: https://github.com/teknowledgist/Chocolatey-packages/blob/master/automatic/nasm/nasm.nuspec#L8

To Reproduce

Expected behavior
Correct link: https://github.com/teknowledgist/Chocolatey-packages/tree/master/automatic/nasm

Screenshots

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context

I had intended to convert fastcopy into an automatic package, but only half finished it.

How do you feel about moving those packages over into my repo?

https://www.3ds.com/products-services/draftsight-cad-software/download-draftsight/

I'll issue a PR later today.

Describe the bug
Upgrading nasm package causes this error:
ERROR: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'NewName'. Specified method is not supported.

To Reproduce
Steps to reproduce the behavior:

1. Upgrade non-latest nasm package

Expected behavior
No error.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Choco: latest

Additional context
Log:

2022-12-31 06:41:26,946 21632 [ERROR] - ERROR: Cannot convert 'System.Object[]' to the type 'System.String' required by parameter 'NewName'. Specified method is not supported.
2022-12-31 06:41:26,950 21632 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\nasm\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '' -preRunHookScripts $null -postRunHookScripts $null'] exited with '-1'.

Checking https://github.com/teknowledgist/Chocolatey-packages/tree/master/automatic/anaconda3 and how the distribution is separate from the navigator.
https://docs.anaconda.com/anaconda/navigator/update-navigator/
conda deactivate
conda update anaconda-navigator

Hi @teknowledgist,

the new version of Chimera seems to have problems with the installer-file. The installer is not imported into the nupkg. It looks like the webpage from UCSF has changed (https://www.cgl.ucsf.edu/chimera/download.html). They have no more direct links to their software. Instead the download-link(s) seem to be associated with a py-Script (chimera-get.py), that leeds to a "License Agreement"-page. Only after confirming you can now download the sources.

Do you have any idea how to solve this issue in the update.ps1? Thanks for your help! I'll also have a look and try to solve it ;)

Have a nice day!

For some reason my libs\lmms contained lmms-1.2.1-win32.exe and lmms-1.2.1-win64.exe as well as lmms-1.2.2-win32.exe and lmms-1.2.2-win64.exe

This caused this error

ERROR: Cannot process argument transformation on parameter 'file'. Cannot convert value to type System.String.

Because File and File64 contained 2 items, I assume.

And the package failed to install

The download links for the approved 2017 SP3 package on Chocolatey-packages and the updated 2018 SP0 package in this repo no longer work. Presumably these changed when 2018 SP1 was released.

cup miktex -debug -y -force prints among other things:

Parsing $env:ChocolateyPackageParameters and $env:ChocolateyPackageParametersSensitive for parameters
Downloading a "Basic" package set to install.
Running 'Get-UninstallRegistryKey' for 'miktex.install' with SoftwareName:'miktex*'
Registry uninstall keys on system: 222
Error handling check: 'Get-ItemProperty' fails if a registry key is encoded incorrectly.
Found 1 uninstall registry key(s) with SoftwareName:'miktex*'
ERROR: You cannot call a method on a null-valued expression.
 at <ScriptBlock>, C:\ProgramData\chocolatey\lib\miktex.install\tools\chocolateyinstall.ps1: line 71
at <ScriptBlock>, C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1: line 49
at <ScriptBlock>, <No file>: line 1
Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\miktex.install\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '''] exited with '-1'.
Calling command ['"C:\WINDOWS\System32\shutdown.exe" /a']
Command ['"C:\WINDOWS\System32\shutdown.exe" /a'] exited with '1116'
Capturing package files in 'C:\ProgramData\chocolatey\lib\miktex.install'
The upgrade of miktex.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\miktex.install\tools\chocolateyinstall.ps1'.
 See log for details.

The erroring line is

Expected:
Uninstall installed files without having to list them

Actual:
While it is possible to install a folder it is not possible to uninstall the fonts in that folder.

Possible Solution 1:
Let Uninstall-ChocolateyFont scan a folder and uninstall the filenames in that folder.

Possible Solution 2:
Log all successfully installed fonts into a file. To uninstall just reference that file. Together with the -multi-feature this would make maintaining font packages a lot easier, as install.ps and uninstall.ps would be the same for all packages and one would only have to add the files into the appropriate folder.

xplorer2 package installation is broken despite the download URL being fixed in this repo.

The xplorer2 package installation script at automatic/xplorer2/tools/chocolateyinstall.ps1 seems to have been updated here on github after a change in the download URL, but when attempting an install on my machine with choco install xplorer2, I get a script with the old URL (http://zabkat.com/xplorer2_lite_setup.exe) which is broken. The whole script, if [P]rinted, looks like this:

C:\WINDOWS\system32>choco install xplorer2
Chocolatey v0.10.15
Installing the following packages:
xplorer2
By installing you accept licenses for the packages.
Progress: Downloading xplorer2 4.3.0.2... 100%

xplorer2 v4.3.0.2 [Approved]
xplorer2 package files install completed. Performing other installation steps.
The package xplorer2 wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): P

------ BEGIN SCRIPT ------

$ErrorActionPreference = 'Stop'

$packageName = $env:ChocolateyPackageName
$url         = 'http://zabkat.com/xplorer2_lite_setup.exe'
$Checksum    = '09c8d8b225c5e677c68280f9730e8628c3aa72eff0ef7f3099c377f107db7cb8'

# silent install requires AutoHotKey
$ahkExe = 'AutoHotKey'
$toolsDir    = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$ahkFile = Join-Path $toolsDir 'chocolateyInstall.ahk'
$ahkProc = Start-Process -FilePath $ahkExe -ArgumentList "$ahkFile" -PassThru
$ahkId = $ahkProc.Id
Write-Debug "$ahkExe start time:`t$($ahkProc.StartTime.ToShortTimeString())"
Write-Debug "Process ID:`t$ahkId"

$packageArgs = @{
  packageName    = $packageName
  unzipLocation  = $toolsDir
  fileType       = 'EXE'
  url            = $url
  softwareName   = 'xplorer² lite*'
  checksum       = $Checksum
  checksumType   = 'sha256'
  silentArgs     = '/S'
  validExitCodes = @(0)
}
Install-ChocolateyPackage @packageArgs


------- END SCRIPT -------
Do you want to run this script?([Y]es/[N]o):

Not sure why the updated URL is not propagated to the live repository. What am I missing? Thanks in advance for any advice.

Upgrading QGIS from the choco package qgis from 3.22.1 to 3.24.1 fails with the following error:

ERROR: Cannot convert value "" to type "System.Version". Error: "Version string portion was too short or too long."

My guess is that the version number $LTRVersion is no longer properly detected and currently empty in automatic/qgis/tools/chocolateyinstall.ps1

bf78628#diff-6c6b7d8e41710ccf665625007012ac0504f143dd985e30c8c6e094d7f16c7732

The update script is looking for .exe links, which are not on the QGIS download page anymore, it should probably match .msi links instead. There's a line of text about them switching to MSI installers, I don't know when that happened.

https://github.com/teknowledgist/Chocolatey-packages/blob/master/automatic/qgis/update.ps1#L23-L28

Full log:

C:\WINDOWS\system32>choco upgrade qgis
Chocolatey v1.1.0
Upgrading the following packages:
qgis
By upgrading, you accept licenses for the packages.

You have qgis v3.22.1 installed. Version 3.24.1 is available based on your source(s).
Progress: Downloading QGIS 3.24.1... 100%

QGIS v3.24.1
qgis package files upgrade completed. Performing other installation steps.
The package QGIS wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): a

ERROR: Cannot convert value "" to type "System.Version". Error: "Version string portion was too short or too long."
The upgrade of qgis was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\QGIS\tools\chocolateyinstall.ps1'.
 See log for details.

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

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

Need to resize inside the LDV window - can't seem to grab the left edge of image display sub-window.

Would it be possible to add a package parameter to switch whether we want to install for all users (--shared=yes) or just for current user (--shared=no).

As I understand from looking in the code, in this line --shared is passed, which is equivalent to --shared=yes, so it's always installed for all users.

Bad checksums on the chocolatey package onedrive.
Please update your package.

User attempted:

Install-ChocolateyFont "Print Fonts*.otf" -multiple

While that exact command might be difficult, there could be a wildcard option.

http://dl-ak.solidworks.com/nonsecure/draftsight/2017SP03/DraftSight64.exe results in a file not found.

$ wget http://dl-ak.solidworks.com/nonsecure/draftsight/2017SP03/DraftSight64.exe
--2017-10-13 08:45:36--  http://dl-ak.solidworks.com/nonsecure/draftsight/2017SP03/DraftSight64.exe
Resolving dl-ak.solidworks.com... 165.254.47.121, 165.254.47.137
Connecting to dl-ak.solidworks.com|165.254.47.121|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-10-13 08:45:36 ERROR 404: Not Found.

This happens when attempting "choco upgrade miktex.install" from "20.7" to "20.11".

In my case, "$key.UninstallString" has the value "C:\Users\mdiers\AppData\Local\Programs\MiKTeX\miktex/bin/x64\miktex-console.exe --start-page cleanup".

Determining "$InstallDir" from that results in an error:

$InstallDir = split-path ($key.UninstallString.split('"')[1])

PS C:\WINDOWS\system32> split-path("C:\Users\mdiers\AppData\Local\Programs\MiKTeX\miktex/bin/x64\miktex-console.exe --start-page cleanup".split('"')[1])
Split-Path : Cannot bind argument to parameter 'Path' because it is null.
At line:1 char:11
+ split-path("C:\Users\mdiers\AppData\Local\Programs\MiKTeX\miktex/bin/ ...
+           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Split-Path], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.SplitPathCo
   mmand

Suggest using "$key.UninstallString" itself as argument to "split-path" when "$key.UninstallString.split('"')[1]" is null.

Package id: dopdf

Current package version: 11.7.352
Version to update to: 11.7.357

Also, because the installer that gets downloaded in the package is the 357 version, currently you get a mismatch of the checksum mismatch upon attempting to install.

Thanks

Package id: nessus-agent

Current package version: 10.2.1.20221110
Version to update to: 10.3.0

Thanks for all your work.

See mkevenaar/chocolatey-packages#114 for cross-reference

I've run into a problem upgrading DraftSight when the "DraftSight API Service" is running.

Stopping the service allows the choco upgrade to work properly.

I see chocolateybeforemodify.ps1 can be put into the tools directory and the service could be stopped before the upgrade?

I'm having a problem with uninstalling (or upgrading) v3.52 of this package. Although the installer installed the program files into C:\Program Files\FastCopy (that's where the files currently are), Chocolatey's uninstaller script seems to look for setup.exe in C:\Program Files (x86)\FastCopy (at least that's what Choco's error message says). Of course, it doesn't find it, so uninstalling fails.

As mentioned in chocolatey/boxstarter#455, because the current architecture of Boxstarter has a single PowerShell session then if multiple packages try to install fonts then they will fail when the Add-Type cmdlet is called by subsequent installs (as the type already exists then).

A possible mitigation would be either to check if the type already exists, or set an -ErrorAction SilentlyContinue on that call.

https://www.3ds.com/products-services/draftsight-cad-software/free-download/

If you'd be interested in submitting a pull request to http://github.com/daxstudio/daxstudio I'd be interested in incorporating your DAX Studio package into our repo so that we can update it automatically as part of our build process so that chocolatey always has the latest version.

It looks like the pandemics is helping v2 development.

https://github.com/Lymphatus/caesium-image-compressor/releases

Version 2.1.0 of the anaconda navigator is available

DraftSight 2018 fails Automated Package Tests, the dreaded 1603 error. Snippet from the verifier.

 ERROR: Running ["C:\Windows\System32\msiexec.exe" /i "C:\Users\Administrator\AppData\Local\Temp\chocolatey\DraftSight.2018.00\DraftSight.msi" /qn /norestart /l*v "C:\Users\Administrator\AppData\Local\Temp\chocolatey\DraftSight.2018.00.MsiInstall.log" ALLUSERS=1 ] was not successful. Exit code was '1603'. 

List tracking stuff that might be helpful

1. Old VirtualBox version requirement
2. How to locate the cause of error code 1603 in a verbose MSI log file
3. Windows Server 2016 testing environment

I think the problem is the package verifier runs Windows Server 2012 R2 and DraftSight 2019 SP0 System Requirements specifically states, "Windows Server 2012 R2 64-bit x86 (No longer supported by R2017x)".

We all know this day was coming. The Microsoft treadmill keeps moving and it's get updated or get left behind. It's the main reason I did PR #23 on chocolatey-test-environment.

I'll do more troubleshooting. But when the vendors specifically states your operating system is not supported I think we need to petition @ferventcoder to update the operating system in chocolatey-test-environment or petition "the powers" for an exemption in the package verifier for DraftSight 2018.

OR

A way to identify the package verifier's operating system and support multiple testing environments.

When attempting to run cinst miktex.install I receive the following error:

====
Unhandled Exception: System.ApplicationException: Cannot combine a path with ':' attempted to combine 'C:\miktex-staging\stable\texmfs\install\miktex\bin\x64\miktexsetup_standalone.exe' with 'C:\ProgramData\chocolatey\lib\miktex.install\tools'
at chocolatey.infrastructure.filesystem.DotNetFileSystem.combine_paths(String leftItem, String[] rightItems)
at chocolatey.licensed.infrastructure.app.powershell.GetChocolateyUnzipCmdlet.#=zjaaKepb1B5RF3KWt$A==.#=zgIosR4fy$jJeOrdenw==(Object #=zH6OPSr4=, DataReceivedEventArgs #=z4a5vhrk=)
at System.Diagnostics.Process.OutputReadNotifyUser(String data)
at System.Diagnostics.AsyncStreamReader.FlushMessageQueue()
at System.Diagnostics.AsyncStreamReader.GetLinesFromStringBuilder()
at System.Diagnostics.AsyncStreamReader.ReadBuffer(IAsyncResult ar)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.IO.Stream.ReadWriteTask.System.Threading.Tasks.ITaskCompletionAction.Invoke(Task completingTask)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.Finish(Boolean bUserDelegateExecuted)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution)
at System.Threading.ThreadPoolWorkQueue.Dispatch()

===

I think the issue is being caused by the tools\miktexsetup-4.0-20.12-x64.zip file being packaged incorrectly. Windows is unable to decompress the file ( file explorer shows the contents as empty ) whereas 7zip shows a series of nested folders starting with a folder named "c:", which I think is source of the problem. The previous version of this file ( tools\mitexsetup-4.0-x64.zip ) does not contain any folders, only the miktexsetup.exe file.