You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PackageManagement\Install-Package : The module 'PSScriptAnalyzer' cannot be installed because the catalog signature in '
PSScriptAnalyzer.cat' does not match the hash generated from the module.
At C:\program files\powershell\6-preview\Modules\PowerShellGet\1.6.0\PSModule.psm1:2057 char:21
+ ... $null = PackageManagement\Install-Package @PSBoundParameters
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Exception
+ FullyQualifiedErrorId : InvalidCatalogSignature,ValidateAndGet-AuthenticodeSignature,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage
After all this time, maybe PowerShellGet / PackageManagement should just punt on this catalog signing feature because NOBODY can seem to publish their modules correctly - including Microsoft.
Now I know that I can use -SkipPublisherCheck to make the install work but this is a lousy user experience as I try to get folks to install from the PSGallery.
Environment data
>$PSVersionTable
Name Value
---------
PSVersion 6.1.0-preview.2
PSEdition Core
GitCommitId v6.1.0-preview.2
OS Microsoft Windows 10.0.17134
Platform Win32NT
PSCompatibleVersions {1.0,2.0,3.0,4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0> (Get-Module-ListAvailable PSScriptAnalyzer).Version |ForEach-Object { $_.ToString() }
1.17.0
The text was updated successfully, but these errors were encountered:
@edyoung Is there any way to prevent modules from being published that have this problem - catalog sig mismatch? UPDATE: nevermind, I saw your response to my issue in the PowerShellGet project.
Before submitting a bug report:
Steps to reproduce
From PS Core 6.1 Preview 2:
Expected behavior
It just works!
Actual behavior
It fails with this error msg:
After all this time, maybe PowerShellGet / PackageManagement should just punt on this catalog signing feature because NOBODY can seem to publish their modules correctly - including Microsoft.
Now I know that I can use
-SkipPublisherCheck
to make the install work but this is a lousy user experience as I try to get folks to install from the PSGallery.Environment data
The text was updated successfully, but these errors were encountered: