fsprojects / fsprojects/Paket

Error: One Paket file '' is missing while restoring

Open
#4,283 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

needs triage
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

I'm getting an unexpected error.

\.paket\Paket.Restore.targets(226,3): error : One Paket file '' is missing while restoring Web.csproj. Please delete
 'paket-files/paket.restore.cached' and call 'paket restore'. [C:\dev\myrepo\src\Web\Web.
csproj]
Repro steps

I'm using paket with an System.Web project (for SDK style csproj)
<Project ToolsVersion="12.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

I used the paket convert-from-nuget command to set paket up.

I'm then trying to do a paket install, interestingly another proj in the solution is also missing a dll from a referenced package. Not sure if this is related.

Expected behavior

Package install works with no errors.

Actual behavior

I get the error Paket.Restore.targets(226,3): error : One Paket file '' is missing while restoring

Known workarounds

It seems to install correctly and a following restore has no errors.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported failure at .paket/Paket.Restore.targets line 226, using the SDK-style System.Web project created by paket convert-from-nuget. Reproduce paket install and inspect paket-files/paket.restore.cached, then run paket restore; done means package installation and restore complete without the missing-file error.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.