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

Migrate/Upgrade from 2.2.3 to latest.
by Rodrigo Santellan 15 Sep '16

15 Sep '16

Hi, I'm trying to do a migration or upgrade from koha 2.2.3 to koha 3. I know is a daunting task that I have embarked but I'm trying to bring back a library to the latest updates of the community. So far this are the steps I have done: 1 - I dump an empty schema of the DB and create a new one with the name koha3. 2 - Apply the update22to30.pl 3 - Import all the tables I could, the one that not been deleted. 4 - Run updatedatabase.pl And now I'm stuck there, I'm missing the table: labels_templates and the table printers_profile is different. I have asked on the IRC channel and they say that table labels_templates is gone on 3.18. I'm heading on a good direction? Or I should do a clean install and then try to import all the old data? I will appreciate any help! Thanks in advance! Regards. Rodrigo Santellán.

3 13

Coding patterns discussion
by Tomas Cohen Arazi 15 Sep '16

15 Sep '16

I've been looking at our coding patterns, and noticed we haven't discussed/agreed on some stuff. Which is a good oportunity to just do it, now the Koha:: namespace is being filled with cool old-code rewrites with lots of test coverage. - Transactions on heavy business functions that should definitely be wrapped inside a transaction. Running $ cd Koha ; git grep txn is just sad. - Little use of Exceptions in Koha. We introduced them, but still don't extend its use. Maybe related to the next item. I think we should keep general exceptions (like Koha::Exceptions::ObjectNotFound) in the general Koha::Exceptions namespace. But move the package-specific ones into its own file. To aid maintenance. A good candidate are Koha::Exceptions::Virtualshelves - We don't use a Try/Catch library. It would make it easier to use Koha::Exceptions with a nice syntax. There are a couple interesting libraries: Try::Tiny and TryCatch. [1] I prefer the latter because the type check seems nicer to write and eval (instead of an if/ifelse cascade checking ref($exception) eq 'Something'. I have my opinions on this items, and it would be great to discuss it openly. There's code in bugzilla waiting for QA, and it'd be great to have some consensus on how to organize the code for the future. Regards [1] http://search.cpan.org/~ether/Try-Tiny-0.27/lib/Try/Tiny.pm and http://search.cpan.org/~ash/TryCatch-1.003002/lib/TryCatch.pm -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

8 12

Circulation rule update
by Cybermon 14 Sep '16

14 Sep '16

Dear All, Actually, I was updated Koha circulation rules. But not changed default_branch_circ_rules field of database. How can I update from 3 to 10 default_branch_circ_rules fields ? Please see below library rules from mysql database. mysql> select * from default_borrower_circ_rules; +--------------+-------------+-------------------+ | categorycode | maxissueqty | maxonsiteissueqty | +--------------+-------------+-------------------+ | BILND | 10 | 10 | | BP | 10 | 10 | | IL | 10 | 10 | | K | 10 | 10 | | PA | 10 | 10 | | PT | 10 | 10 | | S | 10 | 10 | +--------------+-------------+-------------------+ 7 rows in set (0.00 sec) mysql> select * from default_branch_circ_rules; +------------+-------------+-------------------+-------------+-------------------------+--------------+ | branchcode | maxissueqty | maxonsiteissueqty | holdallowed | hold_fulfillment_policy | returnbranch | +------------+-------------+-------------------+-------------+-------------------------+--------------+ | UBPL | 3 | 3 | 1 | any | NULL | +------------+-------------+-------------------+-------------+-------------------------+--------------+ 1 row in set (0.00 sec) mysql>

1 0

What's on in Koha devel #4
by Jonathan Druart 14 Sep '16

14 Sep '16

Hi devs, No new topic this month. Please see bellow the progress of the regular ones. = Security issues = They are almost all pushed. Please see the following 2 omnibus to know what is left: bug 14568 - [OMNIBUS] XSS in Staff Client bug 17096 - [OMNIBUS] CSRF protections = Caching system = Last month I told you about bug 16579, it has been split into 2 bug reports: Bug 11921 - memcached configuration should be moved back to koha-conf.xml Bug 17189 - Add the ability to define several memcached namespaces They have been pushed to master. The conclusion of this is that the memcached configuration is now moved back to the koha-conf.xml file. Memcached will be used for cronjob scripts and Plack without the need to export environment variables. The next step is bug 17224 - Switch to Koha::Cache completely in Context.pm ? To help administrators, bug 17261 is going to display the memcached configuration info to about.pl to inform them if something is badly configured or if everything is ok. = RESTful API = Last month I have asked some general questions about the RESTful API and the different patches waiting for QA/SO. I did not receive any replies from people directly involved in the RESTful API patches. I have put this part aside last month (and certainly for the next month as well). As Marcel said: "If the community decides to push it, the community will have to maintain it". Ok so let's define "the community" :) = Refactoring = == Koha::Patrons == Still lot of things to test/qa, see bug 16846 - Move patron related code to Koha::Patron == C4::Branch == This one is, finally, removed. Bug 15293 - Move the C4::Branch related code to Koha::Libraries is now complete! The total diff is something like 1800+ for 3500- == Koha::AuthorisedValues == Lot of patches to test on bug 15799 (Move authorised values related code into Koha::AuthorisedValues - part 2) == Remove field biblioitems.marc == Following a discussion on koha-devel in July (http://lists.koha-community.org/pipermail/koha-devel/2016-July/042821.html) I have submitted a patch on Bug 10455 - remove redundant 'biblioitems.marc' field and Bug 17196 - Move marcxml out of the biblioitems table This will need to be tested deeply. = Ubuntu 16.04 support = Note that we are still waiting for bug 16554 to support Ubuntu 16.04 and MySQL 5.7. But lot of other bugs exist and only few have been reported. See bug 17258 for the list of the known bugs. = Dev tools = I have sent 2 emails last week, you will find 2 smalls things for bugzilla, 1 for git-bz and 1 for plack: 3 tiny but very useful things - http://lists.koha-community.org/pipermail/koha-devel/2016-September/043023.… Restart plack when needed - http://lists.koha-community.org/pipermail/koha-devel/2016-September/043026.… = Miscellaneous = Tomas asked for feedback on transactions and exceptions a couple of days ago: Coding patterns discussion - http://lists.koha-community.org/pipermail/koha-devel/2016-September/043032.… Note that Paul sent a last call to register for the hackfest in Marseille - http://lists.koha-community.org/pipermail/koha-devel/2016-September/043046.… A dev meeting is planned on September 28th at 21 UTC (https://wiki.koha-community.org/wiki/Development_IRC_meeting_28_September_2…) Please have a look at the agenda and the different topics we will discussed. Cheers, Jonathan

2 1

Call for News: September 2016 Newsletter
by kohanews 14 Sep '16

14 Sep '16

Fellow Koha users ~ I'm collecting news for the September newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events -- **** one month back is the cut-off ***. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Hackfest in Marseille = last call to register !
by Paul Poulain 13 Sep '16

13 Sep '16

Hello Koha ! A reminder: the hackfest in Marseille will take place in a few weeks (oct 10th - 14th), it's time to register !!!! *How to register*: drop me an email *What can I do at the hackfest*: anything useful for the Koha community : testing, documenting, learning, teaching, discovering,... *How much does it cost*: it's free (just count 15€ per lunch, we organize it. Veggie welcomed) *Who will I meet*: almost everyone active in the community (chris, we miss you): 20+ librarians. Some great developers (random order, sorry if I forgot some) Owen, Brendan, Tomas, Mirko, Katrin, Magnus, Jonathan. The people from Koha Gruppo Italiano who convince Ebsco to fund us every year. All BibLibre staff, 5 of ByWaterSolutions staff, 2 of ptfs-europe staff, "Wow, that's a lot of people !" Yes, we have already 54 registrations. But don't worry, this year, we have an additional room just next door that can welcome 12-16 persons, so we still have some empty seats! -- 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

Discussion of mysqldump / bug 12374
by Barton Chittenden 13 Sep '16

13 Sep '16

I recently created a patch for bug 12374 'Add koha-mqsqldump script, analagous to koha-mysql'. This prompted discussion in the ticket, as well as in IRC; Katrin requested a wider discussion: I'd like to get some more opinions on this as both Magnus and Liz have left > notes that this might be better as options for koha-mysql instead of having > a completely separate new script. > Could you bring this up on the mailing list/meeting/IRC for some more > comments, please? Here are Magnus' notes on the subject: > > We already have the koha-dump script, which creates two files, one > mysqldump and one .tar.gz file containing some config and log files, in the > /var/spool/koha/<instancename> dir. Perhaps it could be an option to extend > this script with a couple more options, to make it possible to: > - not dump the configs and logs > - place the mysqldump in a given dir And Liz Rae's notes on the ticket: As noted in IRC, I don't like this solution for a number of reasons. > We already have koha-dump, it's my feeling we should build in the option > to use mysqldump parameters into that instead of having Yet Another Koha-* > script to maintain and document. As well as IRC: 21:33 wizzyrea barton doesn't koha-dump do the same thing > 21:33 it is the bones behind koha-run-backups > ... > 21:34 wizzyrea I don't like it. Should add the functionality to > koha-mysql, as an option > ... > 21:51 wizzyrea if we were to go db agnostic, that would be problematic. We'll take those as the objections to the addition of koha-mysqldump -- here are my arguments for it: 1. If we add to koha-dump or koha-mysql, we require a means of dis-ambuguating arguments controlling the script vs. arguments passed through to mysql / mysqldump. 2. koha-dump is well suited to backing up the entire site, but would require command line options to disable the dump of configs and the full database. This compounds point 1. 3. We already have the koha-mysql koha-mysqlcheck wrappers around mysql and mysqlcheck respectively -- koha-mysqldump seems like a logical extension -- users might logically expect koha-mysqldump to exist, and would not be surprised to find it among the existing tools. 4. The overhead of supporting this script is minimal -- It's already written and documented, and it's only minimally different from koha-mysql, which has been stable for years. 5. It follows the Unix philosophy of 'Do one thing well'. Liz's point that koha-mysqldump is not database agnostic is valid -- but then neither are koha-mysql or koha-mysqlcheck. The reality is that koha-dump should probably be implemented as a wrapper around a tool like koha-mysqldump, which should in turn be thin wrapper around a database agnostic tool that knows how to supply database connection arguments to mysql, mysqldump, postgreSQL clients, etc... But it's not. So failing that, my koha-mysqldump patch fills a currently un-met need -- I routinely copy koha-mysql into my home directory on remote machines and hack it into koha-mysqldump when I need to back up single tables or groups of records. Respectfully, --Barton

3 2

Restart plack when needed
by Jonathan Druart 12 Sep '16

12 Sep '16

Hi devs, A couple days ago I found that the --reload option of plackup causes a high CPU load (around 35%). If I remove it, the process is around 1% (when sleeping). So I have tried inotify2 (Linux::Inotify2) to add watchers and restart plack when a file is changed. But 1/ It's not recursive and I will have to script without knowing the perf impacts and 2/ It will be terrible when checking out another git branch (1 restart per file changed!). After a talk with a friend, I decided to use a git hook and map a key in my vim config to do so: The git hook: .git/hooks/post-checkout #!/bin/sh exec /usr/local/bin/restart_plack exit 0 The vim map command: map <F2> <Esc>:w<CR>:!(/usr/local/bin/restart_plack > /dev/null 2>&1)&<CR>a And that's all :) To be complete, here is my restart_plack script: http://pastebin.com/8wFSC4fJ Cheers, Jonathan

3 2

Berlin, 16 Sep 2016: Round the World Koha Speaking Tour
by Mirko Tietgen 12 Sep '16

12 Sep '16

Dear list, this Friday we will have Joann Ransom talk about Koha in Berlin. She'll stop by on her Round the World Koha Speaking Tour at Büro 2.0, Weigandufer 45, 12059 Berlin Friday, 16 September 2016, 14–16 Admission: free Seats are limited but still available, please send me an email offlist if you want to attend. Cheers, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

1 0

3 tiny but very useful things
by Jonathan Druart 09 Sep '16

09 Sep '16

Hi devs, I have fixed 3 tiny things this morning: 1/ Fold obsolete patches I have sent a SQL query to Chris to automatically add the obsolete tag to the obsolete comment. That will cause them to be collapsed by default (was already fixed previously by a greasemonkey script). 2/ I sent this graph to Kyle yesterday: https://bugs.koha-community.org/bugzilla3/showdependencygraph.cgi?id=15449 (it is the refactoring work) and just realized it's unreadable because we do not have color markers. I have written a patch and sent it to Chris (http://pastebin.com/pN9EacCL) Hopefully it will be available soon. 3/ The last, but not the least. Yesterday on #koha "oleonard wishes for git-bz auto-applying of dependent patches" Hum... not that hard finally, here it is: https://github.com/joubu/git-bz/tree/apply_on_cascade A good example to learn how it works: git bz apply 17249 Have fun :) Disclaimer: This has not been tested deeply (but should not make your computer burst into flames) Have a good end of GBSD and a great week-end! Cheers, Jonathan

2 1