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

paket restore/install resulted in "The profile 'portable-net45+win8+wp8+wp81+wpa81' is not a known profile. Please tell the package author." #2495

Closed
piotr07da opened this issue Jul 7, 2017 · 9 comments

Comments

@piotr07da
Copy link

Description

In paket version 4.8.8 after paket install I have got this:

  Microsoft.AspNet.WebApi.Client (5.2.3)
  Microsoft.Net.Http (>= 2.2.22) - framework: portable-wp80+win+wp81+wpa81
  Newtonsoft.Json (>= 6.0.4) - framework: >= net45, portable-wp80+win+wp81+wpa81

And in this case paket restore returns no errors.

In paket version 5.0.0 after paket install I have got this:

  Microsoft.AspNet.WebApi.Client (5.2.3)
  Microsoft.Net.Http (>= 2.2.22) - restriction: && (< net45) (>= portable-net45+win8+wp8+wp81+wpa81)
  Newtonsoft.Json (>= 6.0.4) - restriction: >= portable-net45+win8+wp8+wp81+wpa81

And in this case paket restore returns:
"The profile 'portable-net45+win8+wp8+wp81+wpa81' is not a known profile. Please tell the package author." error.

Why this is not know profile? Is there way to solve this problem? Currently I installed 4.8.8 version.

Repro steps

  1. Create paket.dependencies with:

       nuget Microsoft.AspNet.WebApi 5.2.0
       nuget Microsoft.AspNet.WebApi.Client 5.2.3
       nuget Microsoft.AspNet.WebApi.Core 5.2.3
       nuget Microsoft.AspNet.WebApi.WebHost 5.2.3
       nuget Microsoft.Net.Http 2.2.22
    
  2. Run paket install

@matthid
Copy link
Member

matthid commented Jul 7, 2017

The known profiles are listed in http://embed.plnkr.co/03ck2dCtnJogBKHJ9EjY
While we support others those are the well defined ones with separate reference assemblies installed.
We print a warning because using a different profile might indicate a packaging error.
Problematic package is https://www.nuget.org/packages/Microsoft.AspNet.WebApi.Client

It is not a paket bug, because nuget apparently can't associate the profile with a known profile either: http://nugettoolsdev.azurewebsites.net/4.0.0/parse-framework?framework=portable-net45%2Bwin8%2Bwp8%2Bwp81%2Bwpa81. Compare this with http://nugettoolsdev.azurewebsites.net/4.3.0-beta1-2418/parse-framework?framework=portable-net45%2Bnetcore45%2Bwpa81%2Bwp8 which detects the 259 profile.

To be honest I'm not a complete expert on this so we might need a nuget expert to clarify. But IMHO one should only use one of the officially supported profiles (because otherwise nuget/msbuild are selecting the next best matching profile anyway if I understood that correctly). Therefore we print the warning at the moment.

Sadly there is currently nothing you can do as a user to get rid of this warning besides not using this package and besides reporting this to the package authors...

@sahgilbert
Copy link

I've run into the same problem. Are we any closer to a fix?

@forki
Copy link
Member

forki commented Jul 17, 2017

Is it an official target?

@sahgilbert
Copy link

Not quite sure what you mean by that. I'm running Paket version 5.7.2 on Appveyor, and each build seems to just hang after hitting this point -

The profile 'portable-net45+win8+wp8+wp81+wpa81' is not a known profile. Please tell the package author.
Could not detect any platforms from 'xamarintvos10'
Could not detect any platforms from 'xamarinwatchos10'
The profile 'portable-net45+win8+wp8+wp81+wpa81' is not a known profile. Please tell the package author.

@matthid
Copy link
Member

matthid commented Jul 17, 2017

@simonalexandergilbert This issue is about the warning, a "hang" is definitely a different issue... Please open a new issue with a verbose log for the hang...

@sahgilbert
Copy link

Ok, thank you.

@haf
Copy link
Member

haf commented Aug 15, 2017

How do I know what package paket is warning about? The warning comes at the end of resolving all packages?

@forki
Copy link
Member

forki commented Aug 15, 2017 via email

@matthid
Copy link
Member

matthid commented Aug 20, 2017

This should be fixed as soon as #2632 is merged.
With "fixed" we mean paket will tell you which package is to blame.

@matthid matthid closed this as completed Aug 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants