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

CI and packaging
by Tomas Cohen Arazi 15 Feb '23

15 Feb '23

Hi all, we've been talking for a while by different means (IRC, pm, hackfests, etc) about the need to build a solid pipeline for our testing infrastructure, package building and testing and also the docker images. Several individuals have implemented different things over time, for building the packages. Today we had a nice Zoom session with Kyle, and this is the result of picking the best ideas from each thing we found: https://gitlab.com/koha-community/koha-dpkg-docker We are still working on the README, but basically, with: - Docker - A Koha clone - An environment variable passed we can build the Debian packages. I think this is a great achievement and kudos to Kyle for his contribution. Thanks Kyle! Now to integrate it! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

KTD and (Linux) Docker Desktop issues
by Tomas Cohen Arazi 15 Feb '23

15 Feb '23

Hi all, community members have reported permissions issues breaking ktd initialization when launching it fresh. It's been narrowed down to be an issue with the Docker Desktop for Linux product. Please use the Docker Engine/server install instructions as pointed by the readme.

1 0

koha-testing-docker is now installing pre-commit git hooks
by Jonathan Druart 14 Feb '23

14 Feb '23

Hi, We have a pre-commit hook in the wiki but people forget to install it. And it was not easy to update and propagate the changes. We decided to embed it in koha-testing-docker and install it automatically. So if you see a message telling you your commit is missing something, don't ignore it ;) Note that you can force the commit with --no-verify. It's working inside and outside a ktd shell. Cheers, Jonathan original issue in misc4dev which was then moved to ktd: https://gitlab.com/koha-community/koha-misc4dev/-/issues/59 https://gitlab.com/koha-community/koha-testing-docker/-/issues/347

3 2

Call for news - Newsletter February 2023
by Koha Newsletter 13 Feb '23

13 Feb '23

Hi I'm collecting news for the February 2023 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

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

How to make self-referential URLs in Koha
by dcook＠prosentient.com.au 30 Jan '23

30 Jan '23

Hi all, With some recent code, I've been using creating self-referential URL in Koha using CGI->url(), and passing it as a value. With CGI, the URL is correct (ie starting with /cgi-bin/koha). With Plack, it's not, because the OPAC is mounted as "/opac". I worked around this by rewriting the self-referential URL in my code, but I was wondering if anyone else had any thoughts on this. I've noticed there are a few places in Koha where we use CGI->url() and I'm guessing we may have unexpected bugs in Plack-enabled Koha as a result. Of course, one workaround would be to have /opac and /intranet aliases or URL rewriting in Apache, so that the self-referential URLs created by Plack still end up resolving. I wonder if that's the easiest path forward. In the past, I have wondered if we could get rid of "/cgi-bin/koha" as a path prefix all together (especially as cgi-bin scares security tools), but it's so deeply embedded in Koha at this point that it seems a huge task to replace it. Anyway, just throwing that out there. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

6 8

Koha Community Newsletter: January 2023
by Koha Newsletter 28 Jan '23

28 Jan '23

The Koha Community Newsletter for January 2023 is here: https://koha-community.org/koha-community-newsletter-january-2023/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Still time to register for the Hackfest in Marseille !!!
by Paul Poulain 27 Jan '23

27 Jan '23

Hi guys, There are already more than 40 ppl registered for the hackfest (7 from Germany, 1 from USA, 1 from UK, the rest from France). Please come and join us for a week of work on Koh! There will be coffee, beer (after work ;) ), fun time translating, testing, documenting, developing. And, of course the legendary cheese lunch (on tuesday) Just drop me an email to say you want to come ! [and if you sent me an email and had no feedback, my bad, drop me an email again please] -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0