September 2022 - Koha - lists.katipo.co.nz

Re: [Koha] How to copy patron permissions?
by BRANNON, CHRISTOPHER 22 Jan '24

22 Jan '24

Michael, I've had some jQuery in the Koha library for quite a while. You should take a look at https://wiki.koha-community.org/wiki/JQuery_Library#Add_clear_and_preset_pe… There are 3 versions of this for different versions of Koha, but this latest one includes a clear permissions button, a couple of preset permission buttons, and a copy permissions button. Please check it out. We also did a video tutorial on this enhancement in season one of The Terrific Every-Other-Thursday Training Videos. You can find that here: https://youtu.be/M6aQITCJY0U. ___________________________ Christopher Brannon IT Coordinator 702 E Front Ave Coeur d'Alene, ID 83814 (208)769-2315 Ext. 456 cbrannon(a)cdalibrary.org www.cdalibrary.org Keep tabs on us at: Date: Tue, 26 Apr 2022 10:39:58 +0200 From: Michael Kuhn <mik(a)adminkuhn.ch> To: Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] How to copy patron permissions? Message-ID: <abc69231-a587-77d5-01d2-7f98e5b16174(a)adminkuhn.ch> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Is it possible to copy the permissions of another patron when creating a new one? I always thought this would happen when copying/duplicating an existing patron. But when I actually tried it today the permissions were not there with the new patron and I had to set them manually. Best wishes: Michael Kuhn

4 3

Koha 21.11.09 released
by Arthur 11 May '23

11 May '23

The Koha community is pleased to announce the release of version 21.11.09. For full release notes, please visit https://koha-community.org/koha-version-21-11-09-released/ <https://koha-community.org/koha-21-11-09-released/> Thanks! 🚀

3 4

Analytical cataloguing causing a searching warning
by Aleisha Amohia 31 Mar '23

31 Mar '23

Hi Koha community! We're having some trouble with analytical cataloguing - linking host and child records. We have EasyAnalyticalRecords enabled, and UseControlNumber disabled. When we link the host item using the barcode, the detail page for the child item shows this warning above the title: "There was an error searching for analytic records, please see the logs for details." The Plack Intranet error log shows the following errors: [2022/02/15 13:59:09] [WARN] CCL parsing error (10014) Embedded truncation not supported ZOOM for query: Host-item=(BIBLIO_TITLE /) at /usr/share/koha/lib/C4/Search.pm line 241. [2022/02/15 13:59:09] [WARN] Warning from simple_search_compat: CCL parsing error (10014) Embedded truncation not supported ZOOM at /usr/share/koha/intranet/cgi-bin/catalogue/detail.pl line 152. I have tried also manually linking the host item by cataloguing directly into the 773 of the child item, the searching warning still shows. I have also tried enabling UseControlNumber and putting the 001 of the host record into 773$w of the child item, which has usually worked (the warning disappears), however this method does not work for us because the library doesn't usually fill in the 001. We'd rather keep UseControlNumber disabled. Is this a problem that other libraries have other seen? Have you been able to solve it while keeping EasyAnalyticalRecords enabled and UseControlNumber disabled? Would appreciate any help. Thanks all! -- Aleisha Amohia (she/her) Koha Developer Catalyst IT - Expert Open Source Solutions www.catalyst.net.nz CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

4 5

Sorry, your Google login failed
by tony.h 18 Jan '23

18 Jan '23

Greetings, I'm having trouble getting the Google login to work since upgrading/rebuilding Koha (we rebuilt the VPS and followed the install guide: https://wiki.koha-community.org/wiki/Debian) *The problem:* 1) I can log in through my local account, no problem. 2) I then try to login through my Google account 3) After pressing allow from the accounts.google.com site, a message is displayed: /Sorry, your Google login failed. .../ The full message is below. "Log in to your account Google login Sorry, your Google login failed. The email address you are trying to use is not associated with a borrower at this library. Please note that the Google login will only work if you are using the e-mail address registered with this library. If you want to, you can try to log in using a different account Log in with Google If you do not have a Google account, but do have a local account, you can still log in:" There are no errors in the Apache log files. *Configuration* Since we had troubles, I'm following the testing guide to configure the OAuth login: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10988#c68 I removed the Google OAuth entries: DELETE FROM systempreferences WHERE variable LIKE 'GoogleO%'; I then ran the upgrade schema tool, as I did when I imported the db: sudo koha-upgrade-schema keiin_lib I added values back in admin panel (Home › Administration › System preferences > Google OpenID Connect I confirmed the 4 values are displayed in the MySQL DB: SELECT * FROM systempreferences WHERE variable LIKE 'GoogleO%'; Any thoughts? Tony -- View this message in context: http://koha.1045719.n5.nabble.com/Sorry-your-Google-login-failed-tp5895227.… Sent from the Koha-general mailing list archive at Nabble.com.

5 5

Koha releases are available 🎁
by Mason James 16 Jan '23

16 Jan '23

kia ora community, the latest Koha packages and tarballs are ready release notes are here... https://koha-community.org/koha-21-11-03-released https://koha-community.org/koha-21-05-11-released https://koha-community.org/koha-20-11-15-released https://koha-community.org/koha-19-11-26-released cheers, Mason

2 2

Patron search not working after upgrade to version 22
by Evan Stewart 06 Dec '22

06 Dec '22

Hello, I recently upgraded my Koka 21 to 22. Everything seemed to be working fine until I tried searching for patrons. Using the intranet portal to search for patrons provides zero results. I see my patrons in the borrowers table, but the GUI won't display them. It's like the search function sees no results. I upgraded to version 22.05.02, but the same problem still occurs. I'm using Raspberry Pi OS (Buster). I can add a new patron, but even the new patron does not show in the search results. Is there a way to refresh the indexer that handles patron searching? Any other suggestions? -Evan Stewart Africa's Hope, USA

5 15

Request for Libraries using Koha to participate in the 2021 Library Automation Perceptions survey
by Marshall Breeding 03 Nov '22

03 Nov '22

To all libraries using Koha: I'm collecting data for the 2021 edition of the International Library Automation Perceptions survey. This survey, conducted annually since 2007, provides an opportunity for libraries to register their perceptions of the strategic automation products they use, organizations that provide these products, and the quality of support delivered. The survey also probes at considerations for migrating to new systems and the level of interest in open source products. As open source software supported both by the general community and by a variety of different service organizations, some special considerations apply to Koha. In the libraries.org directory, Koha is represented by a combination of the name Koha and the primary support organization involved. (For example Koha - Catalyst IT, Koha -- ByWater Solutions). Libraries relying entirely on community support or internal resources are represented as Koha - Independent. If there are any special support arrangements not covered by these conventions, just mention that in the comments area of the survey. In this way the survey will be able to reflect both the functionality of the Koha software and the quality of support provided. This model of representing libraries using Koha isn't perfect, but is a pragmatic approach that aggregates all users of Koha while also segregating the different support scenarios. Participation in this survey will help amplify the visibility of Koha among those interested in library automation. While the numeric rating scales support the statistical results of the study, it's the comments offered that provide the most insight into the current state of library automation satisfaction. Comments will be published in the survey results, redacted to conceal text that might identify the individual or organization responding. The raw data for the survey will not be shared, but reports are available that provide a variety of ways to view results. Please help your fellow librarians who might be in the process of evaluating library automation options by responding to the survey. Any information regarding vendor performance and product quality can be helpful when making strategic decisions regarding automation alternatives. A large number of responses strengthen the impact of the survey and the subsequent report. If you have responded in previous years, please respond again this year to help identify any trends regarding improvement or worsening of the products or support services. For more information about the survey, for instructions on how to participate, and to see results of previous year's survey reports, see: https://librarytechnology.org/perceptions/2021/invite/ I hope that all libraries using Koha will respond. Feel free to forward this request to any other library-related list. You can view the report summarizing the results of last year's survey, including data from all previous editions, here: https://librarytechnology.org/perceptions/2020/ Please let me know if there are any questions regarding the survey. Marshall Breeding Editor, Library Technology Guides www.librarytechnology.org Marshall.breeding(a)librarytechnology.org twitter.com/mbreeding

