mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-25 16:45:53 +03:00
[GH-ISSUE #236] Ubuntu 16.04 NBFC build gives error #208
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ndasim on GitHub (May 6, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/236
There are also some warning messages, I'm putting error messages;
Errors:
@hirschmann commented on GitHub (May 7, 2017):
Seems like at least one nuget package could not be restored:
Try to run nuget.exe in the nfbc-master folder:
mono nuget.exe restoreIf there is no nuget.exe download it:
wget http://nuget.org/nuget.exeand then import Mozilla trusted root certificates into the mono certificates store:
mozroots --import --syncThen try to restore the packages again.
@x42x64 commented on GitHub (Jul 1, 2017):
Kind of the same problem here - after trying
mono nuget.exe restorethe result is:I'm using mono 5.0.1.1 and I'm on the master branch of this repo. Any ideas?
Thanks!
@x42x64 commented on GitHub (Jul 1, 2017):
Ok, I fixed it by using a stable nuget version.
For some reason
wget http://nuget.org/nuget.exepulls the most recent nuget version (4.3.0-preview3) and not the last stable one. With the last stable 4.1.0 I was able to build nbfc sucessfully on Ubuntu 16.04@hirschmann commented on GitHub (Jul 10, 2017):
Actuelly, the version that wget pulls is outdated. Therefore the build script updates nuget via
mono nuget.exe update -selfUnfortunately nuget always updates to the latest version, no matter if it's stable or a preview. According to the nuget team this behavior is intended.
I currently don't have a solution for this problem. Some of NBFC's dependencies require an up to date nuget.exe, so I can't just remove the self update from the build script.
@hirschmann commented on GitHub (Jul 14, 2017):
I think I have found a good solution to the "nuget update problem":
92e7edf4a431d43285c6The build scripts now download the "latest recommended version" of nuget and update nuget manually, if the attempt to restore the packages fails.