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

Re: [Koha-devel] Thoughts on retiring libapache2-mpm-itk?
by dcook＠prosentient.com.au 26 Jul '22

26 Jul '22

What would be insecure about making the Starman/Plack sockets writeable by www-data? It wouldn’t be any different from using TCP sockets (instead of Unix sockets) which is common or a reverse proxy. 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 From: Tomas Cohen Arazi <tomascohen(a)theke.io> Sent: Tuesday, 26 July 2022 1:10 PM To: Chris Cormack <chris(a)bigballofwax.co.nz> Cc: David Cook <dcook(a)prosentient.com.au>; Koha Devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Thoughts on retiring libapache2-mpm-itk? > Yet… Koha mostly runs in Starman these days. We don’t necessarily get that much benefit from AssignUserID anymore. The main problem would be permissions for the CGI scripts that we don’t proxy. So maybe we wait until after we’re proxying everything through Apache and Apache is just a reverse proxy to Starman and a static asset server. Because at that point… there’s no reason it couldn’t just run under the “www-data” user. > > That's not entirely true, plack runs on a unix socket as a user, with potentially multiple sites on a single server. So having only the right apache sites being able to talk to the right sockets by them both being the same user is a very important thing. +1 Being able to have a secure deployment out of the box is a thing we shouldn't loose!

1 0

Long-term support version of Koha (bug 31008)
by David Nind 21 Jul '22

21 Jul '22

