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

The `Paket.Restore.targets` is not in `.paket` directory after boostrapping or restore #2817

Closed
enricosada opened this Issue Oct 3, 2017 · 10 comments

Comments

Projects
None yet
4 participants
@enricosada
Collaborator

enricosada commented Oct 3, 2017

Description

The Paket.Restore.targets is not in .paket directory after boostrapping or restore

Repro steps

.paket\paket.bootstrapper.exe
.paket\paket.exe restore

Expected behavior

the Paket.Restore.targets is created

Actual behavior

the Paket.Restore.targets is not created

Known workarounds

Run install or commit the Paket.Restore.targets to repository.

Note, is not a bug, atm is by design.
Just checking if is not better to create the Paket.Restore.targets on restore? so is aligned with current paket version (instead of be commited in repo).
Lots of build script are just boostrap + restore

@enricosada enricosada closed this Oct 3, 2017

@forki forki reopened this Oct 3, 2017

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Oct 3, 2017

Member

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

Member

forki commented Oct 3, 2017

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

@enricosada

This comment has been minimized.

Show comment
Hide comment
@enricosada

enricosada Oct 3, 2017

Collaborator

well, it should be always aligned with paket version, is just a temp file (required before dotnet restore just for techinical reason) .
Change it in the middle of dotnet restore maybe is not that good (but the target file is already loaded so shouldnt matter)
so replace if different is not that bad, is like updating paket each build.

Collaborator

enricosada commented Oct 3, 2017

well, it should be always aligned with paket version, is just a temp file (required before dotnet restore just for techinical reason) .
Change it in the middle of dotnet restore maybe is not that good (but the target file is already loaded so shouldnt matter)
so replace if different is not that bad, is like updating paket each build.

@forki forki closed this in 66624e8 Oct 3, 2017

@enricosada

This comment has been minimized.

Show comment
Hide comment
@enricosada

enricosada Oct 3, 2017

Collaborator

Fixed by v5.104.0 now is created after restore

Collaborator

enricosada commented Oct 3, 2017

Fixed by v5.104.0 now is created after restore

@andygjp

This comment has been minimized.

Show comment
Hide comment
@andygjp

andygjp Oct 3, 2017

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,
Andy

image

andygjp commented Oct 3, 2017

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,
Andy

image

@andygjp

This comment has been minimized.

Show comment
Hide comment
@andygjp

andygjp Oct 3, 2017

Actually, ignore that - it seems the target file was introduced when I updated FAKE.

Sorry,
Andy

andygjp commented Oct 3, 2017

Actually, ignore that - it seems the target file was introduced when I updated FAKE.

Sorry,
Andy

@TheAngryByrd

This comment has been minimized.

Show comment
Hide comment
@TheAngryByrd

TheAngryByrd Feb 15, 2018

Contributor

If I'm looking to debug Paket.Restore.targets on a repository is there a way to tell paket to not autodownload this file on restore?

Contributor

TheAngryByrd commented Feb 15, 2018

If I'm looking to debug Paket.Restore.targets on a repository is there a way to tell paket to not autodownload this file on restore?

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Feb 16, 2018

Member

it does not download - it extracts it from resources

Member

forki commented Feb 16, 2018

it does not download - it extracts it from resources

@TheAngryByrd

This comment has been minimized.

Show comment
Hide comment
@TheAngryByrd

TheAngryByrd Feb 16, 2018

Contributor

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?

Contributor

TheAngryByrd commented Feb 16, 2018

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?

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Feb 16, 2018

Member
Member

forki commented Feb 16, 2018

@TheAngryByrd

This comment has been minimized.

Show comment
Hide comment
@TheAngryByrd

TheAngryByrd Feb 16, 2018

Contributor

Ok cool 😎

Contributor

TheAngryByrd commented Feb 16, 2018

Ok cool 😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment