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

Testing party on Thursday 17 December at Lyon 3 University
by BOUIS Sonia 15 Dec '15

15 Dec '15

Hi, Just before breaking for Christmas holidays, we are organising a testing party at Lyon 3 University. We have selected several bugzilla tickets as you can see on this Trello : https://trello.com/b/PcSNIggo/journee-test-lyon-3-17-12-2015 If you want to propose us others tickets with patch easy to test on a sandbox or to add a comment, don't hesitate. (Trello is public, but I think I have to add you if you want to comment or change something) Cheers, Sonia BOUIS Responsable du Système intégré de gestion des bibliothèques bIBLIOTHÈQUES UNIVERSITAIRES Université Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 - 69355 Lyon Cedex 08 ligne directe : +33 (0)4 78 78 79 03 | http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> L'Université Jean Moulin est membre fondateur de l'Université de Lyon

2 1

HTTP::OAI version issues
by David Cook 14 Dec '15

14 Dec '15

Hi all: Frédéric, Jonathan, Héctor, and I have chatted a bit on http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14939 about the fact that HTTP::OAI version 4.03 is fundamentally broken. While this might not have much of an impact now, since version 3.27 is used in all stable and older versions of Debian (https://packages.debian.org/search?keywords=libhttp-oai-perl <https://packages.debian.org/search?keywords=libhttp-oai-perl&searchon=names &suite=all&section=all> &searchon=names&suite=all&section=all), version 4.03 is used in one stable version of Ubuntu, and is scheduled to be part of the next LTS release in April 2016 (http://packages.ubuntu.com/search?keywords=libhttp-oai-perl <http://packages.ubuntu.com/search?keywords=libhttp-oai-perl&searchon=names& suite=all&section=all> &searchon=names&suite=all&section=all and https://wiki.ubuntu.com/Releases) If anyone is using or will use those releases, theyre probably going to find it impossible to use any OAI-PMH functionality in Koha. I dont foresee this being a problem in Debian while 4.03 is in testing and unstable, I suspect the Debian folk will either patch the problems or use 3.27 in the next stable release. I havent tested Ubuntu yet to see whether or not its been patched. The version in Debian testing has had some alterations, although I think Jonathan was using the 4.03-1 version in Debian testing and found problems. Anyway, Im just wondering what we should do about this. Frédéric is in the process of contacting the module maintainer, but Im predicting that the maintainer wont respond. Can we make koha-common depend on the older version of libhttp-oai-perl? Should we package our own version of the module? Should we double-check Ubuntu and report bugs there with the hope that they downgrade to the functional version of libhttp-oai-perl? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

3 3

Re: [Koha-devel] DateUtils / Zebra
by Paul A 14 Dec '15

14 Dec '15

At 10:41 PM 12/13/2015 -0300, Tomas Cohen Arazi wrote: >You are running an antique version of Koha. And it used to use >experimental features from Perl (that were removed later). It doesn't hurt >to have those warnings anyway. Tomas -- tnx for the reply. Do you remember if this was a change to <http://rebuild_zebra.pl>rebuild_zebra.pl or to DateUtils.pm? As I said below, I couldn't find any documentation on the subject -- and I'd like to look into getting rid of the warnings. Thanks -- Paul >2015-12-13 20:09 GMT-03:00 Paul A ><<mailto:paul.a@navalmarinearchive.com>paul.a(a)navalmarinearchive.com>: >(I found one email, no response, from 21 May 2014 on this subject; can't >find anything 'DateUtils' with either 'Zebra' or 'catalog' in ><http://bugs.koha-community.org>bugs.koha-community.org.) >It's extremely rare nowadays that we do a complete re-index on the >production servers, but I did one today after a direct (naughty me) tweak >to MySQL (frameworks/itemtypes) to avoid a lengthy sandbox<==>production >to and fro. I got the following: >koha_account@my_production:/usr/share/koha$ >./bin/migration_tools/<http://rebuild_zebra.pl>rebuild_zebra.pl -b -r -v -x >given is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 114. >when is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 115. >when is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 118. >when is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 121. >Smartmatch is experimental at /usr/share/koha/lib/C4/Search.pm line 492. >Useless use of '\'; doesn't escape metacharacter '(' at >/usr/share/koha/lib/C4/AuthoritiesMarc.pm line 917. >Just thought I'd ask if anyone has any thoughts on this as I'm fairly sure >I've never seen it before -- note, it doesn't *appear* to hurt anything. >Tnx and regards -- Paul >_______________________________________________ >Koha-devel mailing list ><mailto:Koha-devel@lists.koha-community.org>Koha-devel(a)lists.koha-community.org > >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >website : <http://www.koha-community.org/>http://www.koha-community.org/ >git : <http://git.koha-community.org/>http://git.koha-community.org/ >bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/ > > > > >-- >TomÃ¡s Cohen Arazi >Theke Solutions (<http://theke.io/>http://theke.io) >â +54 9351 3513384 >GPG:Â B76C 6E7C 2D80 551A C765 Â E225 0A27 2EA1 B2F3 C15F --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

3 2

Does anybody have customized error pages that could be affected by Bug 15288?
by Marc Véron 14 Dec '15

14 Dec '15

Hi all The Koha error pages have some translatability issues. That's why I streamlined and de-duplicated the code in "Bug 15288 - Error pages: Code duplication removal and better translatability". http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15288 There are QA concerns about installations where the error pages might have been customized. Does anybody have objections regarding this bug? Thanks for any comments. Marc Véron

1 0

DateUtils / Zebra
by Paul A 13 Dec '15

13 Dec '15

(I found one email, no response, from 21 May 2014 on this subject; can't find anything 'DateUtils' with either 'Zebra' or 'catalog' in bugs.koha-community.org.) It's extremely rare nowadays that we do a complete re-index on the production servers, but I did one today after a direct (naughty me) tweak to MySQL (frameworks/itemtypes) to avoid a lengthy sandbox<==>production to and fro. I got the following: koha_account@my_production:/usr/share/koha$ ./bin/migration_tools/rebuild_zebra.pl -b -r -v -x given is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 114. when is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 115. when is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 118. when is experimental at /usr/share/koha/lib/Koha/DateUtils.pm line 121. Smartmatch is experimental at /usr/share/koha/lib/C4/Search.pm line 492. Useless use of '\'; doesn't escape metacharacter '(' at /usr/share/koha/lib/C4/AuthoritiesMarc.pm line 917. Just thought I'd ask if anyone has any thoughts on this as I'm fairly sure I've never seen it before -- note, it doesn't *appear* to hurt anything. Tnx and regards -- Paul

2 1

Form input handling
by Martin Persson 13 Dec '15

13 Dec '15

Hello, I was just wondering how new code should handle form input processing? Is there a recommended CPAN module that I can use, or should I simply perform validation and transformations by hand? Best wishes, Martin Persson

1 0

Updates for 3.24
by Brendan Gallagher 11 Dec '15

11 Dec '15

Hi All - I just got back from Asia and it was a lovely trip. While I was gone, Kyle pushed some bugs for us and only concentrated on bugs without string changes. This next week coming up - I will begin to concentrate on pushing bugs with strings changes, and that still leaves us at a target for pushing enhancements starting in January. Personal note I will be working different hours than my normal hours (traveling a little bit but all within US). Thanks all, Brendan

1 0

Re: [Koha-devel] [Koha] Problem with BarcodeFallbackSearch
by Paul A 11 Dec '15

11 Dec '15

At 03:56 PM 12/10/2015 -0500, Galen Charlton wrote: >Hi, > >On Wed, Dec 9, 2015 at 6:46 PM, Paul A <paul.a(a)navalmarinearchive.com> wrote: > > Enhancements, improvements and new features: a good starting point is the > > user list, (IRC?) and possibly the dev list. If there is consensus, this > > should be filed at ??? <enhancements.koha-community.org> (similar to > > bugzilla) > >It is hardly unusual for a "bugs" database to be used to record both >reports of defects with the software and requests for enhancements. >The Koha project has done so for years; procedures for doing are >documented in the project bug reporting guidelines [1]. Hi Galen -- thanks for the reply. I agree that overlap is unavoidable and that there are many reasons to "combine" rather than have two databases, which was why I tried to differentiate between "existing code has a problem" and "future code could improve Koha." My reflections on the matter were prompted by my inability (perhaps I'm missing something?) in Bugzilla to find bugs by "severity." Example, the detailed search for all "major" bugs (in whatever state of advancement barring 'unconfirmed', 'resolved' and 'closed') comes up with 211 results; "critical" is more manageable at 35 results. Add to that the tricky problem of security bugs (publish on knowledge of them? publish when fixed? not publish at all?) My gut feeling is that public discretion is advisable until "sorted out", but I'm not sure what the policy of koha-community might be. Some openness with confirmed sys-admins would surely be a good idea, but there's no "search/system" way at <http://bugs.koha-community.org> e.g it takes a bit of fiddling to find 9569, and I have little or no idea what else there might be (if anything.) Best -- Paul

1 0

DOM indexing performance
by Fridolin SOMERS 11 Dec '15

11 Dec '15

Hie, We have on a machine big performance issues since indexing was changed from GRS1 to DOM. I have made some benchmarks, looks like indexing time is more than twice longer. When there is a lot of circulation, the indexing of zebraqueue can take more than a minute. We know that this machine is not powerful regarding RAM and disk, but it was enough until now. Does anyone have the same problem ? The point is not to come back to obsolete GRS1, but is there a way to optimize DOM indexing ? My tests shows facets indexing does not change a lot. -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

7 6

Re: [Koha-devel] [Koha] Problem with BarcodeFallbackSearch
by Paul A 10 Dec '15

10 Dec '15

At 10:36 PM 12/9/2015 +0100, someone wrote: >El 09/12/15 a las 22:13, someone else escribiÃ³: > > If this is a desirable feature, a good place to start would be to file a > > bug at http://bugs.koha-community.org. :) That's from the "user" list, and while some of you consider me $whatever, I have concerns regarding the use of the term "bug" that I genuinely believe to be in the best interest of koha-community. "A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways." (Wikipedia) 'bugs' -- quantifiable shortcomings in software 'issues' -- potential problems that aren't directly to related code e.g.design decisions 'enhancements' -- ideas that haven't been implemented yet. 'security' -- must be considered separately; breaches are fundamental, not bugs. If backwards correction is not possible, this must be announced. "Security by obscurity" is a fallacy. Suggest[1]: If you are: a) Requesting a new feature (enhancement), or b) Having build problems, or c) Not sure what the behavior should be, or d) Disagreeing with current intended behavior, or e) Not TOTALLY sure that others would agree this is a bug, or f) For any reason at all not sure this should be filed, ...then please post to the dev list first. You'll get a faster response, and others won't be forced to use the bugs.koha database to have the initial real-time conversations. Nothing is lost this way. If it is eventually concluded that it is a bug, then we can still file it later, after the description and reproduction recipe have been honed. Enhancements, improvements and new features: a good starting point is the user list, (IRC?) and possibly the dev list. If there is consensus, this should be filed at ??? <enhancements.koha-community.org> (similar to bugzilla) Best -- Paul [1] loosely based on Apache 2002.

2 1