1 1

French (fr-FR) Translator problem
by amandeep.kapila＠aol.in 17 Oct '22

17 Oct '22

Dear all, I am adding some language to my Koha OPAC and Staff Client. I can add the languages, as desired, with koha-translate package service but unfortunately its not working as expected for French (fr-FR). When I enable French on either of the interfaces the search results display no bibliographic/metadata for the records, only blank spaces, although it returns exact number of results. I have tried with both Zebra and Elasticsearch, same result. For other languages (Spanish, Arabic etc.) everything shows OK. Even the Canadian version of French (fr-CA) is also working. Its happening both in OPAC and Staff Client. The plack opac error logs display message like below, [2022/09/22 11:00:56] [WARN] Use of uninitialized value $field in substitution (s///) at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/QueryBuilder.pm line 1108.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:325: parser error : Entity 'nbsp' not defined <xsl:with-param name="langLabel">Langue : </xsl:with-param> ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:376: parser error : Entity 'nbsp' not defined Collection : </sp ^compilation error: file /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slim2OPACResults.xsl element importxsl:import : unable to load /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl at /usr/share/koha/lib/Koha/XSLT/Base.pm line 342.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:325: parser error : Entity 'nbsp' not defined <xsl:with-param name="langLabel">Langue : </xsl:with-param> ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:376: parser error : Entity 'nbsp' not defined Collection : </sp ^compilation error: file /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slim2OPACResults.xsl element importxsl:import : unable to load /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl at /usr/share/koha/lib/Koha/XSLT/Base.pm line 342.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:325: parser error : Entity 'nbsp' not defined <xsl:with-param name="langLabel">Langue : </xsl:with-param> ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:376: parser error : Entity 'nbsp' not defined Collection : </sp ^compilation error: file /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slim2OPACResults.xsl element importxsl:import : unable to load /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl at /usr/share/koha/lib/Koha/XSLT/Base.pm line 342.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:325: parser error : Entity 'nbsp' not defined <xsl:with-param name="langLabel">Langue : </xsl:with-param> ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:376: parser error : Entity 'nbsp' not defined Collection : </sp ^compilation error: file /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slim2OPACResults.xsl element importxsl:import : unable to load /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl at /usr/share/koha/lib/Koha/XSLT/Base.pm line 342.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:325: parser error : Entity 'nbsp' not defined <xsl:with-param name="langLabel">Langue : </xsl:with-param> ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:376: parser error : Entity 'nbsp' not defined Collection : </sp ^compilation error: file /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slim2OPACResults.xsl element importxsl:import : unable to load /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl at /usr/share/koha/lib/Koha/XSLT/Base.pm line 342.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:325: parser error : Entity 'nbsp' not defined <xsl:with-param name="langLabel">Langue : </xsl:with-param> ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:376: parser error : Entity 'nbsp' not defined Collection : </sp ^compilation error: file /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slim2OPACResults.xsl element importxsl:import : unable to load /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl at /usr/share/koha/lib/Koha/XSLT/Base.pm line 342.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:325: parser error : Entity 'nbsp' not defined <xsl:with-param name="langLabel">Langue : </xsl:with-param> ^/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:376: parser error : Entity 'nbsp' not defined Collection : </sp ^compilation error: file /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slim2OPACResults.xsl element importxsl:import : unable to load /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl at /usr/share/koha/lib/Koha/XSLT/Base.pm line 342.[2022/09/22 11:00:57] [WARN] XSLT::Base: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/fr-FR/xslt/MARC21slimUtils.xsl:269: parser error : Entity 'nbsp' not defined Ãditeur : ^....................................................................................................................................................................................................... Seems like some xslt parser issue. Kindly help,

3 2

Matching authority records with tag 001
by Giacomo Visini 10 Oct '22

10 Oct '22

Hello colleague's, We are trying to import a bunch of authority records with updated fields, but I can't find the right way to match them with existing authority records. The only tag which is workable in our case should be 001. We have followed the manual meticulously, but it just doesn't work. Matching rules used below: Matching rule code: CNUMBER Description: 001 Match threshold: 100 1. Search index: Control-number 2. Score: 101 1. Tag: 001 2. Subfields: [blank] 3. Offset: 0 4. Length: 0 5. Normalization rule: [none] Looking at past messages, we've tried changing the match threshold to '1000' and the score to '1000'. Also, since this matching rule uses a control field, we've tried changing the length to '5' (correct in our case), but to no avail. We've even tried changing the subfield to 'a' and '@', but this doesn't seem to change anything. Anyone who encountered the same problem, but found a solution? Any suggestions? We are using 21.11.06 with Zebra Thanks in advance. Giacomo Visini I Library assistant DIVA, Antwerp Home of Diamonds Visiting adress library (temporary): Kaasstraat 13, B-2000 Antwerpen Postal adress: Kaasstraat 13, B-2000 Antwerpen T + 32 3 360 52 41 M + 32 485 66 49 98 giacomo.visini(a)divaantwerp.be<mailto:giacomo.visini@divaantwerp.be> www.divaantwerp.be<http://www.divaantwerp.be/> Follow us on Facebook<https://www.facebook.com/diva.antwerp> I Linkedin<https://www.linkedin.com/company/438781> I Instagram<https://www.instagram.com/divaantwerp/>

5 9

Re: [Koha] Problem upgrading RabbitMQ / Erlang
by Isabel Pineda 03 Oct '22

03 Oct '22

Hi Mason. The output is: rabbitmq-server: Installed: 3.10.7-1 Candidate: 3.11.0-1 Version table: 3.11.0-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.10.8-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages *** 3.10.7-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 100 /var/lib/dpkg/status 3.10.6-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.10.5-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.10.4-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.10.2-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.10.1-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.10.0-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.23-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.22-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.21-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.20-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.19-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.18-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.17-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.9.13-1 500 500 http://asi-fs-d.contabo.net/ubuntu jammy/main amd64 Packages 500 http://asi-fs-d.contabo.net/ubuntu jammy/main i386 Packages 3.8.35-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.8.34-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.8.33-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.8.32-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages 3.8.31-1 500 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main a md64 Packages 500 https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu jammy/main i 386 Packages erlang-base: Installed: 1:24.2.1+dfsg-1 Candidate: 1:24.2.1+dfsg-1 Version table: *** 1:24.2.1+dfsg-1 500 500 http://asi-fs-d.contabo.net/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Thank you Isabel -----Mensaje original----- De: Mason James <mtj(a)kohaaloha.com> Enviado el: lunes, 26 de septiembre de 2022 23:00 Para: Isabel Pineda <isabel.pineda(a)ds.edu.sv>; koha(a)lists.katipo.co.nz Asunto: Re: [Koha] Problem upgrading RabbitMQ / Erlang hi Isabel can you paste the output of the following command.... $ apt policy rabbitmq-server erlang-base rabbitmq-server: Installed: 3.9.13-1 Candidate: 3.9.13-1 Version table: *** 3.9.13-1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status erlang-base: Installed: 1:24.2.1+dfsg-1 Candidate: 1:24.2.1+dfsg-1 Version table: *** 1:24.2.1+dfsg-1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status On 27/09/22 2:47 am, Isabel Pineda wrote: > Hi. > > I am runing Koha on Ubuntu 22.04 and I have got the problem that RabbitMQ cannot be upgraded because of unmet dependencies (Erlang). It seems that I have got an older version of Erlang (1.24) and Rabbitmq requires version 1.25. The problem is that I cannot update Erlang. The error message is "The repository 'http://binaries.erlang-solutions.com/debian jammy Release' does not have a release file". > > Have you got a recommendation? > > Thank you > Isabel Pineda > _______________________________________________ > > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

2 6