SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Go with the browser: https://docs.digikam.org/en/index.html 2. OR 3. From digiKam: Help > Online Dokumentation OBSERVED RESULT From Web browser: Your connection is not encrypted; NET::ERR_CERT_DATE_INVALID From digikam: page not found EXPECTED RESULT Documentation should open. SOFTWARE/OS VERSIONS Windows: Gnome macOS: Linux/KDE Plasma: Fedora 38 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Latest Google Chrome browser.
The KDE admin team must be contacted to update the ssl certificates for the digikam.org and docs.digikam.org web sites
Hi Ben, Both digikam.org and docs.digikam.org web site needs the certificates to be updated... Best Gilles
This is supposed to automatically renew, however the decommissioning of a subdomain of digikam.org broke this. Has now been corrected and the certificate renewed.
Thanks Ben for the fix. Gilles
Hi Ben, The digiKam.org git repository contents have been completly detroyed (sound like all the dir hierarchy is now as a flat files-system. Why ? Since few days, the build script done everyday report an error when web site is generated: https://invent.kde.org/documentation/digikam-doc/-/jobs/1654544 In fact the Python config file is also dropped. Did you have a backup to restore all the previous giant work ? Best Gilles
The last job working successfully before the mess is this one (one week ago): https://invent.kde.org/documentation/digikam-doc/-/jobs/1623373 Gilles
Sound like the 2 commits below have destroyed the repository contents: https://invent.kde.org/documentation/digikam-doc/-/commit/2ced46b8d705ea3a083c4d61e47cd6bc64777a40 https://invent.kde.org/documentation/digikam-doc/-/commit/4d1e5d79e5d4e95708437970d9bfa3af24fe4274 Gilles
This is an issue that has also struck Kdenlive and Krita. I've now rewound the repository and have applied a safety measure that should hopefully prevent it from recurring.
Thanks Ben