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

GBSD - Global Bug Squashing Day Tomorrow
by Renvoize, Martin 13 Feb '20

13 Feb '20

Hi All, Just a little reminder we have a global bug squashing day scheduled for tomorrow. I look forward to seeing lots of you on IRC and in the bug mails.. Have a great day :) *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

1 0

Starting/stopping koha-testing-docker
by dcook＠prosentient.com.au 11 Feb '20

11 Feb '20

Hi all, Is there a trick for stopping and starting koha-testing-docker, when using docker-compose, so that you can re-use the same containers? I stop/start containers all the time on other projects, and I swear that Tomas told me how to do it with koha-testing-docker, but koha_koha_1 keeps crashing with "User kohadev-koha already exists" after I try to start it after stopping it, as it's trying to run /kohadevbox/run.sh. Perhaps /kohadevbox/run.sh should have a test where it only tries to do setup if it hasn't already setup the container environment. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 3

hackfest registration
by Paul Poulain 10 Feb '20

10 Feb '20

Hello koha fans, A quick reminder: drop me an email if you plan to come to the hackfest, that will be in March, 23-27, in France, Marseille. Currently, we've people from : Argentina, Canada, Finland, France, Germany, Ireland, Spain, UK, USA. Your country and your contribution is missing !!! As usual, it will be a week of useful work, with a lot of documenting, testing, coding, talking, thinking. And a little bit of eating (cheese) and drinking ( -not only- beer, after work of course) Welcome -- 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 0

Re: [Koha-devel] Starting/stopping koha-testing-docker
by dcook＠prosentient.com.au 07 Feb '20

07 Feb '20

Thanks, Tomas, but the issue isn’t the database. I was probably misleading in my original email. The issue is that the /kohadevbox/run.sh script tries to re-provision the koha_koha_1 server, and it fatally fails to do so. Before doing the setup, it should do a test to see if it needs to do the setup. But the --force-recreate option is practical enough for now. If it bothers me enough going forward, I’ll do a patch and send in a pull request for the run.sh script It’s probably not a bad thing to re-create the containers each time just to have a clean code and configuration environment, but it makes long-term work more difficult. Recently, I created a jboss/keycloak container, and I just start/stop that container whenever I need a Keycloak server. Same with a lot of containers I use. Of course, that means it’s easier for untracked localizations to sneak in and then you destroy the container and create a new one and it’s radically different to what you’re using but *shrug*. Anyway, good to know that we can’t stop/start koha-testing-docker. I thought I was missing something, but it just looks like it’s not possible currently. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Tomas Cohen Arazi <tomascohen(a)theke.io> Sent: Friday, 7 February 2020 10:55 AM To: David Cook <dcook(a)prosentient.com.au> Cc: Agustin Moyano <agustinmoyano(a)theke.io>; koha-devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Starting/stopping koha-testing-docker There's one alias for persistent db. That might suit you El jue., 6 de febrero de 2020 20:45, <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió: Hi Agustin, Thanks for your email. However, I think that perhaps you misunderstand me. I’m not trying to re-create the containers; I’m trying to re-use/re-start the existing containers. Your first suggestion will recreate the containers by destroying the old ones. That means I can’t re-use them. Your second suggestion requires the container to be running, but my use case is starting a stopped container, which has been stopped either manually, by a system reboot, or whatever. I suppose I could modify the docker-compose.yml file to have a custom command, and just manually run /kohadevbox/run.sh when I initially create the container… that might be the shortest path to what I’m trying to do. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Agustin Moyano <agustinmoyano(a)theke.io <mailto:agustinmoyano@theke.io> > Sent: Friday, 7 February 2020 1:12 AM To: dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> Cc: koha-devel <koha-devel(a)lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> >; tomascohen(a)theke.io <mailto:tomascohen@theke.io> Subject: Re: [Koha-devel] Starting/stopping koha-testing-docker Hi David, you have 2 ways. First if you started koha-testing-docker using the script alias "ku", the script has the "--force-recreate" flag when it runs.. that means if you kill it, and start it again with ku you wont have any problems. The other way is to not kill the container, but simply do "reset_all" inside docker container... that is basically the same in the way that it will cleanup your database and install everything from scratch. Hope it helps! On Thu, Feb 6, 2020 at 2:16 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, Is there a trick for stopping and starting koha-testing-docker, when using docker-compose, so that you can re-use the same containers? I stop/start containers all the time on other projects, and I swear that Tomas told me how to do it with koha-testing-docker, but koha_koha_1 keeps crashing with “User kohadev-koha already exists” after I try to start it after stopping it, as it’s trying to run /kohadevbox/run.sh. Perhaps /kohadevbox/run.sh should have a test where it only tries to do setup if it hasn’t already setup the container environment. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

1 0

Koha mirror on gitlab.com not updated ?
by Julian Maurice 06 Feb '20

06 Feb '20

Hi all, It seems the mirror on gitlab is not updated anymore. The last commit on master is 604c7b81 Bug 22816: OPAC detail holdings table should now look a bit better which has been committed in May 2019 Does anyone know why ? -- Julian Maurice BibLibre

6 11

Bug 18936 - Circulation Rules Ratification
by Renvoize, Martin 05 Feb '20

05 Feb '20

Hi All, I just wanted to let you all know that I'll be pushing bug 18936 to the master branch this morning. It's the largest to date of the refactoring bugs and will affect any/all bugs related to the circulation rules handling. It's been thoroughly tested and QA'd, but as a large piece I'm sure there will be a few pain points still buried, so keep an eye out and report any bugs you find. Good luck with any rebases that may be required after this and my apologies, but the end result should give us a much cleaner foundation for circ related enhancements and cleanup in the future. Many thanks to those who have spent many hours coding, testing, refining and qaing this piece, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

5 7

Trouble in setting up kohadevbox on Win10 prof
by Indranil Das Gupta 04 Feb '20

04 Feb '20

Hi all, I'm trying to setup kohadevbox on a Windows 10 prof laptop. I'm going after stretch64 Things I've done so far: 1. I had to switch the distribution to https://app.vagrantup.com/digital-port/boxes/debian-stretch64 because otherwise I was hitting the missing linux-headers for vbox guest additions. 2. Ran SMB=1 SKIP_WEBINSTALLER=1 CREATE_ADMIN_USER=1 LOCAL_ANSIBLE=1 SYNC_REPO="/home/vagrant/kohaclone" vagrant up 3. I've the VM created, can ssh into it both as `vagrant ssh` as well as via putty 4. But no cheese when i try to access http://localhost:8081 either inside the VM or from my host box 5. the .deb installation did go through, because there is /usr/share/koha and the koha-* commands are accessible e.g. koha-list. koha-passwd so package got installed. 6. /home/vagrant/kohaclone is empty and that I guess is the root of my problems because the installation has gotten gitified and there is nothing there at the moment. 7. I'm now manually doing a `git clone http://git.koha-community.org/koha.git kohaclone` in /home/vagrant to see if that makes a difference. My question: kohadevbox README.md says - "A clone of the official Koha Git repo, or a NFS-mounted git repository from your host machine." So what am I missing here? Cluesticks / brickbats welcome... and expected :-) thanks -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

6 9

Koha Newsletter January 2020: addendum
by kohanews 03 Feb '20

03 Feb '20

I overlooked a really great submission to the Jan. 2020 newsletter. Must be the lack of caffeine. ( Sorry about that, Marcel! ) Please take a look at the newly added entry in the community announcements section of the newsletter: https://koha-community.org/koha-community-newsletter-january-2020/#announce *Marcel de Rooy* blogs about the history and use of Koha at the Rijksmuseum <https://theartofinformationblog.wordpress.com/2020/01/08/3725/> over the last 10 years. Though rare, this isn't the first time I've overlooked tidbits and article submissions over the past few years and I've decided to start announcing my blunders while calling attention to the articles in an email addendum so they get the attention they deserve. Thank you! Chad -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Koha Community Newsletter: January 2020
by kohanews 01 Feb '20

01 Feb '20

The Koha Community Newsletter for January 2020 is here: https://koha-community.org/koha-community-newsletter-january-2020/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Elasticsearch recent works at BibLibre
by Claire Hernandez 31 Jan '20

31 Jan '20

Hi, This week, some devs work together to move forward concretely on Elasticsearch issues encountered. You will find below a focus on some points (some are at poc state today) written by Alex and Jajm from BibLibre. We would be glad to discuss these topics at hackfest in march and having user feedbacks too :) #1 Proof of concept for language analyzers bug 21357 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21357#c32 It's an attempt at having a default ES configuration with stemming, elision, etc. that works with multi-languages catalogs You can read the comments and patch for more information. #2 Compatibilites for tomorrow Compatibility with latest version of Search::Elasticsearch - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24552 Compatibility with Elasticsearch 7.x : Problem: Search::Elasticsearch is not yet compatible with ES 7.x, so we are stuck with ES 6.x (unless we use something else...) #3 Querying Elasticsearch in a better way POC query_string => boolean query https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24555 This POC is about replacing the use of full text queries (query_string) with Boolean queries for biblio search Advantage: => No search craches with special character ( "!", ")" etc...) => Separate query context and filter context: - Search scores are not altered by facets, - Ability to use range filter (i.e for publication date facet) Regards, Claire.

2 1