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.

5.248.0, Error during parsing paket.lock. Invalid parameter 'netcoreapp5.0'

See original GitHub issue

Description

After doing a dotnet paket update/install with paket > 5.245.0, attempting to do a dotnet restore results in the error:

Paket failed with
  -> Error during parsing of 'xxx/paket.lock'.
  -> Error during parsing of 'xxx/paket.lock'.
  Performance:
  -> failed to parse line '      System.Reflection.Emit.ILGeneration (>= 4.7) - restriction: || (&& (== netcoreapp2.0) (>= netcoreapp5.0)) (&& (== netcoreapp2.0) (< netstandard1.1)) (&& (== netcoreapp2.0) (< netstandard2.0)) (&& (== netcoreapp2.0) (>= uap10.1)) (== netstandard2.0)' (invalid parameter 'netcoreapp5.0' after >= or < in '>= netcoreapp5.0)) (&& (== netcoreapp2.0) (< netstandard1.1)) (&& (== netcoreapp2.0) (< netstandard2.0)) (&& (== netcoreapp2.0) (>= uap10.1)) (== netstandard2.0)') (Could not parse 'framework: restriction: || (&& (== netcoreapp2.0) (>= netcoreapp5.0)) (&& (== netcoreapp2.0) (< netstandard1.1)) (&& (== netcoreapp2.0) (< netstandard2.0)) (&& (== netcoreapp2.0) (>= uap10.1)) (== netstandard2.0)' as key/value pairs.)
   - Runtime: 585 milliseconds
        -  invalid parameter 'netcoreapp5.0' after >= or < in '>= netcoreapp5.0)) (&& (== netcoreapp2.0) (< netstandard1.1)) (&& (== netcoreapp2.0) (< netstandard2.0)) (&& (== netcoreapp2.0) (>= uap10.1)) (== netstandard2.0)'
        -  Could not parse 'framework: restriction: || (&& (== netcoreapp2.0) (>= netcoreapp5.0)) (&& (== netcoreapp2.0) (< netstandard1.1)) (&& (== netcoreapp2.0) (< netstandard2.0)) (&& (== netcoreapp2.0) (>= uap10.1)) (== netstandard2.0)' as key/value pairs.
        -> invalid delimiter at position 22

Known workarounds

Downgrade paket to 5.245.0. Revert any changes to paket.lock file. Run dotnet paket update/install again.

Issue Analytics

State:
Created 3 years ago
Comments:13 (7 by maintainers)

Top GitHub Comments

1reaction

forkicommented, Oct 22, 2020

You may want to put

version 5.251.0

at top of your paket.dependencies file

0reactions

mpheltcommented, Oct 22, 2020

What makes paket.bootstrapper.exe (5.251.0) to actually download paket.exe 5.251.0?

Top Results From Across the Web

release-notes

Allow to parse DNXCore in lock file and be backwards compatible again ... because it is not valid on OSX - https://github.com/fsprojects/Paket/pull/3298 ...