The Paket.Restore.targets is not in .paket directory after boostrapping or restore
#2817
Comments
|
Question is a bit if we should overwrite with latest version when it's already there. I don't think we should. But creating it when it's missing is probably a good thing |
|
well, it should be always aligned with paket version, is just a temp file (required before |
|
Fixed by v5.104.0 now is created after restore |
|
Hi, I think there might still be a related issue. Just cloned my repo to my machine and kicked off a build but I get: "The system cannot find the path specified." The .paket\Paket.Restore.targets is only 2.4KB. When it worked, the same file was 15.2KB. See attached screenshot. Cheers,
|
|
Actually, ignore that - it seems the target file was introduced when I updated FAKE. Sorry, |
|
If I'm looking to debug |
|
it does not download - it extracts it from resources |
|
Sorry, regardless of the mechanism of how the file gets there, is there a way to tell paket to not overwrite the file when I have changed it to include more debug messages? If not, would an environment variable be appropriate? |
|
Yeah would accept a pr which introduces a env variable
Am 16.02.2018 13:48 schrieb "Jimmy Byrd" <[email protected]>:
… Sorry, regardless of the mechanism of how the file gets there, is there a
way to tell paket to not overwrite the file when I have changed it to
include more debug messages? If not, would an environment variable be
appropriate?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2817 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNE5dkgHWy0XssjCrUikqnbrA2wKbks5tVXkMgaJpZM4Pr6Cw>
.
|
|
Ok cool 😎 |
Description
The
Paket.Restore.targetsis not in.paketdirectory after boostrapping or restoreRepro steps
Expected behavior
the
Paket.Restore.targetsis createdActual behavior
the
Paket.Restore.targetsis not createdKnown workarounds
Run
installor commit thePaket.Restore.targetsto repository.Note, is not a bug, atm is by design.
Just checking if is not better to create the
Paket.Restore.targetson restore? so is aligned with current paket version (instead of be commited in repo).Lots of build script are just boostrap restore
The text was updated successfully, but these errors were encountered: