Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

PS Core 6.0 RC2 issue with 2.0.0 version not being catalog signed

See original GitHub issue

Environment data

PS version: 6.0.0-rc.2
PSReadline version: 1.2 - but I'm trying to get to 2.0
os: 10.0.16299.15 (WinBuild.160101.0800)
PS file version: 6.0.0

Steps to reproduce or exception report

Install PS Core 6.0 rc2 and execute:

PS C:\Program Files\PowerShell\6.0.0-rc.2> Install-Module psreadline -RequiredVersion 2.0.0-beta1 -AllowPrerelease -Scope CurrentUser

This is what I get:

PackageManagement\Install-Package : The version '2.0.0' of the module 'PSReadLine' being installed is not catalog signed. Ensure that the version '2.0.0' of the module 'PSReadLine' has the catalog file 'PSReadLine.cat' and signed with the same publisher 'CN=Microsoft Root Certificate Authority 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US' as the previously-installed module 'PSReadLine' with version '1.2' under the directory 'C:\program files\powershell\6.0.0-rc.2\Modules\PSReadLine'. If you still want to install or update, use -SkipPublisherCheck parameter.
At C:\program files\powershell\6.0.0-rc.2\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 : ModuleIsNotCatalogSigned,Validate-ModuleAuthenticodeSignature,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

I should probably mention there is a simple workaround, use -SkipPublisherCheck but still, we shouldn’t need a workaround.