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

Perl syntax for strings
by Fridolin SOMERS 16 Jun '21

16 Jun '21

Hi, I see in Perl code some cases where a string in written with a space between q or qq or qw and string. Like : qq /foo bar/ instead of qq/foo bar/ It works, but I dont find it in docs like https://perldoc.perl.org/perlop#Quote-Like-Operators Most of cases are in : use CGI qw ( -utf8 ); There are only 29 other cases : git grep -E ' q[qw]? [/({]' | grep -v 'use CGI qw ' Should we add a coding guideline ? https://wiki.koha-community.org/wiki/Coding_Guidelines I must admint for me it would be better to avoid it because it breaks syntax coloring in my editor (Eclipse with EPIC). But maybe other have the same issue. Best regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

2 2

some thoughts on #28519 regarding lib
by Thomas Klausner 16 Jun '21

16 Jun '21

Hi! without knowing a lot of Koha-internals (still..), I'd strongly prefer to have all the code in a lib dir (as is standard in Perl apps / modules for ages). There are also a lot of tools available to make using code stored `lib` (but not "installed" in the system, i.e. only available in the checkout) easy. The simplest is of course 'lib': https://perldoc.perl.org/lib Or more complex like https://metacpan.org/pod/lib::projectroot (which I wrote some time ago to handle a Monorepo setup; it also includes a comparison of different modules in the SEE ALSO section) OTOH, CGI::Session::Serialize is a cpan module, so technically it should not be checked out into the app code `lib`, but installed as a dependency. There are even more ways to handle installing of dependencies and the finding them, but the currently most comfortable one is https://metacpan.org/pod/Carton. Or (if running everything via Carton is too much of a change), a combination of https://metacpan.org/pod/local::lib and a modern CPAN client (https://metacpan.org/pod/App::cpanminus or https://metacpan.org/pod/App::cpm. I did not want to spam the actuall ticket with this, as I'm not sure if any of this is in fact relevant to the bug, and/or matches the current plans for Koha. Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

3 3

Sharing installation method with Hea
by dcook＠prosentient.com.au 15 Jun '21

15 Jun '21

Hi all, I was looking at https://hea.koha-community.org/systempreferences to view the different versions of Koha out there, and it got me thinking how it would be nice to know how people install Koha. I imagine that we all think that the majority of people use the Debian packages, but it would be good to know. What do people think? David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 2

Notes about Docker Swarm / Portainer and Koha
by Tomas Cohen Arazi 15 Jun '21

15 Jun '21

Hi all, for the 21.05 release, I proposed to launch the API docs site [1]. I did it on Theke's infrastructure for simplicity, but then started thinking how management could be handed to the community. This site is provided by a docker image [2] that is built on each change on the Koha community repository. This is triggered by webhooks. With the idea that this image should be deployed in production automatically, I deployed a Portainer service. Portainer would let us configure and deploy (dockerized) services in a fairly easy way, has an API, and also provides webhooks for triggering things like redeploying/updating (what I needed for api.koha-community.org) Right now this is running under Theke's umbrella, but my idea is to hand this to the community, especially those running the services we use. The short term plan would be to: 1. Have the following domains point to the server we are providing: - traefik.koha-community.org - portainer.koha-community.org - api.koha-community.org 2. Migrate Jenkins into this server/setup 3. Anyone running server for community purposes, can make them join this 'swarm' so we can use them. 4. There will be some community members with admin access to this, so we can all do maintenance tasks like restarting a service, etc. 5. Help is needed regarding backups and how we want to deal with that. We volunteer to help anyone running community sites migrate to this schema. [1] https://api.koha-community.org [2] https://gitlab.com/koha-community/koha-api-docs/-/pipelines/316321820 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Columns settings fails
by Stefano Bargioni 13 Jun '21

13 Jun '21

Hi, imho, Columns settings in circ/circulation.pl (while checking out) doesn't save columns chosen by the librarian. This behaviour is expected by my staff. Any opinion? Thx. Stefano

3 2

Call for news - Newsletter June 2021
by Koha Newsletter 13 Jun '21

13 Jun '21

Hi I'm collecting news for the June 2021 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length, they should be in plain text. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. For events: * Please include dates for past events. If I can't find dates I may not add it. * Announcements for future events with dates to be announced are fine, e. g. Kohacon. * For past events, one month back is the cut-off. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

First big moves for 21.06 - early pushes
by Jonathan Druart 11 Jun '21

11 Jun '21

Hi devs, I'd like to see us focus on those bugs, good candidates for early push: Bug 17600 - Standardize the EXPORT Bug 27526 - Remove Mod/AddItemFromMarc from additem.pl (first step, more work needed in this area) Bug 17427 - Replace CGI::Session with Data::Session Bug 25078 - Update DB process - wrap each DBRev inside a transaction and better error handling (need it soon to prevent unnecessary work later when lot of DBrevs will exist in 21.06) I am going to provide an updated version for the last one, the others are ready for testing. Hoping to see some help there :) Cheers, Jonathan

1 0

The Perl and Raku Conference (In the Cloud)
by Thomas Klausner 10 Jun '21

10 Jun '21

Hi! Today starts this years Perl and Raku Conference (still in the cloud, thanks to Corona): https://perlconference.us/tprc-2021-cloud/ As Koha is written in Perl, this event might interest a few of you. You can watch the live stream for free via YouTube, if you want to participate via Zoom and Slack you need to pay a 10$ fee. Here you can find the schedule (where you can also select your timezone): https://tprc2021cic.sched.com/ I'm doing a short talk on Koha on Thursday, but it's not going to be very technical. As a long time Perl dev I have only recently learned about Koha and it's big community, and want to introduce this project to the Perl community. Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

2 1

Re: [Koha-devel] Increasing Debian Package Compatibility Levels
by dcook＠prosentient.com.au 07 Jun '21

07 Jun '21

Note that those warnings are from Debian Stretch. Since it's oldstable, it's probably still OK to be building on it. What OS do the Koha CI servers use? David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: dcook(a)prosentient.com.au <dcook(a)prosentient.com.au> Sent: Monday, 7 June 2021 4:23 PM To: 'koha-devel(a)lists.koha-community.org' <koha-devel(a)lists.koha-community.org> Cc: 'Mason James' <mtj(a)kohaaloha.com> Subject: Increasing Debian Package Compatibility Levels Hi all, I've been noticing lately some of the following warnings when I'm building Koha Debian packages: dh_install: Compatibility levels before 9 are deprecated (level 7 in use) dh_installdocs dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use) dh_installchangelogs dh_installchangelogs: Compatibility levels before 9 are deprecated (level 7 in use) dh_compress dh_fixperms dh_installdeb dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use) dh_gencontrol It seems to me that we should look at upping our compatibility level. We can see the changes between v7, 8, and 9 at https://manpages.debian.org/testing/debhelper/debhelper.7.en.html. At a glance, I think that we'd probably be OK moving up to 9 from 7. But we'd want to do some testing. David Cook 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

Increasing Debian Package Compatibility Levels
by dcook＠prosentient.com.au 07 Jun '21

07 Jun '21

Hi all, I've been noticing lately some of the following warnings when I'm building Koha Debian packages: dh_install: Compatibility levels before 9 are deprecated (level 7 in use) dh_installdocs dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use) dh_installchangelogs dh_installchangelogs: Compatibility levels before 9 are deprecated (level 7 in use) dh_compress dh_fixperms dh_installdeb dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use) dh_gencontrol It seems to me that we should look at upping our compatibility level. We can see the changes between v7, 8, and 9 at https://manpages.debian.org/testing/debhelper/debhelper.7.en.html. At a glance, I think that we'd probably be OK moving up to 9 from 7. But we'd want to do some testing. David Cook 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