Well, I am just grumpy as there have been a lot of issues post the 7.0 release, that were not issues in actual calibre code. I have had to investigate bugs/incompatibilities in all sorts of software from Qt to OpenSSL to Wayland and I am rather tired of finding and fixing things in other peoples' systems, it takes a disproportionate amount of effort. And Linux is particularly egregious for this, because of its diversity, and the constant pointless churn in its basic infrastructure. There is a lot of meaningless variation between Linux distros. In Linux land people just keep re-inventing the same things in slightly different forms and all this pointless churn imposes high costs on anybody trying to build anything based on their systems. It's a real pity Linux userland didnt learn from the Linux kernel the importance of stability in external APIs.
For this latest case as best as I can determine, *only* Fedora/RedHat and its derivatives suffer from making it impossible to use unmodified upstream openssl libraries on their distros. All other distros do not have this problem. But because of Fedora/RedHat it is impossible for me to allow openssl to read the system configuration, which means it is impossible for calibre users to configure their openssl system wide and have calibre pick up that configuration. As it is there is a kludge in calibre code (put in way back in the calibre 2.x era again for Fedora) where at startup I set an openssl env var so that at least it uses the system root certificates. I hate having to impose that kind of limitation for no good reason.
Hopefully things will stabilise now. I am planning to take a break from dealing with these problems in other peoples systems type issues to just write code, which usually cheers me up
