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

Fixes for --no-restore still doing a restore #3486

Merged
merged 1 commit into from
Jan 18, 2019

Conversation

BlythMeister
Copy link
Contributor

@BlythMeister BlythMeister commented Jan 17, 2019

Fixes #3485 and #3449

The version number used in the PaketPropsVersion in https://github.com/fsprojects/Paket/blob/master/src/Paket.Core/Installation/RestoreProcess.fs#L328 is 5.185.3 which does not match the targets.
This means that PaketRestoreRequired is always true, even if you have literally just built.

@baronfel
Copy link
Contributor

Is there a way to template this value so that it could be populated on release builds? I'm just worried about reintroducing this failure transparently down the line.

Either that or a more low tech fix: a test that checks if the version in the embedded targets matches the current assembly version?

@BlythMeister BlythMeister changed the title The PaketPropsVersion in the targets does not match the version written to the props Fixes for --no-restore still doing a restore Jan 17, 2019
@BlythMeister
Copy link
Contributor Author

@baronfel have added comments above the 2 values which need to be in sync.

These appear to be values for the format of the data since the value in the props does not match that of paket itself.

Have also made an additional change to the beforetarget to make paket mirror the order of the standard nuget restore target.

@BlythMeister
Copy link
Contributor Author

Scrap that before target stuff...that's just plain wrong...will rebase and fix up this PR :D

Also add a comment to hint that these should be kept in sync
@BlythMeister
Copy link
Contributor Author

also looking at the changes which changed one of these files, i think it was known that they need to be kept in sync...but the wrong targets was changed :)

828f9e4

The one that this repo actually uses to build was changed, not the one that paket puts into repos :D

@forki
Copy link
Member

forki commented Jan 18, 2019 via email

@BlythMeister
Copy link
Contributor Author

i'm an experienced archaeology driven developer ;)

@forki forki merged commit 0dd27ac into fsprojects:master Jan 18, 2019
@BlythMeister BlythMeister deleted the norestore branch May 11, 2021 16:06
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

Successfully merging this pull request may close these issues.

None yet

3 participants