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

22.11.12 having package dependency problems?
by David Cook 25 Jan '24

25 Jan '24

I help out a few libraries running 22.11 straight from the community, and two libraries lately have had Koha go down during automatic upgrades to 22.11.12-1. koha-common mostly installs but fails to complete due to unmet dependencies: apt install koha-common -s Reading package lists... Done Building dependency tree... Done Reading state information... Done koha-common is already the newest version (22.11.12-1). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: koha-common : Depends: koha-l10n but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). You can remedy this by running apt-get install koha-l10n, but I'm curious why this is happening. I imagine it must be happening to more libraries around the world as well. Maybe when the koha-common upgrade ran the koha-l10n package wasn't available? Has anyone else bumped into this? I didn't realize that we were backporting koha-l10n to other releases than 23.11, so it hasn't been on my radar until now. 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

4 4

Translation
by Marcel de Rooy 25 Jan '24

25 Jan '24

Hi, I came across this link on opac-detail in our Dutch OPAC: <a href="/cgi-bin/koha/opac-search.pl?q=an:%22152985%22" class="co-auteur">Dalbajewa, Birgit [contributor]</a> As you may see, various class names, attribute names etc. are being translated (while they should not have been translated). In the PO file it just says for instance msgstr "contributor", so things get translated. In the above co-auteur and Persoon should not have been there. Anyone have an idea how we could prevent such entries from coming into the PO file at the first place? Thanks, Marcel

2 3

Reminder: Development IRC meeting 24 January 2024
by Fischer, Katrin 22 Jan '24

22 Jan '24

Hi all, just a quick reminder: we have a development meeting scheduled for this Wednesday: Agenda: https://wiki.koha-community.org/wiki/Development_IRC_meeting_24_January_2024 Time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IR C+Meeting <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I RC+Meeting&iso=20240124T1300> &iso=20240124T1300 Road map 24.05: . If you are a project lead, please prepare an update on your projects' status . You can also add the roadmap_24_05 now on Bugzilla to highlight any bugs/patches See you there! Katrin

1 0

Hackfest in Marseille in 2024
by Paul Poulain 17 Jan '24

17 Jan '24

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

1 1

Building unittests
by Wagner, Alexander 16 Jan '24

16 Jan '24

Hi! Currently I work on the migration of our library system to Koha and AFAIS we would like to get bug 29930 into the code. Playing through the test description showed already that the stuff works, so with a little help I already learned the sign-off procedure. Now, to get the stuff into Koha this module change requires a unit test. Thus I took the plunge into t/db_dependent/Auth_with_ldap.t as recommended and tried to understand what's going on there and how to handle some external dependency (the ldap server that does not exist out there). I also think that I found where I'd have to add the necessary checks for the new code, however I get stuck with actually implementing it. As far as I understand the code the whole ldap is done via a mockup. Similarly, the borrower is done as a mockup. IOW if I don't miss-understand the code there is no change to kohas internal data and larger parts of the code including the relevant one for #29930 is actually sort of cut short. So I don't really understand how to hook in the new test in such a way, that it actually tests the functionality. I may add that unittests in perl are pretty new to me. The last years I spent mainly doing some small python stuff and I am not a real developer either. Could someone with more knowledge of Kohas internal probably give me a helping hand there? -- Kind regards, Alexander Wagner Deutsches Elektronen-Synchrotron DESY Library and Documentation Building 01d Room OG1.444 Notkestr. 85 22607 Hamburg phone: +49-40-8998-1758 e-mail: alexander.wagner(a)desy.de

1 0

Phishing attempts using dev names
by Waylon Robertson 13 Jan '24

13 Jan '24

I received an email from Chris Cormack e_2020100200a(a)uncp.edu.pe , attempting to get me to look at pictures, with a link to go to them. Seems spammers are now mining this list?

2 2

Call for news - Newsletter January 2024
by Koha Newsletter 12 Jan '24

