From kohadevel at agogme.com Wed Nov 1 13:54:19 2023 From: kohadevel at agogme.com (Thomas Dukleth) Date: Wed, 1 Nov 2023 12:54:19 -0000 Subject: [Koha-devel] DMARC testing for koha-devel In-Reply-To: References: Message-ID: <793826e58b49015f9ebcd7f9e5ba714b.squirrel@wmail.agogme.com> 1. DMARC Support on the Koha-Devel List. On Wed. 18 Oct. Jonathan Druart changed the Mailman 2 configuration of the koha-devel mailing list to support DMARC compatibility as an initial test in production for supporting DMARC on Koha mailing lists generally following periodic discussions of supporting DMARC compatibility on the Koha mailing lists in Development IRC meetings. This change addresses bug 34927, "Adding DMARC compatibility to mailing lists", https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34927 . The test of configuration changes should at least not loose any messages while making changes to support DMARC. See further below for testing information including the evident need for mailing list DKIM re-signing. 2. How the Change Should Function. DMARC support on Mailman sends messages from the authenticated mailing list address without impersonating the original author in the From header when resending messages to mailing list recipients. Using the munge From header method, better supported by email clients, Mailman copies the original message From header with the original author's email address to the Reply-To header and substitutes the list email address for the message author's email address in the From header. The issue is about how mailing list messages are sent with the mailing list address authenticated to avoid having the mailing list server impersonate the author of the mailing list email message. No one is suggesting blocking mailing list subscribers who do not use DMARC which could be a substantial minority and is unrelated to the problem of mailing list impersonation of the message author. 3. Testing. 3.1. Check Your Email Client Use for Unexpected Changes. You should not notice any changes in how you interact with the mailing list unless you have some filtering rules or scripts using the exact form of the original author's From header which is now in the Reply-To header. For email clients with good mailing list support, you should have a function to "send to list" and "reply to list" as you may have had previously. The "reply" function of your email client should reply offlist to the original message author as it did previously. The "reply to all" function of your email client should reply offlist to the original message author as well as on list to the mailing list address in the CC header and offlist to any others in the CC header as it did previously. If your email client had different behaviour previously, the previous different behaviour should be unchanged. Most importantly, if you were receiving mailing list messages previously you should continue to receive them unless your email system suddenly adopted some strict DMARC requirement. 3.2. Check an Email Client in DMARC Only System. If you have an environment which rejects non-DMARC compliant messages, see whether subscribing to the koha-devel list from an email address in such a strict DMARC environment allows messages to be received. In some recent years, some major proprietary webmail systems have been known to reject non-DMARC compliant messages for an extended period of time. DMARC support as configured in Mailman 2 should be fine for most recipients but you may have the misfortune of having an extra stringent DMARC only system. DMARC strictness includes rejection or quarantine policies which depend upon SPF attestation and DKIM a signature for the message body and some headers. DKIM is most likely to fail validation 3.2.1. DMARC Strictness Failures. Reasons for a strict system rejecting or quarantining DMARC messages from a mailing list may include the following: 3.2.1.1. DKIM Not Working Properly for Mailing List. For DMARC which is dependent upon SPF and DKIM, the DKIM signature should be re-signed using the mailing list sender, such as koha-devel at lists.koha-community.org . DKIM signatures from the message author should not validate because we change the From header, moving the original From header to Reply-To , adding "[koha-devel]" to the subject header, and add a mailing list footer to the body. It is currently evident as probably expected that the DKIM signatures in the message headers are not being re-signed for lists.koha-community.org . Messages retain the DKIM signature of the original author and would not validate properly even without DMARC changes because every message is altered slightly for the mailing list. Such a DKIM signature problem may have been more of an issue in past years where popular mail systems had adopted excessive strictness in rejecting messages. Mailman 3 has code which might address the issue better when setting remove_dkim_headers to yes but removing the header does not ensure that the SMTP server will supply an appropriate DKIM header for the mailing list. Re-signing the outgoing message to can be fixed by forcing Mailman to send to a special port for which messages are designated as originating from the system and re-signed. The mailing lists are also not DKIM signing the monthly mailing list membership messages despite a DKIM signature reported for lists.koha-community.org . I am communicating with people at BibLibre with the configuration details for fixing DKIM signing and mailing list message re-signing. 3.2.1.2. DKIM Strictness. DKIM strictness is partly a function of DKIM canonicalization. Canonicalization has variants simple for strict and relaxed for relaxed. Simple can fail on white space mismatch. Relaxed should not be expected to validate with even the addition of a footer for the mailing list or the addition of the list designator such as "[koha-devel] in the subject. Canonicalization can be expressed in a divided form such as: simple/relaxed relaxed/simple simple/simple relaxed/relaxed The first part of the divided form is for headers. The second part is for the message body. 3.2.1.3. ARC Support. Another issue for an overly strict system could be not including authenticated receiving chain, ARC support. Mailman 3 includes ARC support which is not included in Mailman 2. 3.2.1.4. False Passes. In my testing of the popular proprietary mail system Gmail, their system is currently passing DMARC with SPF but no DKIM signature. Gmail has also passed valid DKIM but I have not tested invalid DKIM. Testing gives the appearance that DMARC seems to be validated independently of SPF and DKIM and may currently only be matching evaluation. 4. Motivation. There was a request a few months ago to support DMARC for the general mailing list for people who are under strict DMARC only policies at their place of employment, I had carefully researched the least harmful quick method of implementing DMARC support with a configuration change in Mailman 2 which the Koha mailing lists are using and which is still supported. No immediate need for administrators to upgrade to Mailman 3 with whatever time would be needed for that work. [Mailman 3 has enough changes and differences in supported options compared to Mailman 2 that upgrading may be non-trivial for some implementations.] 5. Mailman 2 Configuration Changes. In the Mailman 2 General List Personality section: Change from_is_list from "No" to "Munge From". In the Mailman 2 Sender Filters section: Change dmarc_moderation_action from "Accept" to "Munge From". 6. DNS Changes. 6.1. Biblibre Managed Lists. The BibLibre managed lists already had the DMARC setting in DNS. _dmarc.lists.koha-community.org. IN TXT "v=DMARC1; p=none" 6.2. DNS Change Needed for the Koha General Mailing List run by Katipo. The DNS configuration for lists.katipo.co.nz needs the following line: _dmarc.lists.katipo.co.nz. IN TXT "v=DMARC1; p=none" ... if using BIND as DNS server or the equivalent where the policy is "p=none" matching the Biblibre DNS configuration and allows messages to the mailing list from non-DMARC compliant systems. 6.3. Additional Helpful DNS Configuration Option. Checking DMARC reports for failure may be helpful using the following form for BIND configuration. rua=mailto:dmarc-rua-reports at domain.tld Possible examples for the Biblibre and Katipo mailing list domains. _dmarc.lists.koha-community.org. IN TXT "v=DMARC1; p=none; rua=mailto:dmarc-rua-reports at biblibre.com" _dmarc.lists.katipo.co.nz. IN TXT "v=DMARC1; p=none; rua=mailto:dmarc-rua-reports at katipo.co.nz" Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 From tomascohen at gmail.com Thu Nov 2 14:30:58 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 2 Nov 2023 10:30:58 -0300 Subject: [Koha-devel] Last month before the release Message-ID: Hi all. We are almost done with the release, a couple medium/big things to push today/tomorrow and then bug fixing. I wanted to ask y'all to please view the Jenkins tasks status anytime after your stuff has been pushed. I know I said this many times, but some devs clearly break some tests that are trivially fixable and the team needs you to take care of your breakages. I'm doing my best to track things and fix, but you should all be worried about that. -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri Nov 3 01:14:58 2023 From: dcook at prosentient.com.au (David Cook) Date: Fri, 3 Nov 2023 11:14:58 +1100 Subject: [Koha-devel] Last month before the release In-Reply-To: References: Message-ID: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> What’s the best way to do this? I think Jenkins might send emails, but I think my mail server blocked it ages ago as spam. 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: Koha-devel On Behalf Of Tomas Cohen Arazi via Koha-devel Sent: Friday, 3 November 2023 12:31 AM To: koha-devel Subject: [Koha-devel] Last month before the release Hi all. We are almost done with the release, a couple medium/big things to push today/tomorrow and then bug fixing. I wanted to ask y'all to please view the Jenkins tasks status anytime after your stuff has been pushed. I know I said this many times, but some devs clearly break some tests that are trivially fixable and the team needs you to take care of your breakages. I'm doing my best to track things and fix, but you should all be worried about that. -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Fri Nov 3 01:24:38 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 2 Nov 2023 21:24:38 -0300 Subject: [Koha-devel] Last month before the release In-Reply-To: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> References: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> Message-ID: The suggested sequence is: 1. You notice your stuff for pushed, yay! 2. You look at Jenkins runs for the relevant branches (e.g. Koha_Master_* tasks) 3. If some test gets broken that day, you try too see if it was you. Beware sometimes it is not obvious. Today there was a failure in the holds API tests, because of a bug that didn't touch the API, but made the code stricter (?) so the loose tests we had written had to be tweaked so they didn't trigger a silly error. So the devs did right, didn't introduce a bug, but made the tests fail. But it is all of us, specially those who got patches pushed, who should be looking after those failures. Team work Thanks! El jue, 2 nov 2023 21:15, David Cook escribió: > What’s the best way to do this? > > > > I think Jenkins might send emails, but I think my mail server blocked it > ages ago as spam. > > > > 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:* Koha-devel *On > Behalf Of *Tomas Cohen Arazi via Koha-devel > *Sent:* Friday, 3 November 2023 12:31 AM > *To:* koha-devel > *Subject:* [Koha-devel] Last month before the release > > > > Hi all. > > > > We are almost done with the release, a couple medium/big things to push > today/tomorrow and then bug fixing. > > > > I wanted to ask y'all to please view the Jenkins tasks status anytime > after your stuff has been pushed. I know I said this many times, but some > devs clearly break some tests that are trivially fixable and the team needs > you to take care of your breakages. > > > > I'm doing my best to track things and fix, but you should all be worried > about that. > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri Nov 3 01:41:35 2023 From: dcook at prosentient.com.au (David Cook) Date: Fri, 3 Nov 2023 11:41:35 +1100 Subject: [Koha-devel] Last month before the release In-Reply-To: References: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> Message-ID: <020a01da0dee$8e90c200$abb24600$@prosentient.com.au> It’s not clear to me though how you look at Jenkins runs. Is it going to https://dashboard.koha-community.org/ and then clicking on one of the badges to go to Jenkins like https://jenkins.koha-community.org/job/Koha_Master_U22/ and then clicking on “Latest Test Result”? 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 Sent: Friday, 3 November 2023 11:25 AM To: David Cook Cc: koha-devel Subject: Re: [Koha-devel] Last month before the release The suggested sequence is: 1. You notice your stuff for pushed, yay! 2. You look at Jenkins runs for the relevant branches (e.g. Koha_Master_* tasks) 3. If some test gets broken that day, you try too see if it was you. Beware sometimes it is not obvious. Today there was a failure in the holds API tests, because of a bug that didn't touch the API, but made the code stricter (?) so the loose tests we had written had to be tweaked so they didn't trigger a silly error. So the devs did right, didn't introduce a bug, but made the tests fail. But it is all of us, specially those who got patches pushed, who should be looking after those failures. Team work Thanks! El jue, 2 nov 2023 21:15, David Cook > escribió: What’s the best way to do this? I think Jenkins might send emails, but I think my mail server blocked it ages ago as spam. 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: Koha-devel > On Behalf Of Tomas Cohen Arazi via Koha-devel Sent: Friday, 3 November 2023 12:31 AM To: koha-devel > Subject: [Koha-devel] Last month before the release Hi all. We are almost done with the release, a couple medium/big things to push today/tomorrow and then bug fixing. I wanted to ask y'all to please view the Jenkins tasks status anytime after your stuff has been pushed. I know I said this many times, but some devs clearly break some tests that are trivially fixable and the team needs you to take care of your breakages. I'm doing my best to track things and fix, but you should all be worried about that. -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From mtj at kohaaloha.com Fri Nov 3 03:23:24 2023 From: mtj at kohaaloha.com (Mason James) Date: Fri, 3 Nov 2023 15:23:24 +1300 Subject: [Koha-devel] Is koha-common.postinst restarting services in the correct order? In-Reply-To: <6e5bc024-db8e-4bae-a14b-847b23ec028f@catalyst.net.nz> References: <6e5bc024-db8e-4bae-a14b-847b23ec028f@catalyst.net.nz> Message-ID: hi Aleisha i added a fix here... https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35242 On 26/10/23 10:28 am, Aleisha Amohia via Koha-devel wrote: > Hello everyone > > Curious what other people think here... > > We have set up koha-common to be upgraded using unattended upgrades. Whenever we do this, something happens to koha-worker and eventually worker-output.log fills up the disk. can you add a sample of the worker-output.log file, that's filling the disk > The only solution appears to be deleting the log file then restarting memcached and koha-common - but it would be good to avoid doing this if our packages get upgraded for us overnight. From ztajoli at gmail.com Fri Nov 3 08:38:30 2023 From: ztajoli at gmail.com (Zeno Tajoli) Date: Fri, 3 Nov 2023 08:38:30 +0100 Subject: [Koha-devel] Download a record with curl and Koha API Message-ID: Hi, I'm trying to download a record using curl and GET /biblios/{biblio_id} With curl I try: curl -u user:Pwd --request GET 'http://127.0.0.1:8080/api/v1/biblios/xxxx' --header "Content-Type: application/json" But the answer is: ["application\/json","application\/marcxml+xml","application\/marc-in-json","application\/marc","text\/plain"] not a json with the MARC21 data. What is the error ? Cheers Zeno Tajoli From jonathan.druart at bugs.koha-community.org Fri Nov 3 09:09:45 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 3 Nov 2023 09:09:45 +0100 Subject: [Koha-devel] Last month before the release In-Reply-To: <020a01da0dee$8e90c200$abb24600$@prosentient.com.au> References: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> <020a01da0dee$8e90c200$abb24600$@prosentient.com.au> Message-ID: David, if you don't know Jenkins and you are part of the QA team, I guess you are not alone to be lost with our CI structure and it means we have a big problem. Either motivation, or tools or communication. I am not answering you now but maybe we need to document a bit better how it works for the next release, responsibilize people (asking them to fix what they broke instead of fixing for them) and finally maybe have a live chat beginning of the cycle with RMaints and QA team to (re) explain how it works. Le vendredi 3 novembre 2023, David Cook via Koha-devel < koha-devel at lists.koha-community.org> a écrit : > It’s not clear to me though how you look at Jenkins runs. Is it going to https://dashboard.koha-community.org/ and then clicking on one of the badges to go to Jenkins like https://jenkins.koha-community.org/job/Koha_Master_U22/ and then clicking on “Latest Test Result”? > > > > 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 > Sent: Friday, 3 November 2023 11:25 AM > To: David Cook > Cc: koha-devel > Subject: Re: [Koha-devel] Last month before the release > > > > The suggested sequence is: > > > > 1. You notice your stuff for pushed, yay! > > 2. You look at Jenkins runs for the relevant branches (e.g. Koha_Master_* tasks) > > 3. If some test gets broken that day, you try too see if it was you. Beware sometimes it is not obvious. > > > > Today there was a failure in the holds API tests, because of a bug that didn't touch the API, but made the code stricter (?) so the loose tests we had written had to be tweaked so they didn't trigger a silly error. > > > > So the devs did right, didn't introduce a bug, but made the tests fail. But it is all of us, specially those who got patches pushed, who should be looking after those failures. Team work > > > > Thanks! > > > > El jue, 2 nov 2023 21:15, David Cook escribió: > > What’s the best way to do this? > > > > I think Jenkins might send emails, but I think my mail server blocked it ages ago as spam. > > > > 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: Koha-devel On Behalf Of Tomas Cohen Arazi via Koha-devel > Sent: Friday, 3 November 2023 12:31 AM > To: koha-devel > Subject: [Koha-devel] Last month before the release > > > > Hi all. > > > > We are almost done with the release, a couple medium/big things to push today/tomorrow and then bug fixing. > > > > I wanted to ask y'all to please view the Jenkins tasks status anytime after your stuff has been pushed. I know I said this many times, but some devs clearly break some tests that are trivially fixable and the team needs you to take care of your breakages. > > > > I'm doing my best to track things and fix, but you should all be worried about that. > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Fri Nov 3 09:41:23 2023 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Thu, 2 Nov 2023 22:41:23 -1000 Subject: [Koha-devel] [Koha] Roles for 24.05 are open In-Reply-To: <491447b8-c544-4944-8f09-3ec7d5be0b1f@biblibre.com> References: <491447b8-c544-4944-8f09-3ec7d5be0b1f@biblibre.com> Message-ID: <78f528a3-b8cc-454d-a45d-38746f129e26@biblibre.com> Hi, Sorry I could not attempt the meeting of 1 nov. Great news :D We have Frédéric Demians for 22.11 LTS Best regards, Le 28/10/2023 à 11:27, Fridolin SOMERS a écrit : > Hi community :D > > I'm happy to propose for the role of Release Maintainer for 23.11. > > I see we are currently missing a Release Maintainer for 22.11 LTS. > This is a very important role for our LTS proposition : > https://wiki.koha-community.org/wiki/Koha_Versioning#LTS_Releases > > Best regards, > > Le 18/10/2023 à 03:18, Tomas Cohen Arazi a écrit : >> A new cycle is about to start. It is time for you all to put your >> names for >> the next release. >> >> Here: https://wiki.koha-community.org/wiki/Roles_for_24.05 >> >> Best regards >> > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From tomascohen at gmail.com Fri Nov 3 13:49:39 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 3 Nov 2023 09:49:39 -0300 Subject: [Koha-devel] Last month before the release In-Reply-To: References: Message-ID: Hi all, this is master's latest failures: https://jenkins.koha-community.org/job/Koha_Master/lastCompletedBuild/testReport/ The selenium failure has been there for a while, and the other ones are recent. El jue, 2 nov 2023 a las 10:30, Tomas Cohen Arazi () escribió: > Hi all. > > We are almost done with the release, a couple medium/big things to push > today/tomorrow and then bug fixing. > > I wanted to ask y'all to please view the Jenkins tasks status anytime > after your stuff has been pushed. I know I said this many times, but some > devs clearly break some tests that are trivially fixable and the team needs > you to take care of your breakages. > > I'm doing my best to track things and fix, but you should all be worried > about that. > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Fri Nov 3 14:09:24 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 3 Nov 2023 14:09:24 +0100 Subject: [Koha-devel] Last month before the release In-Reply-To: References: Message-ID: Because of 26170, I left a comment there. Le ven. 3 nov. 2023 à 13:49, Tomas Cohen Arazi via Koha-devel a écrit : > > Hi all, this is master's latest failures: > > https://jenkins.koha-community.org/job/Koha_Master/lastCompletedBuild/testReport/ > > The selenium failure has been there for a while, and the other ones are recent. > > El jue, 2 nov 2023 a las 10:30, Tomas Cohen Arazi () escribió: >> >> Hi all. >> >> We are almost done with the release, a couple medium/big things to push today/tomorrow and then bug fixing. >> >> I wanted to ask y'all to please view the Jenkins tasks status anytime after your stuff has been pushed. I know I said this many times, but some devs clearly break some tests that are trivially fixable and the team needs you to take care of your breakages. >> >> I'm doing my best to track things and fix, but you should all be worried about that. >> >> -- >> Tomás Cohen Arazi >> Theke Solutions (https://theke.io) >> ✆ +54 9351 3513384 >> GPG: B2F3C15F > > > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From domm at plix.at Fri Nov 3 17:24:51 2023 From: domm at plix.at (Thomas Klausner) Date: Fri, 3 Nov 2023 17:24:51 +0100 Subject: [Koha-devel] Download a record with curl and Koha API In-Reply-To: References: Message-ID: Hi! On Fri, Nov 03, 2023 at 08:38:30AM +0100, Zeno Tajoli via Koha-devel wrote: > I'm trying to download a record using curl and GET /biblios/{biblio_id} > With curl I try: > curl -u user:Pwd --request GET > 'http://127.0.0.1:8080/api/v1/biblios/xxxx' --header "Content-Type: > application/json" > But the answer is: > ["application\/json","application\/marcxml+xml","application\/marc-in-json","application\/marc","text\/plain"] > not a json with the MARC21 data. > What is the error ? You need to tell the server what format you want via the 'Accept' header: curl -u user:Pwd --request GET 'http://127.0.0.1:8080/api/v1/biblios/xxxx' --header 'Accept: application/json' The "content-type" header tell the server the format of the data you're **sending** (but you're not sending anything..) Greetings, domm -- Thomas Klausner domm https://domm.plix.at Just another ( Perl | Postgres | Bicycle | Food | Photo | Vinyl ) Hacker Moneglia, Italy, via Puck, 2 day exposure [ 2023-10-14 10:00 > https://domm.plix.at/potd/2023-10-14.html ] Son #1 release a new very random, very fun game: Mosa Lina https://store.steampowered.com/app/2477090/Mosa_Lina/ [ 2023-10-24 19:57 > https://domm.plix.at/microblog.html ] From dcook at prosentient.com.au Mon Nov 6 00:31:34 2023 From: dcook at prosentient.com.au (David Cook) Date: Mon, 6 Nov 2023 10:31:34 +1100 Subject: [Koha-devel] Last month before the release In-Reply-To: References: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> <020a01da0dee$8e90c200$abb24600$@prosentient.com.au> Message-ID: <013b01da1040$3df0e600$b9d2b200$@prosentient.com.au> Thanks, Jonathan. Yeah, I think having a live chat sounds like a plan. Communication is good. Timezones, especially mine, make it tough, but being able to point at documentation for policies and procedures is helpful. 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: Jonathan Druart Sent: Friday, 3 November 2023 7:10 PM To: David Cook Cc: Tomas Cohen Arazi ; koha-devel Subject: Re: [Koha-devel] Last month before the release David, if you don't know Jenkins and you are part of the QA team, I guess you are not alone to be lost with our CI structure and it means we have a big problem. Either motivation, or tools or communication. I am not answering you now but maybe we need to document a bit better how it works for the next release, responsibilize people (asking them to fix what they broke instead of fixing for them) and finally maybe have a live chat beginning of the cycle with RMaints and QA team to (re) explain how it works. Le vendredi 3 novembre 2023, David Cook via Koha-devel > a écrit : > It’s not clear to me though how you look at Jenkins runs. Is it going to https://dashboard.koha-community.org/ and then clicking on one of the badges to go to Jenkins like https://jenkins.koha-community.org/job/Koha_Master_U22/ and then clicking on “Latest Test Result”? > > > > 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 > > Sent: Friday, 3 November 2023 11:25 AM > To: David Cook > > Cc: koha-devel > > Subject: Re: [Koha-devel] Last month before the release > > > > The suggested sequence is: > > > > 1. You notice your stuff for pushed, yay! > > 2. You look at Jenkins runs for the relevant branches (e.g. Koha_Master_* tasks) > > 3. If some test gets broken that day, you try too see if it was you. Beware sometimes it is not obvious. > > > > Today there was a failure in the holds API tests, because of a bug that didn't touch the API, but made the code stricter (?) so the loose tests we had written had to be tweaked so they didn't trigger a silly error. > > > > So the devs did right, didn't introduce a bug, but made the tests fail. But it is all of us, specially those who got patches pushed, who should be looking after those failures. Team work > > > > Thanks! > > > > El jue, 2 nov 2023 21:15, David Cook > escribió: > > What’s the best way to do this? > > > > I think Jenkins might send emails, but I think my mail server blocked it ages ago as spam. > > > > 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: Koha-devel > On Behalf Of Tomas Cohen Arazi via Koha-devel > Sent: Friday, 3 November 2023 12:31 AM > To: koha-devel > > Subject: [Koha-devel] Last month before the release > > > > Hi all. > > > > We are almost done with the release, a couple medium/big things to push today/tomorrow and then bug fixing. > > > > I wanted to ask y'all to please view the Jenkins tasks status anytime after your stuff has been pushed. I know I said this many times, but some devs clearly break some tests that are trivially fixable and the team needs you to take care of your breakages. > > > > I'm doing my best to track things and fix, but you should all be worried about that. > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Nov 6 07:03:13 2023 From: dcook at prosentient.com.au (David Cook) Date: Mon, 6 Nov 2023 17:03:13 +1100 Subject: [Koha-devel] Last month before the release References: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> <020a01da0dee$8e90c200$abb24600$@prosentient.com.au> Message-ID: <016101da1076$f0f71180$d2e53480$@prosentient.com.au> Also, regarding https://jenkins.koha-community.org/job/Koha_Master/lastCompletedBuild/testReport/ : I’ve got a fix for “t_db_dependent_Koha_Patrons_Import_t.No warning raised by import_patrons” at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35264 It looks like Katrin fixed “xt_author_valid_templates_t./kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation_batch_checkouts.tt” And I can’t reproduce the problem on master for “t_db_dependent_selenium_patrons_search_t.Search patrons”, so I’m guessing someone has already fixed that one? Hopefully the next run will be fail free :D 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: David Cook Sent: Monday, 6 November 2023 10:32 AM To: 'Jonathan Druart' Cc: 'Tomas Cohen Arazi' ; 'koha-devel' Subject: RE: [Koha-devel] Last month before the release Thanks, Jonathan. Yeah, I think having a live chat sounds like a plan. Communication is good. Timezones, especially mine, make it tough, but being able to point at documentation for policies and procedures is helpful. 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: Jonathan Druart > Sent: Friday, 3 November 2023 7:10 PM To: David Cook > Cc: Tomas Cohen Arazi >; koha-devel > Subject: Re: [Koha-devel] Last month before the release David, if you don't know Jenkins and you are part of the QA team, I guess you are not alone to be lost with our CI structure and it means we have a big problem. Either motivation, or tools or communication. I am not answering you now but maybe we need to document a bit better how it works for the next release, responsibilize people (asking them to fix what they broke instead of fixing for them) and finally maybe have a live chat beginning of the cycle with RMaints and QA team to (re) explain how it works. Le vendredi 3 novembre 2023, David Cook via Koha-devel > a écrit : > It’s not clear to me though how you look at Jenkins runs. Is it going to https://dashboard.koha-community.org/ and then clicking on one of the badges to go to Jenkins like https://jenkins.koha-community.org/job/Koha_Master_U22/ and then clicking on “Latest Test Result”? > > > > 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 > > Sent: Friday, 3 November 2023 11:25 AM > To: David Cook > > Cc: koha-devel > > Subject: Re: [Koha-devel] Last month before the release > > > > The suggested sequence is: > > > > 1. You notice your stuff for pushed, yay! > > 2. You look at Jenkins runs for the relevant branches (e.g. Koha_Master_* tasks) > > 3. If some test gets broken that day, you try too see if it was you. Beware sometimes it is not obvious. > > > > Today there was a failure in the holds API tests, because of a bug that didn't touch the API, but made the code stricter (?) so the loose tests we had written had to be tweaked so they didn't trigger a silly error. > > > > So the devs did right, didn't introduce a bug, but made the tests fail. But it is all of us, specially those who got patches pushed, who should be looking after those failures. Team work > > > > Thanks! > > > > El jue, 2 nov 2023 21:15, David Cook > escribió: > > What’s the best way to do this? > > > > I think Jenkins might send emails, but I think my mail server blocked it ages ago as spam. > > > > 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: Koha-devel > On Behalf Of Tomas Cohen Arazi via Koha-devel > Sent: Friday, 3 November 2023 12:31 AM > To: koha-devel > > Subject: [Koha-devel] Last month before the release > > > > Hi all. > > > > We are almost done with the release, a couple medium/big things to push today/tomorrow and then bug fixing. > > > > I wanted to ask y'all to please view the Jenkins tasks status anytime after your stuff has been pushed. I know I said this many times, but some devs clearly break some tests that are trivially fixable and the team needs you to take care of your breakages. > > > > I'm doing my best to track things and fix, but you should all be worried about that. > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Mon Nov 6 15:05:45 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 6 Nov 2023 15:05:45 +0100 Subject: [Koha-devel] Last month before the release In-Reply-To: <016101da1076$f0f71180$d2e53480$@prosentient.com.au> References: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> <020a01da0dee$8e90c200$abb24600$@prosentient.com.au> <016101da1076$f0f71180$d2e53480$@prosentient.com.au> Message-ID: selenium/patrons_search.t has been failing randomly for a while. Failures should be reported on bug 31199. Le lun. 6 nov. 2023 à 07:03, David Cook a écrit : > Also, regarding > https://jenkins.koha-community.org/job/Koha_Master/lastCompletedBuild/testReport/ > : > > > > I’ve got a fix for “t_db_dependent_Koha_Patrons_Import_t.No warning raised > by import_patrons” at > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35264 > > > > It looks like Katrin fixed > “xt_author_valid_templates_t./kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/modules/circ/ > circulation_batch_checkouts.tt” > > > > And I can’t reproduce the problem on master for > “t_db_dependent_selenium_patrons_search_t.Search patrons”, so I’m guessing > someone has already fixed that one? > > > > Hopefully the next run will be fail free :D > > > > 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:* David Cook > *Sent:* Monday, 6 November 2023 10:32 AM > *To:* 'Jonathan Druart' > *Cc:* 'Tomas Cohen Arazi' ; 'koha-devel' < > koha-devel at lists.koha-community.org> > *Subject:* RE: [Koha-devel] Last month before the release > > > > Thanks, Jonathan. Yeah, I think having a live chat sounds like a plan. > Communication is good. > > > > Timezones, especially mine, make it tough, but being able to point at > documentation for policies and procedures is helpful. > > > > 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:* Jonathan Druart > *Sent:* Friday, 3 November 2023 7:10 PM > *To:* David Cook > *Cc:* Tomas Cohen Arazi ; koha-devel < > koha-devel at lists.koha-community.org> > *Subject:* Re: [Koha-devel] Last month before the release > > > > David, if you don't know Jenkins and you are part of the QA team, I guess > you are not alone to be lost with our CI structure and it means we have a > big problem. Either motivation, or tools or communication. > I am not answering you now but maybe we need to document a bit better how > it works for the next release, responsibilize people (asking them to fix > what they broke instead of fixing for them) and finally maybe have a live > chat beginning of the cycle with RMaints and QA team to (re) explain how it > works. > > Le vendredi 3 novembre 2023, David Cook via Koha-devel < > koha-devel at lists.koha-community.org> a écrit : > > It’s not clear to me though how you look at Jenkins runs. Is it going to > https://dashboard.koha-community.org/ and then clicking on one of the > badges to go to Jenkins like > https://jenkins.koha-community.org/job/Koha_Master_U22/ and then clicking > on “Latest Test Result”? > > > > > > > > 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 > > Sent: Friday, 3 November 2023 11:25 AM > > To: David Cook > > Cc: koha-devel > > Subject: Re: [Koha-devel] Last month before the release > > > > > > > > The suggested sequence is: > > > > > > > > 1. You notice your stuff for pushed, yay! > > > > 2. You look at Jenkins runs for the relevant branches (e.g. > Koha_Master_* tasks) > > > > 3. If some test gets broken that day, you try too see if it was you. > Beware sometimes it is not obvious. > > > > > > > > Today there was a failure in the holds API tests, because of a bug that > didn't touch the API, but made the code stricter (?) so the loose tests we > had written had to be tweaked so they didn't trigger a silly error. > > > > > > > > So the devs did right, didn't introduce a bug, but made the tests fail. > But it is all of us, specially those who got patches pushed, who should be > looking after those failures. Team work > > > > > > > > Thanks! > > > > > > > > El jue, 2 nov 2023 21:15, David Cook > escribió: > > > > What’s the best way to do this? > > > > > > > > I think Jenkins might send emails, but I think my mail server blocked it > ages ago as spam. > > > > > > > > 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: Koha-devel On > Behalf Of Tomas Cohen Arazi via Koha-devel > > Sent: Friday, 3 November 2023 12:31 AM > > To: koha-devel > > Subject: [Koha-devel] Last month before the release > > > > > > > > Hi all. > > > > > > > > We are almost done with the release, a couple medium/big things to push > today/tomorrow and then bug fixing. > > > > > > > > I wanted to ask y'all to please view the Jenkins tasks status anytime > after your stuff has been pushed. I know I said this many times, but some > devs clearly break some tests that are trivially fixable and the team needs > you to take care of your breakages. > > > > > > > > I'm doing my best to track things and fix, but you should all be worried > about that. > > > > > > > > -- > > > > Tomás Cohen Arazi > > > > Theke Solutions (https://theke.io) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Mon Nov 6 19:22:11 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 6 Nov 2023 15:22:11 -0300 Subject: [Koha-devel] Last month before the release In-Reply-To: References: <01fc01da0dea$ce5869a0$6b093ce0$@prosentient.com.au> <020a01da0dee$8e90c200$abb24600$@prosentient.com.au> <016101da1076$f0f71180$d2e53480$@prosentient.com.au> Message-ID: Hi all. First of all, thanks everyone for looking after the problems. Things are almost green. About the 'random failure', I've gotta say it is pretty consistent the last weeks. El lun, 6 nov 2023 a las 11:06, Jonathan Druart via Koha-devel (< koha-devel at lists.koha-community.org>) escribió: > selenium/patrons_search.t has been failing randomly for a while. > Failures should be reported on bug 31199. > > Le lun. 6 nov. 2023 à 07:03, David Cook a > écrit : > >> Also, regarding >> https://jenkins.koha-community.org/job/Koha_Master/lastCompletedBuild/testReport/ >> : >> >> >> >> I’ve got a fix for “t_db_dependent_Koha_Patrons_Import_t.No warning >> raised by import_patrons” at >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35264 >> >> >> >> It looks like Katrin fixed >> “xt_author_valid_templates_t./kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/modules/circ/ >> circulation_batch_checkouts.tt” >> >> >> >> And I can’t reproduce the problem on master for >> “t_db_dependent_selenium_patrons_search_t.Search patrons”, so I’m guessing >> someone has already fixed that one? >> >> >> >> Hopefully the next run will be fail free :D >> >> >> >> 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:* David Cook >> *Sent:* Monday, 6 November 2023 10:32 AM >> *To:* 'Jonathan Druart' >> *Cc:* 'Tomas Cohen Arazi' ; 'koha-devel' < >> koha-devel at lists.koha-community.org> >> *Subject:* RE: [Koha-devel] Last month before the release >> >> >> >> Thanks, Jonathan. Yeah, I think having a live chat sounds like a plan. >> Communication is good. >> >> >> >> Timezones, especially mine, make it tough, but being able to point at >> documentation for policies and procedures is helpful. >> >> >> >> 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:* Jonathan Druart >> *Sent:* Friday, 3 November 2023 7:10 PM >> *To:* David Cook >> *Cc:* Tomas Cohen Arazi ; koha-devel < >> koha-devel at lists.koha-community.org> >> *Subject:* Re: [Koha-devel] Last month before the release >> >> >> >> David, if you don't know Jenkins and you are part of the QA team, I guess >> you are not alone to be lost with our CI structure and it means we have a >> big problem. Either motivation, or tools or communication. >> I am not answering you now but maybe we need to document a bit better how >> it works for the next release, responsibilize people (asking them to fix >> what they broke instead of fixing for them) and finally maybe have a live >> chat beginning of the cycle with RMaints and QA team to (re) explain how it >> works. >> >> Le vendredi 3 novembre 2023, David Cook via Koha-devel < >> koha-devel at lists.koha-community.org> a écrit : >> > It’s not clear to me though how you look at Jenkins runs. Is it going >> to https://dashboard.koha-community.org/ and then clicking on one of the >> badges to go to Jenkins like >> https://jenkins.koha-community.org/job/Koha_Master_U22/ and then >> clicking on “Latest Test Result”? >> > >> > >> > >> > 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 >> > Sent: Friday, 3 November 2023 11:25 AM >> > To: David Cook >> > Cc: koha-devel >> > Subject: Re: [Koha-devel] Last month before the release >> > >> > >> > >> > The suggested sequence is: >> > >> > >> > >> > 1. You notice your stuff for pushed, yay! >> > >> > 2. You look at Jenkins runs for the relevant branches (e.g. >> Koha_Master_* tasks) >> > >> > 3. If some test gets broken that day, you try too see if it was you. >> Beware sometimes it is not obvious. >> > >> > >> > >> > Today there was a failure in the holds API tests, because of a bug that >> didn't touch the API, but made the code stricter (?) so the loose tests we >> had written had to be tweaked so they didn't trigger a silly error. >> > >> > >> > >> > So the devs did right, didn't introduce a bug, but made the tests fail. >> But it is all of us, specially those who got patches pushed, who should be >> looking after those failures. Team work >> > >> > >> > >> > Thanks! >> > >> > >> > >> > El jue, 2 nov 2023 21:15, David Cook >> escribió: >> > >> > What’s the best way to do this? >> > >> > >> > >> > I think Jenkins might send emails, but I think my mail server blocked >> it ages ago as spam. >> > >> > >> > >> > 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: Koha-devel On >> Behalf Of Tomas Cohen Arazi via Koha-devel >> > Sent: Friday, 3 November 2023 12:31 AM >> > To: koha-devel >> > Subject: [Koha-devel] Last month before the release >> > >> > >> > >> > Hi all. >> > >> > >> > >> > We are almost done with the release, a couple medium/big things to push >> today/tomorrow and then bug fixing. >> > >> > >> > >> > I wanted to ask y'all to please view the Jenkins tasks status anytime >> after your stuff has been pushed. I know I said this many times, but some >> devs clearly break some tests that are trivially fixable and the team needs >> you to take care of your breakages. >> > >> > >> > >> > I'm doing my best to track things and fix, but you should all be >> worried about that. >> > >> > >> > >> > -- >> > >> > Tomás Cohen Arazi >> > >> > Theke Solutions (https://theke.io) >> > ✆ +54 9351 3513384 >> > GPG: B2F3C15F >> > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue Nov 7 03:55:10 2023 From: dcook at prosentient.com.au (David Cook) Date: Tue, 7 Nov 2023 13:55:10 +1100 Subject: [Koha-devel] Using Elasticsearch in koha-testing-docker Message-ID: <022301da1125$d5a01030$80e03090$@prosentient.com.au> Hi all, I'm trying to use Elasticsearch in koha-testing-docker, and I would appreciate some assistance. Here's the steps I'm taking: 1. Launch koha-testing-docker 2. Update Koha's sysprefs a. Change SearchEngine from "Zebra" to "Elasticsearch" at http://localhost:8081/cgi-bin/koha/admin/preferences.pl?op=search &searchfield=SearchEngine 3. (Re)build Elasticsearch indexes: a. koha-elasticsearch --rebuild kohadev 4. Start Elasticsearch indexer: a. koha-es-indexer --start kohadev Is there anything else to do? In a prod install, do I just need to update the "elasticsearch" config in koha-conf.xml? Do I leave all the Zebra things running or can I turn those off? I recall reading somewhere that zebra_queue might fill up if I turn it off? Thanks all! 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Tue Nov 7 10:09:21 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 7 Nov 2023 10:09:21 +0100 Subject: [Koha-devel] Using Elasticsearch in koha-testing-docker In-Reply-To: <022301da1125$d5a01030$80e03090$@prosentient.com.au> References: <022301da1125$d5a01030$80e03090$@prosentient.com.au> Message-ID: About ktd you need to include one of the ES/OS compose files ( docker-compose.es* docker-compose.os*), there are bin/ktd switches. You also need KOHA_ELASTICSEARCH set to "yes" in the .env file. Le mar. 7 nov. 2023 à 03:55, David Cook via Koha-devel < koha-devel at lists.koha-community.org> a écrit : > Hi all, > > > > I’m trying to use Elasticsearch in koha-testing-docker, and I would > appreciate some assistance. > > > > Here’s the steps I’m taking: > > 1. Launch koha-testing-docker > 2. Update Koha’s sysprefs > 1. Change SearchEngine from “Zebra” to “Elasticsearch” at > http://localhost:8081/cgi-bin/koha/admin/preferences.pl?op=search&searchfield=SearchEngine > 3. (Re)build Elasticsearch indexes: > 1. koha-elasticsearch --rebuild kohadev > 4. Start Elasticsearch indexer: > 1. koha-es-indexer --start kohadev > > > > Is there anything else to do? In a prod install, do I just need to update > the “elasticsearch” config in koha-conf.xml? > > > > Do I leave all the Zebra things running or can I turn those off? I recall > reading somewhere that zebra_queue might fill up if I turn it off? > > > > Thanks all! > > > > 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 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Tue Nov 7 21:22:17 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 7 Nov 2023 21:22:17 +0100 Subject: [Koha-devel] Anybody still using tarballs? Message-ID: Hi, I am suggesting removing the tarball from our release process. I don't think anybody is using it anyway. It's extra work for RMaints, and it does not seem necessary. I am going to suggest removing the po files from the Koha src code starting from November releases, and that will require yet an extra (unnecessary?) step to embed the po files to generate the tarball. What do you think? Cheers, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Tue Nov 7 22:26:35 2023 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Wed, 8 Nov 2023 10:26:35 +1300 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: Message-ID: <055ea5fa-a275-414a-82d1-d2fe146bc5a5@catalyst.net.nz> Morning People are still downloading them, looking at the access logs on the server From this morning there are a few downloads, for example [07/Nov/2023:04:17:18 +0000] "GET /koha-22.11.10.tar.gz HTTP/1.1" 200 99643874 "https://download.koha-community.org/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36" [07/Nov/2023:04:46:02 +0000] "GET /koha-latest.tar.gz HTTP/1.1" 200 100758420 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Edg/119.0.0.0" I think it is worth keeping the. I doubt anyone who is using them will be on the koha-devel list though, or maybe even the main list, so download statistics is probably the best metric we have. Chris On 8/11/23 09:22, Jonathan Druart via Koha-devel wrote: > Hi, > > I am suggesting removing the tarball from our release process. I don't > think anybody is using it anyway. > It's extra work for RMaints, and it does not seem necessary. > I am going to suggest removing the po files from the Koha src code > starting from November releases, and that will require yet an extra > (unnecessary?) step to embed the po files to generate the tarball. > > What do you think? > > Cheers, > Jonathan > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Kaihuawaere Matihiko (he/him) Kāi Tahu, Kāti Māmoe, Waitaha Catalyst.Net Limited - Expert Open Source Solutions 027 4500789 chrisc at catalyst.net.nz From dcook at prosentient.com.au Wed Nov 8 01:09:01 2023 From: dcook at prosentient.com.au (David Cook) Date: Wed, 8 Nov 2023 11:09:01 +1100 Subject: [Koha-devel] Using Elasticsearch in koha-testing-docker In-Reply-To: References: <022301da1125$d5a01030$80e03090$@prosentient.com.au> Message-ID: <030701da11d7$cca076c0$65e16440$@prosentient.com.au> Thanks, Jonathan. I’ve done some playing around and I think I’m learning a lot about Koha’s integration. I’m a bit surprised that there isn’t an “any”, “all”, or “anywhere” index. I notice “ElasticsearchMARCFormat” can make the full MARC record searchable by storing the MARC record as a JSON object, but it seems like that’s not recommended. I don’t know why we wouldn’t just index the full record like we do with Zebra. It would make for a bigger data store, but it could be done fairly simply. Who all is actively contributing to the Elasticsearch work? Might be useful to get in on the conversation… 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: Jonathan Druart Sent: Tuesday, 7 November 2023 8:09 PM To: David Cook Cc: koha-devel Subject: Re: [Koha-devel] Using Elasticsearch in koha-testing-docker About ktd you need to include one of the ES/OS compose files (docker-compose.es * docker-compose.os*), there are bin/ktd switches. You also need KOHA_ELASTICSEARCH set to "yes" in the .env file. Le mar. 7 nov. 2023 à 03:55, David Cook via Koha-devel > a écrit : Hi all, I’m trying to use Elasticsearch in koha-testing-docker, and I would appreciate some assistance. Here’s the steps I’m taking: 1. Launch koha-testing-docker 2. Update Koha’s sysprefs a. Change SearchEngine from “Zebra” to “Elasticsearch” at http://localhost:8081/cgi-bin/koha/admin/preferences.pl?op=search &searchfield=SearchEngine 3. (Re)build Elasticsearch indexes: a. koha-elasticsearch --rebuild kohadev 4. Start Elasticsearch indexer: a. koha-es-indexer --start kohadev Is there anything else to do? In a prod install, do I just need to update the “elasticsearch” config in koha-conf.xml? Do I leave all the Zebra things running or can I turn those off? I recall reading somewhere that zebra_queue might fill up if I turn it off? Thanks all! 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 _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Wed Nov 8 08:04:44 2023 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 7 Nov 2023 21:04:44 -1000 Subject: [Koha-devel] Koha 23.05.05 released Message-ID: <6de224ef-8a67-4336-a3a6-04eeebb30aff@biblibre.com> Hello everyone 🤗 The Koha community is proud to announce the release of Koha 23.05.05. It is a bugfix/maintenance release including 16 enhancements, 85 bugfixes. The full release notes are available here: https://koha-community.org/koha-23-05-05-released/ Debian packages should be available soon 🎁 Note we are at the end of cycle. For next cycle I will continue as maintainer of 23.11 🛠️ Best regards 🤓 -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From jonathan.druart at bugs.koha-community.org Wed Nov 8 09:24:36 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 8 Nov 2023 09:24:36 +0100 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: <055ea5fa-a275-414a-82d1-d2fe146bc5a5@catalyst.net.nz> References: <055ea5fa-a275-414a-82d1-d2fe146bc5a5@catalyst.net.nz> Message-ID: Hi Chris, Thanks for the info, that's useful. Could you monitor these logs to have a rough estimate per month? Are we around 10, 100, 1000? Cheers, Jonathan Le mar. 7 nov. 2023 à 22:26, Chris Cormack via Koha-devel < koha-devel at lists.koha-community.org> a écrit : > Morning > > People are still downloading them, looking at the access logs on the server > > From this morning there are a few downloads, for example > > [07/Nov/2023:04:17:18 +0000] "GET /koha-22.11.10.tar.gz HTTP/1.1" 200 > 99643874 "https://download.koha-community.org/" "Mozilla/5.0 (Windows NT > 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) > Chrome/118.0.0.0 Safari/537.36" > > [07/Nov/2023:04:46:02 +0000] "GET /koha-latest.tar.gz HTTP/1.1" 200 > 100758420 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 > Edg/119.0.0.0" > > > I think it is worth keeping the. > I doubt anyone who is using them will be on the koha-devel list though, > or maybe even the main list, so download statistics is probably the best > metric we have. > > Chris > > On 8/11/23 09:22, Jonathan Druart via Koha-devel wrote: > > Hi, > > > > I am suggesting removing the tarball from our release process. I don't > > think anybody is using it anyway. > > It's extra work for RMaints, and it does not seem necessary. > > I am going to suggest removing the po files from the Koha src code > > starting from November releases, and that will require yet an extra > > (unnecessary?) step to embed the po files to generate the tarball. > > > > What do you think? > > > > Cheers, > > Jonathan > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > -- > Kaihuawaere Matihiko (he/him) > Kāi Tahu, Kāti Māmoe, Waitaha > Catalyst.Net Limited - Expert Open Source Solutions > 027 4500789 > chrisc at catalyst.net.nz > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Wed Nov 8 17:45:03 2023 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Thu, 09 Nov 2023 05:45:03 +1300 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: <055ea5fa-a275-414a-82d1-d2fe146bc5a5@catalyst.net.nz> Message-ID: Hi Jonathan Yup I'll run some stats over the logs Chris On 8 November 2023 9:24:36 pm NZDT, Jonathan Druart wrote: >Hi Chris, > >Thanks for the info, that's useful. >Could you monitor these logs to have a rough estimate per month? Are we >around 10, 100, 1000? > >Cheers, >Jonathan > >Le mar. 7 nov. 2023 à 22:26, Chris Cormack via Koha-devel < >koha-devel at lists.koha-community.org> a écrit : > >> Morning >> >> People are still downloading them, looking at the access logs on the server >> >> From this morning there are a few downloads, for example >> >> [07/Nov/2023:04:17:18 +0000] "GET /koha-22.11.10.tar.gz HTTP/1.1" 200 >> 99643874 "https://download.koha-community.org/" "Mozilla/5.0 (Windows NT >> 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) >> Chrome/118.0.0.0 Safari/537.36" >> >> [07/Nov/2023:04:46:02 +0000] "GET /koha-latest.tar.gz HTTP/1.1" 200 >> 100758420 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) >> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 >> Edg/119.0.0.0" >> >> >> I think it is worth keeping the. >> I doubt anyone who is using them will be on the koha-devel list though, >> or maybe even the main list, so download statistics is probably the best >> metric we have. >> >> Chris >> >> On 8/11/23 09:22, Jonathan Druart via Koha-devel wrote: >> > Hi, >> > >> > I am suggesting removing the tarball from our release process. I don't >> > think anybody is using it anyway. >> > It's extra work for RMaints, and it does not seem necessary. >> > I am going to suggest removing the po files from the Koha src code >> > starting from November releases, and that will require yet an extra >> > (unnecessary?) step to embed the po files to generate the tarball. >> > >> > What do you think? >> > >> > Cheers, >> > Jonathan >> > >> > _______________________________________________ >> > Koha-devel mailing list >> > Koha-devel at 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/ >> >> -- >> Kaihuawaere Matihiko (he/him) >> Kāi Tahu, Kāti Māmoe, Waitaha >> Catalyst.Net Limited - Expert Open Source Solutions >> 027 4500789 >> chrisc at catalyst.net.nz >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ >> -- Kaihuawaere Matihiko (he/him) Kāi Tahu, Kāti Māmoe, Waitaha Catalyst.Net Limited - Expert Open Source Solutions 027 4500789 chrisc at catalyst.net.nz -------------- next part -------------- An HTML attachment was scrubbed... URL: From victor at tuxayo.net Fri Nov 10 04:52:19 2023 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 10 Nov 2023 04:52:19 +0100 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: <055ea5fa-a275-414a-82d1-d2fe146bc5a5@catalyst.net.nz> Message-ID: Hi :) To still provide tarballs without release process steps to maintain and perform every time there is still this: https://git.koha-community.org/Koha-community/Koha/tags No files for signature though. Though, where can people find the rmaint public keys anyway? So I'm not sure anyone uses this to get Koha. Hum, after trying, the forge is a bit weird about the tarball feature, it seems the link doesn't work. But after like 30 sec of processing it works. (might need to click again) And subsequent clicks work directly. Direct link still work though: https://git.koha-community.org/Koha-community/Koha/archive/v23.05.05.tar.gz Oh no when using the direct link the 1st time, it ends up in a 500 error and next try it works. (timeout?) So having the release process get the tarball URL to trigger the generation would work. Still a bit wack but could be an alternative to keep tarballs without much work. (same behavior on Forgejo, tested on codeberg.org but it's likely with a fast enough server the request doesn't timeout or something) Cheers, -- Victor Grousset/tuxayo From jonathan.druart at bugs.koha-community.org Fri Nov 10 08:50:17 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 10 Nov 2023 08:50:17 +0100 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: <055ea5fa-a275-414a-82d1-d2fe146bc5a5@catalyst.net.nz> Message-ID: You missed the original request, Victor. The .po files will be missing from the src and so the git extract won't be enough. I think we better need to have a job triggered on tags pushed that will build and push the .tar.gz files. Le ven. 10 nov. 2023 à 04:52, Victor Grousset/tuxayo via Koha-devel < koha-devel at lists.koha-community.org> a écrit : > Hi :) > > To still provide tarballs without release process steps to maintain and > perform every time there is still this: > https://git.koha-community.org/Koha-community/Koha/tags > No files for signature though. Though, where can people find the rmaint > public keys anyway? So I'm not sure anyone uses this to get Koha. > > Hum, after trying, the forge is a bit weird about the tarball feature, > it seems the link doesn't work. But after like 30 sec of processing it > works. (might need to click again) And subsequent clicks work directly. > > Direct link still work though: > https://git.koha-community.org/Koha-community/Koha/archive/v23.05.05.tar.gz > > Oh no when using the direct link the 1st time, it ends up in a 500 error > and next try it works. (timeout?) > > So having the release process get the tarball URL to trigger the > generation would work. Still a bit wack but could be an alternative to > keep tarballs without much work. (same behavior on Forgejo, tested on > codeberg.org but it's likely with a fast enough server the request > doesn't timeout or something) > > Cheers, > > -- > Victor Grousset/tuxayo > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmc at equinoxoli.org Fri Nov 10 15:00:51 2023 From: gmc at equinoxoli.org (Galen Charlton) Date: Fri, 10 Nov 2023 09:00:51 -0500 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: Message-ID: Hi, On Tue, Nov 7, 2023 at 3:22 PM Jonathan Druart via Koha-devel < koha-devel at lists.koha-community.org> wrote: > I am suggesting removing the tarball from our release process. I don't > think anybody is using it anyway. > It's extra work for RMaints, and it does not seem necessary. > I know that there are some Koha libraries running on RedHat-derived distributions. While such sites could in principle maintain their installations from Git checkouts, they are a constituency of likey tarball users. Regards, Galen -- Galen Charlton Implementation and IT Manager Equinox Open Library Initiative gmc at equinoxOLI.org https://www.equinoxOLI.org phone: 877-OPEN-ILS (673-6457) direct: 770-709-5581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Fri Nov 10 16:08:26 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 10 Nov 2023 12:08:26 -0300 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: Message-ID: Gitlab allows you to download a tar.gz, and commits are GPG signed already. Maybe we can change the workflow. We should take some time to think about it next cycle. El mar, 7 nov 2023 a las 17:22, Jonathan Druart via Koha-devel (< koha-devel at lists.koha-community.org>) escribió: > Hi, > > I am suggesting removing the tarball from our release process. I don't > think anybody is using it anyway. > It's extra work for RMaints, and it does not seem necessary. > I am going to suggest removing the po files from the Koha src code > starting from November releases, and that will require yet an extra > (unnecessary?) step to embed the po files to generate the tarball. > > What do you think? > > Cheers, > Jonathan > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Fri Nov 10 16:15:53 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 10 Nov 2023 16:15:53 +0100 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: Message-ID: But it won't embed po files. Please see my reply to Victor. Le vendredi 10 novembre 2023, Tomas Cohen Arazi a écrit : > Gitlab allows you to download a tar.gz, and commits are GPG signed already. > Maybe we can change the workflow. We should take some time to think about it next cycle. > El mar, 7 nov 2023 a las 17:22, Jonathan Druart via Koha-devel (< koha-devel at lists.koha-community.org>) escribió: >> >> Hi, >> I am suggesting removing the tarball from our release process. I don't think anybody is using it anyway. >> It's extra work for RMaints, and it does not seem necessary. >> I am going to suggest removing the po files from the Koha src code starting from November releases, and that will require yet an extra (unnecessary?) step to embed the po files to generate the tarball. >> What do you think? >> Cheers, >> Jonathan >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > > > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Fri Nov 10 16:18:42 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 10 Nov 2023 12:18:42 -0300 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: Message-ID: Yes, you're correct. We need to spend some time reviewing our build pipeline process and distribution mechanisms. I can spend time on that right after the release. Have a great weekend, and enjoy your holiday, US people. El vie, 10 nov 2023 a las 12:15, Jonathan Druart (< jonathan.druart at bugs.koha-community.org>) escribió: > But it won't embed po files. > Please see my reply to Victor. > > Le vendredi 10 novembre 2023, Tomas Cohen Arazi a > écrit : > > Gitlab allows you to download a tar.gz, and commits are GPG signed > already. > > Maybe we can change the workflow. We should take some time to think > about it next cycle. > > El mar, 7 nov 2023 a las 17:22, Jonathan Druart via Koha-devel (< > koha-devel at lists.koha-community.org>) escribió: > >> > >> Hi, > >> I am suggesting removing the tarball from our release process. I don't > think anybody is using it anyway. > >> It's extra work for RMaints, and it does not seem necessary. > >> I am going to suggest removing the po files from the Koha src code > starting from November releases, and that will require yet an extra > (unnecessary?) step to embed the po files to generate the tarball. > >> What do you think? > >> Cheers, > >> Jonathan > >> _______________________________________________ > >> Koha-devel mailing list > >> Koha-devel at 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/ > > > > > > -- > > Tomás Cohen Arazi > > Theke Solutions (https://theke.io) > > ✆ +54 9351 3513384 > > GPG: B2F3C15F -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From victor at tuxayo.net Fri Nov 10 16:33:09 2023 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 10 Nov 2023 16:33:09 +0100 Subject: [Koha-devel] Anybody still using tarballs? In-Reply-To: References: <055ea5fa-a275-414a-82d1-d2fe146bc5a5@catalyst.net.nz> Message-ID: <697df89b-fb82-4e63-9da6-5d906be846c3@tuxayo.net> On 23-11-10 08:50, Jonathan Druart wrote: > You missed the original request, Victor. The .po files will be missing > from the src and so the git extract won't be enough. Indeed! Read it and forgot it when looking at how to get them from the forge... > I think we better need to have a job triggered on tags pushed that will build and push the .tar.gz files. If there isn't much usage maybe it's ok to have one tarball for Koha itself and one for the .po files. And if there are requests for a complete tarball then maybe do a job. Not sure about the tarball usage but if it's for manual installs then having a step to extract the .po tarball in the directory of koha could be okay for users. Cheers, -- Victor Grousset/tuxayo From jonathan.druart at bugs.koha-community.org Sat Nov 11 22:03:10 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Sat, 11 Nov 2023 22:03:10 +0100 Subject: [Koha-devel] Translation server migrated Message-ID: Hello, The translation server has been migrated from Pootle to Weblate. It's a whole new server with a complete new workflow. The goal was to have it ready to translate 23.11, but everything is not set up yet (downtimes may appear). You can login with your Pootle credentials, and you should have the same privileges (part of a language team/administrator of the team). Note that no SMTP server (email) is configured yet. There are some heavy tasks that will be run from 1:00 to 2:00 UTC and from 3:00 to 5:00 (or 6:00? I don't know yet!), expect a slow response time during these slots (can be adjusted later if needed). More information (about what has been done and what still need to be done) can be found on the wiki page https://wiki.koha-community.org/wiki/Translation_server_migration_weblate Please report any problems you encounter! Happy translating! Cheers, Jonathan PS: email to the general mailing list about this migration will be sent next week. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohanews at gmail.com Mon Nov 13 10:05:47 2023 From: kohanews at gmail.com (Koha Newsletter) Date: Mon, 13 Nov 2023 10:05:47 +0100 Subject: [Koha-devel] Call for news - Newsletter November 2023 Message-ID: Hi I'm collecting news for the November 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Mon Nov 27 10:38:02 2023 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 27 Nov 2023 10:38:02 +0100 Subject: [Koha-devel] Hackfest in Marseille in 2024 Message-ID: Hello koha-devel, A couple of you asked "will there be a hackfest in Marseille in 2024, and when ?" So I answer publicly: * yes, there will be a koha hackfest in Marseille * it will not be late march as usual (holy week then easter) but in April, 8th - 12th * BibLibre has moved, our new office is a little bit smaller than the previous one, I have to think of the formula. Not sure if it will be as "open to anyone" as it used to be. We can easily/comfortably host 35 ppl, maybe 40. More would mean being crowded maybe, so I'll have to think of how to manage registrations. But there will be a hackfest, definitely ! Cheers, -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue Nov 28 03:55:38 2023 From: dcook at prosentient.com.au (David Cook) Date: Tue, 28 Nov 2023 13:55:38 +1100 Subject: [Koha-devel] "Online access" vs "Online resources" Message-ID: <000001da21a6$634bca10$29e35e30$@prosentient.com.au> Hi all, Detail pages say "Online resources" but search results say "Online access". I don't know if I've never noticed before or what but I had a librarian raise it today. I think it makes sense to harmonise so that they're both the same, but how do we choose which one? I've raised a ticket for this: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35410 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohadevel at agogme.com Tue Nov 28 16:52:46 2023 From: kohadevel at agogme.com (Thomas Dukleth) Date: Tue, 28 Nov 2023 15:52:46 -0000 Subject: [Koha-devel] Feb. 2024 prospects of Koha lists delivery problems for Gmail, etc. Message-ID: <50359817bd09604765caac6bcd74558a.squirrel@wmail.agogme.com> Beginning in February 2024, Koha mailing lists may have delivery problems for recipients using some large email service providers such as Gmail if not fixed. The problem is more likely to affect such recipients of the Koha general mailing list because more needs fixing even if relatively easy to fix and it might additionally be considered a large volume sender if there are enough subscribers reading via Gmail including on popular mobile devices despite fewer otherwise evident Gmail users. Please give attention to new party needed for hosting the Koha general mailing list in section 2.2 further below. 1. Diminishing Time for Implementing Fixes. By February 2024, fixing DKIM signing and re-signing may be needed for lists.koha-community.org lists such as koha-devel and more for the Koha general mailing list when Gmail and Yahoo mail [with AOL] may start blocking messages for not being DKIM re-signed when sent from the mailing lists. It is uncertain whether Gmail and Yahoo mail will continue to give a false pass for messages using the original author's DKIM signature which does not match the mailing list sending server, nor the From header with DMARC support enabled. A false DKIM pass may be more likely than not in February for the low volume mailing lists.koha-community.org, but we have been warned, see the announcements linked below. [The Koha general mailing list may be more of a problem with more configuration needed and a greater prospect of being recognised as a large volume sender.] Gmail, Yahoo mail, AOL mail, Microsoft [Exchange and various names] etc. have all rejected messages for bad DKIM signature from mailing lists during past periods of extra DKIM strictness. 2. Details of Changes Needed. See the bug report for some implementation details, "Adding DMARC compatibility to mailing lists" - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34927 . The bug issue was slowly being advanced over the past year before any knowledge of any particular forthcoming changes at large email providers such as Google. 2.1. BibLibre Hosted Mailing Lists. I have given precise technical details of changes which may be made to Laurent Ducos and Fridolin Somers at BibLibre for resolving the issue of OpenDKIM signing and resigning for lists.koha-community.org . 2.2. New Party Needed to Host the Koha General Mailing List. I have also communicated with Rachel Hamilton-Williams about adding DMARC support for the Koha general mailing list. In addition to DKIM support, lists.katipo.co.nz needs a DMARC record in DNS and then activating DMARC in Mailman, and possibly an SPF record for the subdomain lists.katipo.co.nz . Rachel informed me that she would like to hand over hosting of the Koha mailing list for more attentive management than her partner and system administrator, Simon Blake, may be able to provide currently. Without the very simple task of adding DMARC support to the Koha general list, delivery problems are more likely than not for Gmail, Yahoo, etc. subscribers from Feb. A false pass would need at least the pretence of DMARC support. ARC support is required for all mailing lists irrespective of size, for which DMARC might be a workaround as possibly avoiding the need for ARC support. 3. February 2024 Changes for Gmail and Yahoo Mail, etc. At the end of last week, a radio broadcast brought my attention to changes coming in February 2024 which affect everyone in some manner. Everyone includes lists.koha-community.org. Large volume senders have additional requirements. [For large volume senders, there additional requirements beyond those affecting everyone, which might affect people subscribing to the Koha general mailing list if the number of mailing list subscribers is enough and enough people route mail through the popular choice of Gmail even on mobile despite having some other apparent domain of some subscriber wherever that may be hosted initially.] Details about more stringent SPF, DKIM, DMARC, ARC, and one-click unsubscribe link requirements are available from Google. Mailing lists may be able to substitute DMARC support for lack of ARC support when rewriting the From header and thus re-originating and not merely forwarding messages but adding ARC is best addressed second. "Email sender guidelines : Requirements for all senders" - https://support.google.com/mail/answer/81126#zippy=%2Crequirements-for-all-senders . Another part of the same document has the requirements which may affect the Koha general mailing list "Requirements for sending 5,000 or more messages per day" - https://support.google.com/mail/answer/81126#requirements-5k&zippy=%2Crequirements-for-sending-or-more-messages-per-day . The Yahoo guide which I found has fewer details and does not refer to the coming February 2024 policy change: "Sender Best Practices" - https://senders.yahooinc.com/best-practices/ . There is no shortage of secondary sources such as from the support provider Proofpoint, "Google and Yahoo Set a Short Timeline to Meet New DMARC Policy & Setup Requirements. Are You Ready?" - https://www.proofpoint.com/us/blog/email-and-cloud-threats/google-and-yahoo-set-new-email-authentication-requirements . 4. Note on ARC Support. ARC is intended for authenticating the email chain when forwarding messages which is the basic function of mailing lists. Adding DMARC support should make the issue of ARC support for acceptable authentication for mailing lists might be moot because the mailing list is more clearly shown as re-originating email and not merely forwarding. However, the announcements for February 2024 do not state that case with explicit clarity and Gmail adds ARC headers to all mail on their system and people at Google may presume that everyone else should to especially when messages may retain headers showing that the message has been forwarded over the mailing list despite having been re-originated from mailing list with DMARC authentication. While Mailman 3 has functionality for ARC support which was added essentially experimentally a few years ago, the proper place for ARC support is in the MTA not in the mailing list software. When using ARC via Mailman 3 the mail envelope is sealed before DKIM re-signing which is the wrong order and has caused ARC authentication failure. OpenARC, like OpenDKIM, functions in the MTA for Postfix or Sendmail, https://github.com/trusteddomainproject/OpenARC . Mailing lists at https://openarc.org/ . OpenARC is not as fully developed as OpenDKIM and support for some nice things such as multiple sending domains on the system seems to have been abandoned. OpenARC has better support for BSD Unix and Red Hat than Debian based systems but is not as well developed, and although not robustly maintained for Debian based systems, there are openarc packages based on the OpenARC development branch for Debian 9 to 11, https://download.opensuse.org/repositories/home%3A/andreasschulze/ . [Mailman 2 which we are using for the mailing lists does not go past Debian 10 for lack of Python 2. Upgrading to Mailman 3 is non-trivial because of configuration changes, etc. and should not be the most immediate priority.] There is a very brief blog post about using the Andreas Schulze Debian packages, "OpenARC with Postfix on Debian 10 (buster)" / Matthieu - https://weber.fi.eu.org/blog/Informatique/openarc_with_postfix_on_debian_10.html . You can also build your own packages from source as I have. [In current testing of my source build, Postfix has a socket permissions error for OpenARC which may be from a mistake I had made with umask settings long ago on the system which runs my mailserver.] Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kohadevel at agogme.com Tue Nov 28 17:37:45 2023 From: kohadevel at agogme.com (Thomas Dukleth) Date: Tue, 28 Nov 2023 16:37:45 -0000 Subject: [Koha-devel] Feb. 2024 prospects of Koha lists delivery problems for Gmail, etc. Message-ID: [Resent without the accidental attachment from an unrelated message of David Cook which produced peculiar mailing list behaviour assigning the wrong thread and no copy of my own message from the mailing list. I do not generally use HTML mail attachments and did not notice it at the bottom of my compose window from the previous message rewriting from the forward function instead of new list message.] Beginning in February 2024, Koha mailing lists may have delivery problems for recipients using some large email service providers such as Gmail if not fixed. The problem is more likely to affect such recipients of the Koha general mailing list because more needs fixing even if relatively easy to fix and it might additionally be considered a large volume sender if there are enough subscribers reading via Gmail including on popular mobile devices despite fewer otherwise evident Gmail users. Please give attention to new party needed for hosting the Koha general mailing list in section 2.2 further below. 1. Diminishing Time for Implementing Fixes. By February 2024, fixing DKIM signing and re-signing may be needed for lists.koha-community.org lists such as koha-devel and more for the Koha general mailing list when Gmail and Yahoo mail [with AOL] may start blocking messages for not being DKIM re-signed when sent from the mailing lists. It is uncertain whether Gmail and Yahoo mail will continue to give a false pass for messages using the original author's DKIM signature which does not match the mailing list sending server, nor the From header with DMARC support enabled. A false DKIM pass may be more likely than not in February for the low volume mailing lists.koha-community.org, but we have been warned, see the announcements linked below. [The Koha general mailing list may be more of a problem with more configuration needed and a greater prospect of being recognised as a large volume sender.] Gmail, Yahoo mail, AOL mail, Microsoft [Exchange and various names] etc. have all rejected messages for bad DKIM signature from mailing lists during past periods of extra DKIM strictness. 2. Details of Changes Needed. See the bug report for some implementation details, "Adding DMARC compatibility to mailing lists" - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34927 . The bug issue was slowly being advanced over the past year before any knowledge of any particular forthcoming changes at large email providers such as Google. 2.1. BibLibre Hosted Mailing Lists. I have given precise technical details of changes which may be made to Laurent Ducos and Fridolin Somers at BibLibre for resolving the issue of OpenDKIM signing and resigning for lists.koha-community.org . 2.2. New Party Needed to Host the Koha General Mailing List. I have also communicated with Rachel Hamilton-Williams about adding DMARC support for the Koha general mailing list. In addition to DKIM support, lists.katipo.co.nz needs a DMARC record in DNS and then activating DMARC in Mailman, and possibly an SPF record for the subdomain lists.katipo.co.nz . Rachel informed me that she would like to hand over hosting of the Koha mailing list for more attentive management than her partner and system administrator, Simon Blake, may be able to provide currently. Without the very simple task of adding DMARC support to the Koha general list, delivery problems are more likely than not for Gmail, Yahoo, etc. subscribers from Feb. A false pass would need at least the pretence of DMARC support. ARC support is required for all mailing lists irrespective of size, for which DMARC might be a workaround as possibly avoiding the need for ARC support. 3. February 2024 Changes for Gmail and Yahoo Mail, etc. At the end of last week, a radio broadcast brought my attention to changes coming in February 2024 which affect everyone in some manner. Everyone includes lists.koha-community.org. Large volume senders have additional requirements. [For large volume senders, there additional requirements beyond those affecting everyone, which might affect people subscribing to the Koha general mailing list if the number of mailing list subscribers is enough and enough people route mail through the popular choice of Gmail even on mobile despite having some other apparent domain of some subscriber wherever that may be hosted initially.] Details about more stringent SPF, DKIM, DMARC, ARC, and one-click unsubscribe link requirements are available from Google. Mailing lists may be able to substitute DMARC support for lack of ARC support when rewriting the From header and thus re-originating and not merely forwarding messages but adding ARC is best addressed second. "Email sender guidelines : Requirements for all senders" - https://support.google.com/mail/answer/81126#zippy=%2Crequirements-for-all-senders . Another part of the same document has the requirements which may affect the Koha general mailing list "Requirements for sending 5,000 or more messages per day" - https://support.google.com/mail/answer/81126#requirements-5k&zippy=%2Crequirements-for-sending-or-more-messages-per-day . The Yahoo guide which I found has fewer details and does not refer to the coming February 2024 policy change: "Sender Best Practices" - https://senders.yahooinc.com/best-practices/ . There is no shortage of secondary sources such as from the support provider Proofpoint, "Google and Yahoo Set a Short Timeline to Meet New DMARC Policy & Setup Requirements. Are You Ready?" - https://www.proofpoint.com/us/blog/email-and-cloud-threats/google-and-yahoo-set-new-email-authentication-requirements . 4. Note on ARC Support. ARC is intended for authenticating the email chain when forwarding messages which is the basic function of mailing lists. Adding DMARC support should make the issue of ARC support for acceptable authentication for mailing lists might be moot because the mailing list is more clearly shown as re-originating email and not merely forwarding. However, the announcements for February 2024 do not state that case with explicit clarity and Gmail adds ARC headers to all mail on their system and people at Google may presume that everyone else should to especially when messages may retain headers showing that the message has been forwarded over the mailing list despite having been re-originated from mailing list with DMARC authentication. While Mailman 3 has functionality for ARC support which was added essentially experimentally a few years ago, the proper place for ARC support is in the MTA not in the mailing list software. When using ARC via Mailman 3 the mail envelope is sealed before DKIM re-signing which is the wrong order and has caused ARC authentication failure. OpenARC, like OpenDKIM, functions in the MTA for Postfix or Sendmail, https://github.com/trusteddomainproject/OpenARC . Mailing lists at https://openarc.org/ . OpenARC is not as fully developed as OpenDKIM and support for some nice things such as multiple sending domains on the system seems to have been abandoned. OpenARC has better support for BSD Unix and Red Hat than Debian based systems but is not as well developed, and although not robustly maintained for Debian based systems, there are openarc packages based on the OpenARC development branch for Debian 9 to 11, https://download.opensuse.org/repositories/home%3A/andreasschulze/ . [Mailman 2 which we are using for the mailing lists does not go past Debian 10 for lack of Python 2. Upgrading to Mailman 3 is non-trivial because of configuration changes, etc. and should not be the most immediate priority.] There is a very brief blog post about using the Andreas Schulze Debian packages, "OpenARC with Postfix on Debian 10 (buster)" / Matthieu - https://weber.fi.eu.org/blog/Informatique/openarc_with_postfix_on_debian_10.html . You can also build your own packages from source as I have. [In current testing of my source build, Postfix has a socket permissions error for OpenARC which may be from a mistake I had made with umask settings long ago on the system which runs my mailserver.] Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 From kohadevel at agogme.com Tue Nov 28 18:54:59 2023 From: kohadevel at agogme.com (Thomas Dukleth) Date: Tue, 28 Nov 2023 17:54:59 -0000 Subject: [Koha-devel] Testing receiving own message back from list Message-ID: Maybe no message copy is sent back if sending to "koha-devel" instead of bare koha-devel at lists.koha-community.org . I have not intentionally changed my procmail recipes this month. However, I have been experimenting with my own mail server settings and testing OpenARC. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 From kohadevel at agogme.com Tue Nov 28 19:03:17 2023 From: kohadevel at agogme.com (Thomas Dukleth) Date: Tue, 28 Nov 2023 18:03:17 -0000 Subject: [Koha-devel] Testing receiving own message back from list In-Reply-To: References: Message-ID: [Reply inline.] On Tue, November 28, 2023 17:54, Thomas Dukleth via Koha-devel wrote: > Maybe no message copy is sent back if sending to "koha-devel" > instead of bare > koha-devel at lists.koha-community.org . My testing confirms, using the bare form koha-devel at lists.koha-community.org works. Sending to "koha-devel" may create a parsing problem for at least the particular version of Mailman installed for lists.koha-community.org unless my procmail recipes are catching the response improperly which would need further testing if it would be worth investigating. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 From kohanews at gmail.com Wed Nov 29 19:05:19 2023 From: kohanews at gmail.com (Koha Newsletter) Date: Wed, 29 Nov 2023 19:05:19 +0100 Subject: [Koha-devel] Koha Community Newsletter: November 2023 Message-ID: The Koha Community Newsletter for November 2023 is here: https://koha-community.org/koha-community-newsletter-november-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 -------------- next part -------------- An HTML attachment was scrubbed... URL: