February 2023 - Koha-devel - lists.koha-community.org

Automatically managing generated configuration files like log4perl.conf
by David Cook 10 Feb '23

10 Feb '23

Hey all, Updating configuration files like log4perl.conf can be really painful. Surely, there has to be a better way? Jonathan and I talk a bit about this on "Bug 32791 - Log4perl configuration files need a tool for updating on package upgrade". My first draft uses a bespoke tool, but this morning I learned about the "ucf" utility, which was designed to manage dynamically generated configuration in a similar way to how we manage configuration files packaged in koha-common! If the installed file hasn't been manually updated locally, it will be replaced with the newest generated version. If the installed file has been changed, then the user will be prompted with some options about installing the package version, retaining the local version, viewing a diff of the two files, or even doing a 3 way merge. I think 99.9% of cases will show a lot of these files never get locally changed, so it would just automagically provide updated configuration. And for that 0.1% of cases where the sysadmin has updated the configuration, they'd have a familiar industry standard UI to work with. I'm happy to provide a patch, but I'd like to get some more feedback first. I think it would work very well for log4perl, and it could be useful for other configuration files too. (The only danger I see is when you have a large number of instances with local changes, and you get bogged down with the UI. But there are some ENV variables that can be used to auto-choose which version to install. The utility leaves behind files with extensions like ".ucf-dist" and ".ucf-old" as well so you can always go back and fix up your conf after the fact manually.) Anyway, food for thought! David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Failed to load external entity docbook.xsl when building Koha package
by Aleisha Amohia 03 Feb '23

03 Feb '23

Hello all We're running into an error when trying to build Koha debian packages. It's toward the end of the build-git-snapshot output and starts with this: xsltproc --output /build/koha-22.11.01.000+xxx+20230117170120.52134d4b/debian/tmp/debian/tmp_docbook/ \ /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl \ debian/docs/*.xml warning: failed to load external entity "/usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl" cannot parse /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl debian/rules:17: recipe for target 'override_dh_auto_install' failed make[1]: *** [override_dh_auto_install] Error 4 We're using gitlab runners for these builds, which haven't changed since they were previously working last month. Has anyone seen this before and know what's causing it or what the fix is? Thanks! -- Aleisha Amohia (she/her) Koha Developer Catalyst IT - Expert Open Source Solutions www.catalyst.net.nz CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

4 6

Trouble for the Gitea project: forked to Forgejo
by Victor Grousset/tuxayo 01 Feb '23

01 Feb '23

Hi :) Thanks David Nind for sharing this info on the last dev meeting: > Use of Gitea: We use Gitea for git.koha-community.org. Gitea was "forked" and is now Forgejo[1] - see the links update and related links[2] (sounds eerily familiar 8-(.. ). The community needs to look at what to do next, such as whether to continue to use Gitea, update to Forgejo, do something else.... (David Nind) > [1] https://forgejo.org/ > [2] https://forgejo.org/2022-12-26-monthly-update Comments during the meeting: > forgejo is the 'good' one? > that's what it looks like ^^ > "After Gitea Ltd confirmed the takeover of the Gitea project on 30 October 2022, a group of people proposed that Codeberg e.V. should become the custodian of a fork of Gitea. The proposal was accepted 16 November 2022" - e.V. is a German thing actually More details: e. V. is the legal form for associations in Germany and Codeberg e. V. is known for their Gitea (well, now Forgejo) instance that became host to a decent number of libre projects in the last two years. (likely they moved away from GitHub and not wanted the not libre GitLab instance at GitLab.com (open-core)) Trivia: > Forgejo (pronounced /forˈd͡ʒe.jo/) is inspired by forĝejo, the Esperanto word for forge. 😃😃😃 I knew the name spelling looked familiar! Cheers, -- Victor Grousset/tuxayo

6 8