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

3.3.5: paket.dependencies and paket.lock are out of sync ALWAYS #1766

Closed
konste opened this issue Jun 27, 2016 · 7 comments
Closed

3.3.5: paket.dependencies and paket.lock are out of sync ALWAYS #1766

konste opened this issue Jun 27, 2016 · 7 comments

Comments

@konste
Copy link
Contributor

@konste konste commented Jun 27, 2016

For attached paket.dependencies and packet.lock Paket always reports that they are out of sync! You can delete paket.lock and let Paket 3.3.5 to regenerate it (with Paket install) and immediately the next Paket restore command would report that they are out of sync!

paket.dependencies.txt
paket.lock.txt

@forki
Copy link
Member

@forki forki commented Jun 27, 2016

Thanks for reporting. Will look at it tomorrow
On Jun 27, 2016 9:03 PM, "Konstantin Erman" notifications@github.com
wrote:

For attached paket.dependencies and packet.lock Paket always reports that
they are out of sync! You can delete paket.lock and let Paket 3.3.5 to
regenerate it (with Paket install) and immediately the next Paket restore
command would report that they are out of sync!

paket.dependencies.txt
https://github.com/fsprojects/Paket/files/335631/paket.dependencies.txt
paket.lock.txt
https://github.com/fsprojects/Paket/files/335632/paket.lock.txt


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1766, or mute the thread
https://github.com/notifications/unsubscribe/AADgND8ApEWG6Jc1I7PC1zvqooanHKBwks5qQB6GgaJpZM4I_Z0-
.

@forki forki closed this in 1362dd0 Jun 28, 2016
@forki
Copy link
Member

@forki forki commented Jun 28, 2016

please retry with 3.3.6

Btw: you can also get rid of the framework restrictions on the packages - I mean you are already restricting the full group. (that was also the issue that paket did not detect)

@konste
Copy link
Contributor Author

@konste konste commented Jun 29, 2016

Here is what I don't understand despite all the efforts: we have internal package which intentionally targets NET35 and nothing else. What shall I write in paket.dependencies and paket.references so that the package is still picked up for .NET 4.6.1 projects? Whatever I do I get "Package BitTitan.DeviceManagement contains libraries, but not for the selected TargetFramework net461 in project...". I want those libraries to be referenced anyway, they are compatible with all versions of .NET
How?

@forki
Copy link
Member

@forki forki commented Jun 29, 2016

This is unrelated to the issue right?
Can you please open new one?

@konste
Copy link
Contributor Author

@konste konste commented Jun 29, 2016

Done.

@daniellittledev
Copy link
Contributor

@daniellittledev daniellittledev commented Mar 6, 2017

This issue seems to be back in 3.36.1

@forki
Copy link
Member

@forki forki commented Mar 7, 2017

Please open a new issue with a repro case. I assume it's a new version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.