12 Jan '24

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

1 0

Plugin Development
by Charles Athey 08 Jan '24

08 Jan '24

This is my first post to this list. I am a retired computer scientist with development and system administration experience. I used PERL a lot about 25 years ago but haven’t done much with it since until now. I recently deployed Koha at the Sacramento FamilySearch Center where I volunteer. The Sac FSC is an archival library, meaning we don’t allow books to be checked out. We have and are digitizing our collection of copy protected books. Public domain books are being digitized and the physical book and the digital copy are sent to the FamilySearch organization to be added to their system. They are also using Koha but our Center’s instance is separate. We are making the PDFs of copy protected books available on-site ONLY, no internet access at this point, and are storing the books for preservation and space reasons. We had a need to update the MARC 856 data fields to reflect the location of the PDFs of our books. I looked at the plugin AddURLsToMarc by Tomás Cohen Arazi. It didn’t have quite enough capability as we wanted to update a few more of the subfields. I decided to make a plugin based on AddURLsToMarc that I made more general and added functionality to allow arbitrary MARC data fields to be added or deleted. It is working very well. So, the questions are - What is the process for sharing such plugins with the Koha community, are there conventions that are used, etc.? - Is this the right forum to ask these questions? - Can users running other version help testing the plugin? I have only tested it on 23.05.05 on Ubuntu 22.04 LTS. Our plugin is titled UpdateMarcField and I have put it on GitHub in my koha-plugin-updatemarcfield <https://github.com/athey3/koha-plugin-updatemarcfield> repository. I have used local Git extensively for personal code but have only accessed GitHub not posted items on it prior to this as most things I have worked on have been proprietary. Any and all advise is appreciated. Chuck Athey Asst. Directory for Technology Sacramento FamilySearch Center athey3(a)gmail.com

2 1

TT notice question
by Stephen Graham 05 Jan '24

05 Jan '24

Hi All - not specifically Koha I guess, but maybe someone can explain why this happens. I had some TT in an email notice like: [% IF illrequests.branchcode == "CL" %] College Lane LRC [% ELSIF illrequests.branchcode == "DH" %] De Havilland LRC [% ELSE %] <<illrequests.branchcode>> [% END %] Every time I generated the email it printed CL, which is the value of llrequests.branchcode. I just could not get the first condition to work no matter what I did - it never printed College Lane LRC always CL. However, I changed it to: [% SET localbranch = illrequests.branchcode %] [% IF illrequests.branchcode == localbranch %] College Lane LRC [% ELSIF illrequests.branchcode == localbranch %] De Havilland LRC [% ELSE %] <<illrequests.branchcode>> [% END %] , and this works if I set the illrequests.branchcode to a local variable and then check this. Not sure why I have to do this? The example I have seen on the wiki look like I should be able to test a variable against a string using ==. Just couldn't get it to work. Any ideas? Stephen -------------------------------------- Stephen Graham Library Technology Consultant Library and Computing Services University of Hertfordshire Hatfield, Hertfordshire, AL10 9AB Email: s.graham4(a)herts.ac.uk<mailto:s.graham4@herts.ac.uk> Website: herts.ac.uk

2 3

REMINDER: Development IRC meeting 3 January 2024 / Roadmap deadline
by Fischer, Katrin 02 Jan '24

02 Jan '24

Hi all, we have a development IRC meeting scheduled for tomorrow: <https://wiki.koha-community.org/wiki/Development_IRC_meeting_3_January_2024 > https://wiki.koha-community.org/wiki/Development_IRC_meeting_3_January_2024 Time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Development+M eeting <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Development+ Meeting&iso=20231213T1300> &iso=20231213T1300 We will take time again to discuss roadmap project proposals and next steps: https://wiki.koha-community.org/wiki/Road_map_24.05 The deadline for completing the proposed project entries has been extended to 12 January 2024. Please make sure to add any missing information! See you tomorrow! Katrin

1 1