The latest trunk check-in is now considered a release candidate. If no objections are raised over the next couple of days, I will push out the official 2.23 release of Fossil based on the latest trunk.

Please run any tests you may have and send follow-up posts to this forum thread if you have objections.

Complete set of changes going back to the previous release: https://fossil-scm.org/home/timeline?p=trunk&bt=release

Latest change log: https://fossil-scm.org/home/doc/trunk/www/changes.wiki

Hmm, is it expected that I have to add the package libssl-dev?

I was able to build fossil with SSL support as of version [b5aa9f8ab4] 2023-08-18 14:15:20 UTC without this new package.

The error was:

cc -I. -I./src -I./extsrc -Ibld -Wall -Wdeclaration-after-statement -DFOSSIL_ENABLE_JSON -DFOSSIL_ENABLE_TH1_HOOKS -DFOSSIL_DYNAMIC_BUILD=1  -g -O2 -DHAVE_AUTOCONFIG_H  -o bld/http_transport.o -c bld/http_transport_.c
./src/http_ssl.c:36:10: fatal error: openssl/bio.h: No such file or directory
 #include <openssl/bio.h>
          ^~~~~~~~~~~~~~~
compilation terminated.
src/main.mk:1377: recipe for target 'bld/http_ssl.o' failed

os:

Distributor ID: Ubuntu
Description:    Ubuntu 18.04.6 LTS
Release:        18.04
Codename:       bionic

OpenSSL 1.1.1  11 Sep 2018

Rebuilding after adding libssl-dev worked fine.

Hmm, is it expected that I have to add the package libssl-dev?

It's always required that for SSL/TLS support. If configured with --with-openssl=none then it will build without SSL support, otherwise is requires the libssl-dev package (or equivalent - the libssl header files).

The only changes to the http_ssl.c source file since the last release are:

https://fossil-scm.org/home/fdiff?v1=6327207da26138b0&v2=d8f90458ff2bc23c

So I don't know how you were able to build before without libssl-dev.

The release binaries statically link against OpenSSL, which requires downloading and compiling OpenSSL first. There is a checklist on how to build the release binaries at https://fossil-scm.org/home/wiki?name=Release+Build+How-To. Maybe you can build that way without requiring libssl-dev?

Hmm interesting.

Stephan, I have openssl=auto on my configure line.

Richard, I'm not sure how I was able to build either. Might have to do some spelunking in my apt logs to see if libssl-dev got removed recently. I also haven't done a full, clean rebuild in a while, so it might not have been removed that recently.

I'm not morally opposed to installing libssl-dev on my system. I just thought it was weird that I needed to add it and didn't remember having done so before.

Thanks for your feedback. This is resolved AFAIAC.

But the latest OpenSSL is version 3.1.2 (Just checked - looks like they have just recently added 3.1.3 - I'll upgrade before doing the release build). Maybe you should follow the checklist provided and build with the latest OpenSSL?

Release Delayed

A bug inserted by the enhanced defense against CSRF caused self-registration to stop working. The bug is fixed in check-in 6ae9941860bfade6.

I nearly did a release that contained this rather serious bug. That close call inspires me to delay the release a while longer, hoping to catch any other problems. Expression your agreement or disagreement with that choice in replies to this post.

Multiple new merges to trunk from user Preben. So the release is definitely delayed now - probably by a few weeks.

My sincere apologies for that.

Certainly not what I intended.

That pretty much matches (in quantity) what I get on Ubuntu 18.04:

***** Final results: 68 errors out of 38306 tests
***** Considered failures: amend-tag-2.2 test-framework-diff json-login-c-m json-login-c-n json-login-c-c merge1-2.1 merge1-2.2 merge1-4.1 merge1-4.2 merge1-7.1 merge1-7.2 merge3-3 merge3-4 merge3-5 merge3-6 merge3-7 merge3-8 merge3-11 merge3-24 merge3-25 merge3-34 merge3-35 merge3-44 merge3-45 merge3-54 merge3-55 merge3-64 merge3-65 merge3-74 merge3-75 merge3-84 merge3-85 merge3-94 merge3-95 merge3-103 merge3-104 merge4-1000 merge4-1002 test-framework-merge_renames test-framework-merge_renames_2 merge_warn-1 test-framework-mv-rm test-framework-revert test-framework-settings-repo settings-valid-local-auto-hyperlink-delay settings-valid-local-auto-hyperlink-mouseover settings-valid-local-chat-timeline-user settings-valid-local-dont-commit settings-valid-local-email-listid settings-valid-local-forum-close-policy settings-valid-local-large-file-size settings-valid-local-self-pw-reset settings-valid-global-auto-hyperlink-delay settings-valid-global-auto-hyperlink-mouseover settings-valid-global-chat-timeline-user settings-valid-global-dont-commit settings-valid-global-email-listid settings-valid-global-forum-close-policy settings-valid-global-large-file-size settings-valid-global-self-pw-reset test-framework-stash test-framework-symlinks test-framework-th1-repo th1-trace-2 th1-trace-4 th1-defHeader-2 th1-info-commands-1 test-framework-unversioned
***** Ignored results: 3 ignored errors out of 38306 tests
***** Ignored failures: json-cap-POSTenv-name json-env-RC-1103-code merge5-sqlite3-issue

so what you aren't seeing isn't just a platform issue.