At the Development IRC meeting on 8 June 2022 the issue of having a long-term support version of Koha (Koha LTS) was discussed. (It has been discussed and proposed in the past.) Summary ======= General agreement was reached that: 1. A long-term support (LTS) version of Koha would be for 2.5 to 3 years 2. We would start with oldstable (which is now 21.11) 3. There would be an LTS maintainer role for each cycle (there is no expectation that this is the same person for up to three years - it is preferable that it is someone different each cycle) 4. The mandate for the LTS version would cover: . security fixes . things that are broken (such as APIs (external), dependencies (such as Elasticsearch), etc), and . essential back ports only, once past oldoldstable 5. It would be an irregular release - only when something is needed once past oldoldstable 6. We would inform the Koha Community about the LTS version of Koha, what it is, and what it means for support (including updates to the website, mailing list, manual section on supported versions, etc) Next steps ======== Your feedback is welcome on the proposed LTS version of Koha. Feel free to provide this however you wish, including replying to this email, IRC, and on bug 31008. It will then be discussed again, and the approach confirmed at the next available Development IRC Meeting (ideally this would have been the 22 June 2022 meeting, but I've just sent this email!). References ========= [1] Bug 31008: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31008 [2] 8 June 2022 Development IRC meeting: . Minutes: https://meetings.koha-community.org/2022/development_irc_meeting_8_june_202… . Log: https://meetings.koha-community.org/2022/development_irc_meeting_8_june_202… David Nind | david(a)davidnind.com New Zealand m. +64 21 0537 847

3 2

Updating SCSS lint process to use stylelint
by Owen Leonard 21 Jul '22

21 Jul '22

Hi all, Back when we switched from LESS to SCSS in the OPAC (Bug 20427) I added a linting configuration, .scss-lint.yml. I've always configured my editor to automatically lint SCSS using this configuration. I don't know if anyone else does this too. In VS Code I was using scss-lint for this, but it's now deprecated. They suggest stylelint instead: https://stylelint.io. I'd like to propose replacing .scss-lint.yml with .stylelintrc.json, transferring most of the same rules. It could be left up to the individual to install the dependencies, or I could update package.json. One nice thing about stylelint is that it has a "--fix" feature for some simple rules. This could be build into our gulp tasks. Has anyone else been linting SCSS? If so, does anyone have opinions about how our current rule set is working? -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

6 6

KohaCon23 proposals - review proposal page and draft message
by David Nind 16 Jul '22

16 Jul '22

My action points from the last development meeting were to: - create a Wiki page for KohaCon23 proposals, and - draft an email for the general mailing list. KohaCon23 proposals wiki page ========================= I've created a wiki page: https://wiki.koha-community.org/wiki/KohaCon23_Proposals Draft message for the general mailing list =============================== Subject: Proposals now open for KohaCon23 Summary ------------- The request for proposals to host KohaCon 2023 is now open! If you or your organization would like to organize KohaCon23, please enter all the required information on the KohaCon 2023 proposals wiki page:[1] https://wiki.koha-community.org/wiki/KohaCon23_Proposals The closing date for bids is *6 September 2022 23:59 UTC*. Proposals received will be discussed at the 7 September 2022 General IRC Meeting ( https://wiki.koha-community.org/wiki/General_IRC_meeting_7_September_2022) Information about hosting KohaCon ----------------------------------------------- The community has agreed that KohaCon conferences must be either: - hybrid with an in-person conference streamed online, or - entirely online. This allows for greater accessibility, so that everyone can attend and learn from each other no matter their availability, ability to travel, or budget. For more information about the generally agreed rules established for KohaCons, see https://wiki.koha-community.org/wiki/Processes_for_KohaCons This covers the timetable, continent rotation, and information to help with planning a successful KohaCon. Deadline for proposals ------------------------------ The closing date for proposals is *6 September 2023 at 23:59 UTC*. If there is more than one proposal, we will organize a vote - this will be announced on the mailing list. Help with your proposal ------------------------------- The community stands behind anyone who volunteers to organize a KohaCon, and help is always available if you're unsure how to proceed. Reply to this email if you need help, or ask on IRC. There is a wealth of experience in the community from those who have attended and organized previous KohaCons (and other conferences). [1] If you do not have an account to edit the wiki, you can request one. It is usually pretty fast to get access. Feedback ======== Please provide any feedback (or edit the Wiki pages) by the end of Monday 18th July 2022 23:59 UTC. I will send the message to the general mailing list on Tuesday 19 July 2022, unless more time is required. Thanks! David Nind | david(a)davidnind.com 387 Whartons Road, RD 10D, Oamaru 9492, New Zealand m. +64 21 0537 847

2 1

Checkouts API Question
by Stephen Graham 13 Jul '22

13 Jul '22

Hi All - we are on 21.11, and would like to include patron account data in our bespoke University mobile app. I was planning on using the RESTful API to get the data. What we would like is simply a list of titles (plus author and ISBN) along with the due back dates. I'm struggling , when looking at https://api.koha-community.org/21.11.html, to see how this could be done without using lots of API calls. Would I have to do something like the following: * Call /checkouts to get a list of checkouts from the patron * Iterate over the checkout_id and call /checkouts/$id for each checkout * I cannot see any Biblio references in the returned data, so I'd have to then grab the biblio_id from the /items/$id endpoint and then call the /biblios endpoint to get the actual bibliographic data. If the patron had 10 items out this would be at least 30 calls to get the bib data. Is that what I would have to do, or am I missing something - like a header or extra query which would return all the info I require from the first endpoint call? Any advice/pointers would be much appreciated!! Cheers, Stephen -------------------------------------- Stephen Graham Library Technology Consultant Library and Computing Services University of Hertfordshire Hatfield, Hertfordshire, AL10 9AB Email: s.graham4(a)herts.ac.uk<mailto:s.graham4@herts.ac.uk> Website: herts.ac.uk

3 3

Call for news - Newsletter July 2022
by Michael Kuhn 13 Jul '22

13 Jul '22

Hi I'm collecting news for the July 2022 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 -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

1 0

Re: [Koha-devel] Help needed
by Tomas Cohen Arazi 12 Jul '22

12 Jul '22

Thanks, Jonathan. Your pointer was very helpful. El lun, 11 jul 2022 6:27, Jonathan Druart <jonathan.druart(a)gmail.com> escribió: > I think the problem is that Koha::Checkouts::Renewals has 2 > ("virtual") FKs on the same column. > > t::lib::TestBuilder::_create_links is generating an object (/values) > for "checkout" and $col_values->{checkout _id} has the ID from the > checkout we generated. > THEN we are processing the next relationship, old_checkout, and > generate another checkout, but this time we pass the checkout_id > previously generated. As we cannot pass an AI value, TestBuilder > explodes with "Value not allowed for auto_incr issue_id in Issue". > I guess the fix would be to use the constraint's name instead of the > column's name. > > Le sam. 9 juil. 2022 à 02:18, Tomas Cohen Arazi <tomascohen(a)gmail.com> a > écrit : > > > > Hi all, I've been trying to track down a problem with TestBuilder tests. > The are failing (almost) randomly but I narrow it down to: > > > > - Koha::Checkouts::Renewals > > - Koha::Biblio::ItemGroup::Items > > > > I ran out of fuel today, but it would be great if some more eyes were > put on this, so I can move on with pushing new stuffs with a happy test > suite. This is the subset of TestBuilder.t that I'm looking at (put it in > t/db_dependent/test.t): > > > > https://paste.koha-community.org/10864 > > > > My feeling is TestBuilder->_should_be_fk is not working as it should > (for Koha::Checkouts::Renewals) and about Koha::Biblio::ItemGroup::Items, > all I can say is that the table is a linking table, pretty much like the > club holds one. > > > > Thanks in advance and have a great weekend! > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (http://theke.io) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : https://www.koha-community.org/ > > git : https://git.koha-community.org/ > > bugs : https://bugs.koha-community.org/ >

1 1

QAing OpenID Connect SSO implementation
by dcook＠prosentient.com.au 11 Jul '22

11 Jul '22

Hi all, Is there a QA person with some time to QA the OpenID Connect SSO implementation at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30988? I'm happy to provide additional advice on how to test it using the Keycloak IdP docker image, if the steps I provide at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30988#c26 aren't enough. I'm not the patch author; Shi Yao Yang at inLibro wrote it, but I'm keen to get it into core Koha. With Shibboleth/SAML and OpenID Connect, we'd have the 2 major SSO authentication protocols supported in Koha. I've been maintaining a OpenID Connect implementation in Koha locally since 2014, so I'd love to be able to use the core code instead of my custom code. 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

Can we set arbitrary due date via SIP2 end-point
by Indranil Das Gupta 11 Jul '22

11 Jul '22

Hi all, The case: Koha 21.05.x on Debian 10.12 (standard package installation). Circ rules are defined, 15 days per checkout. SIP2 is also working. The RFID vendor wants to provide options of "1 day" / "15 days" / "365 days" to any itemtype from the SC RFID kiosk (based on the fact that from Koha's checkout page we can set arbitrary due dates overriding the calendar and issuelength rules. This is what I have tried so far from the server CLI telnetting to port 8023: INPUT - 11NY20220710 02583620230710 000000AOMAIN|AA1|AB22918|AC|CH| RESPONSE - 121NNY20220710 124122AOMAIN|AA1|AB22918|AJECOLOGICAL METHODS|AH20220725 235900| As can be seen from AH in response it is being set at 15 days (instead of 365 days as supplied with "nb due date" in the CHECKOUT msg) Looking at the SIP2 code i see $overriden_duedate is going in as undef Am I missing something OR is it how it is atm? thanks in advance Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

Help needed
by Tomas Cohen Arazi 11 Jul '22

11 Jul '22

Hi all, I've been trying to track down a problem with TestBuilder tests. The are failing (almost) randomly but I narrow it down to: - Koha::Checkouts::Renewals - Koha::Biblio::ItemGroup::Items I ran out of fuel today, but it would be great if some more eyes were put on this, so I can move on with pushing new stuffs with a happy test suite. This is the subset of TestBuilder.t that I'm looking at (put it in t/db_dependent/test.t): https://paste.koha-community.org/10864 My feeling is TestBuilder->_should_be_fk is not working as it should (for Koha::Checkouts::Renewals) and about Koha::Biblio::ItemGroup::Items, all I can say is that the table is a linking table, pretty much like the club holds one. Thanks in advance and have a great weekend! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1