We would like for you to give them a try and report any encountered regressions on our issue tracker: https://github.com/nim-lang/Nim/issues
- Downloading Official package list
- Tip: 4 messages have been suppressed, use --verbose to show them.
- Error: Refresh failed
- ... Could not download: No SSL/TLS CA certificates found.
- Prompt: No local packages.json found, download it from internet? -> [forced yes]
- Downloading Official package list
- Tip: 5 messages have been suppressed, use --verbose to show them.
- Error: Refresh failed
- ... Could not download: No SSL/TLS CA certificates found.
##[error]Bash exited with code '1'.
So this is why I can't use nimble in Azure Pipelines Windows anymore?
Yes. I wonder why though... if Nimble can find the OpenSSL DLLs it can also find the certificates, this is how we designed it. How do build/install Nim on the CI?
If the Windows CI does not use dlls.zip nor windeps.zip, the script should contain a line like
bitsadmin.exe /rawreturn /transfer "JobName" /priority FOREGROUND https://curl.se/ca/cacert.pem ##vso[task.prependpath]$pwd\NimBinaries\nim-$(CHANNEL)\bin\cacert.pem
The line was:
bitsadmin.exe /rawreturn /transfer "cURL-certicates" /priority FOREGROUND https://curl.se/ca/cacert.pem $pwd\NimBinaries\nim-$(CHANNEL)\bin\cacert.pem
without the ##vso[task.prependpath]
https://github.com/mratsim/constantine/pull/157/commits/b833a17407e12fe063195030d5d544fd50df218f
I pin Nim stable instead of devel in the same PR so confirmation will be when 1.4.4 is deployed.
how about releasing RC candidates with odd numbers, eg: 1.4.2 is a stable release 1.4.3 is a RC candidate for 1.4.4
(if needed, you could even have`1.4.3.1`, 1.4.3.3 but that's not actually needed for this proposal)
When can we expect a non RC release?
Start of the next week.
We have new RCs, which if no regressions are reported will become the official releases:
We would appreciate your (plural) feedback! (Yes, even "everything works fine" :))