Closed pedake closed 2 years ago
build is still working with dotnet 5.0 (tested with version 2022.8.4)
build is still working with dotnet 5.0 (tested with version 2022.8.4)
Did you try generating a license? That's were it failed for me.
@h44z Further more, attempting to build BitBetter on a clean updated copy of Debian Bullseye results in the following:
A modified version of what @pedake suggested results in the expected successful build:
grep -RiIl "5\.0" | xargs sed -i 's/5.0/6.0/g'
I will check that later. On my debian 11 installation it works with dotnet 5, not a fresh installation though...
I can confirm this as well, updating to use .Net 6.0 resolved the build issues.
Perhaps @h44z downloaded the 5.0 framework, as mentioned in the OP and suggested by the failed build, at some point and so his builds do not fail. Either way, I believe that, perhaps, this issue should be reopened until fully resolved either by adding instructions to the README about installing 5.0 framework or updating the project to use 6.0.
I am honestly curious, is there a reason we wouldn't want to utilize 6.0?
I'm having the same problem on Ubuntu 20.04.4 (existing installation). Managed to get the build to complete successfully by using the helpful workaround from @pedake above.
24 hours later though and I'm getting an error relating to invalid license. Have tried re-running the license generator but it's not working. Have also tried rebuilding the licencegen but still having the same issue. It looks like it's not generating the cert.
Need to nip out now but will try creating the cert manually and report back with my findings.
24 hours later though and I'm getting an error relating to invalid license. Have tried re-running the license generator but it's not working. Have also tried rebuilding the licencegen but still having the same issue. It looks like it's not generating the cert.
@oliverjnash I used a modified version of what @pedake suggested because the original one erroneously changed 36500 to 366.00 in ~/BitBetter/.keys/generate-keys,sh, which results in keys not being generated.
Either go into that file and change 366.00 to 36500 and rebuild, or start over and use:
grep -RiIl "5\.0" | xargs sed -i 's/5.0/6.0/g'
Edit: Also, I did not require downloading any additional framework files. I simply ran the above command on a newly installed BitBetter and it all worked.
@Ayitaka I think you read my mind. Literally in the process of doing that now. Thanks so much for commenting! Will report back shortly 👍
Thanks @Ayitaka, that's worked perfectly.
The only oddity I noticed when generating a new licence is that just running:
./run.sh interactive
doesn't seem to work, even when the keys are in the default directory.
I had to run:
./run.sh /BitBetter/.keys/cert.pfx interactive
in order for it to complete. It appears to have worked as expected when including the absolute path to the .pfx.
The only oddity I noticed when generating a new licence is that just running:
./run.sh interactive
doesn't seem to work, even when the keys are in the default directory.I had to run:
./run.sh /BitBetter/.keys/cert.pfx interactive
in order for it to complete. It appears to have worked as expected when including the absolute path to the .pfx.
That is because the run.sh script, checks for 2 arguments or more.
Should probably be:
if [ "${1,,}" != "interactive" ] && [ "$#" -lt "2" ]; then
Actually, scratch that. To make it work properly, defaulting to the usual cert path, and using just one argument for "interactive" requires a bit more reworking than what I suggested, unfortunately.
@h44z Further more, attempting to build BitBetter on a clean updated copy of Debian Bullseye results in the following:
Building with 5.0 fails (Click to expand) A modified version of what @pedake suggested results in the expected successful build:
grep -RiIl "5\.0" | xargs sed -i 's/5.0/6.0/g'
Building with 6.0 succeeds (Click to expand)
I just wanted to confirm this identical result and solution.
Can confirm @Ayitaka's solution solved the issue for me
BitBetter now uses dotnet 6.0.
dotnet 5.0 outdated
Fix
Was able to mitgate by
needed to run openssl manually.