Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(gpg4win) ERROR: Cannot process argument transformation on parameter 'file'. Cannot convert value to type System.String. #2608

Open
2 tasks done
opoplawski opened this issue Dec 31, 2024 · 1 comment
Labels

Comments

@opoplawski
Copy link
Contributor

Checklist

  • I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
  • I have verified that this is happening in the latest available version of the package.

Chocolatey Version

2.4.1

Chocolatey License

None

Package Version

4.3.1 -> 4.0.0

Current Behaviour

Upgrading the following packages:
  gpg4win
  By upgrading, you accept licenses for the packages.
  gpg4win|4.3.1|4.4.0|false
  Downloading package from source 'https://chocolatey.org/api/v2/'
  
  gpg4win v4.4.0 [Approved]
  gpg4win package files upgrade completed. Performing other installation steps.
  ERROR: Cannot process argument transformation on parameter 'file'. Cannot convert value to type System.String.
  The upgrade of gpg4win was NOT successful.
  Error while running 'C:\\ProgramData\\chocolatey\\lib\\Gpg4win\\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
   - gpg4win (exited -1) - Error while running 'C:\\ProgramData\\chocolatey\\lib\\Gpg4win\\tools\\chocolateyInstall.ps1'.
   See log for details.

Expected Behaviour

Successful upgrade

Steps To Reproduce

  1. install gpg4win 4.3.1
  2. upgrade to 4.4.0

Environment

- Operating System: Microsoft Windows NT 10.0.22631.0
- PowerShell Version: 5.1.22621.4391
- Shell:

Chocolatey Log

2024-12-31 06:10:16,319 3092 [DEBUG] - ---------------------------Script Execution---------------------------^M
2024-12-31 06:10:16,321 3092 [DEBUG] - Running 'ChocolateyScriptRunner' for Gpg4win v4.4.0 with packageScript 'C:\ProgramData\chocolatey\lib\Gpg4win\tools\chocolateyInstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\Gpg4win', installArguments: '', packageParameters: '', preRunHookScripts: '', postRunHookScripts: '',^M
2024-12-31 06:10:16,327 3092 [DEBUG] - Running package script 'C:\ProgramData\chocolatey\lib\Gpg4win\tools\chocolateyInstall.ps1'^M
2024-12-31 06:10:16,348 3092 [DEBUG] - Running Get-PackageParameters ^M
2024-12-31 06:10:16,350 3092 [DEBUG] - Parsing $env:ChocolateyPackageParameters and $env:ChocolateyPackageParametersSensitive for parameters^M
2024-12-31 06:10:16,367 3092 [ERROR] - ERROR: Cannot process argument transformation on parameter 'file'. Cannot convert value to type System.String.^M


### Anything else?

_No response_
@opoplawski opoplawski added the Bug label Dec 31, 2024
Copy link

Thanks for raising this issue!

The packages within this repository are maintained by a small team of volunteer Community Maintainers, in their own time. Their time, like yours is important. Please help them by not wasting it.

This is a community repository where the expectation is that everybody will get involved by raising pull requests to fix problems they find. This will also allow that problem to be fixed more quickly as you don't have to wait for a member of the Community Maintainer Team to pick it up.

If you are unable to fix the issue yourself, the Community Maintainers Team will look at it when time allows. There are no service level agreements, nor should there be any expectation on when people can resolve issues in their own time.

A few dos and don'ts:

  • Do provide as much information as you can in any issue that you raise.
  • Don't complain that an issue has not yet been picked up or resolved. You are expected to help out in this community maintained repository. If you are unable to do so, don't complain when others don't adhere to your timelines. There is no SLA nor should you have any expectation of one.
  • Do read the CONTRIBUTING and COMMITTERS documentation before raising a pull request as it contains valuable information on what automation is used in this repository.
  • Do read the Code of Conduct.
  • Don't post your frustration in comments. The Community Maintainers Team are not a punching bag for your frustration. You will only end up banned from the repository.

Thank you.
(Automatically posted message)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant