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

a few days before Feature Freeze = 10 patches to signoff / 3 paches to QA quickly
by Paul Poulain 19 Sep '12

19 Sep '12

Hi listserv Reminder: the Feature Freeze for Koha 3.10 is soon (next monday -the 22th is a saturday, I'm GMT+0 I'll push the last "risky" patches on monday, to let everybody a chance to signoff/QA patches on "his" 22th) Since my last RM newsletter many patches have been signed-off and QAed (and pushed). But there are still some patches that should make their way quickly to 3.10, or they'll wait for 6 more months ! So, PLEASE, SIGN-OFF ! Here is an updated list of Enhancements that I won't push after FF (for 3.10) and NEED SIGNOFF: 5342 Serial claiming improvements 5349 Moving an order 5356 Shipping billing address improvements 7162 Factorize code for order cancellation 7295 list of librarian managing a basket 7688 Change subscriptions numbering pattern and frequencies 7736 Edifact QUOTE and ORDER functionality 7957 Routing lists: manage several routing list for each subscription, and export them as CSV 8365 Renewal duration in issuingules 8782 Close a suscription QA TEAM = The 3 following are already Signed-off and just need QA: 5335 More granular VAT 8523 Authority hierarchies only support UNIMARC 5786 Move AllowOnShelfHolds system preference to the Circulation Matrix I think all other ENH will be pushable after the FF and before the String Freeze (but, disclaimer: as already said, I may change my mind. If I think a patch can have a potential side effect, it will wait for 3.12) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Re: [Koha-devel] [Koha] 3.8.4 staff main page
by Paul 19 Sep '12

19 Sep '12

"Redirecting" this to the devel (not user) list At 06:51 PM 9/14/2012 +0800, MT wrote: >>The first staff page in 3.8.4 after logging in has a tabbed search box >>at the top that "defaults" to patron check [out]s - our staff has >>asked me to change this to the fourth/last tab "catalogue" as they >>cannot find a "preference" anywhere. >And this is why a git installation for testing and development would be >very helpful. You could develop a patch for changing the default ordering >of the tab in the header_search div, which could be of use to the community. >The recommended way is to USE JQUERY (javascript). This upgrades with ease >if done properly. >Do not modify the perl/template files! This sets you up for an upgrade >headache. I am unaware of an *easy* way to write anything in js to accomplish my staff's request. However, here's the fix (Mark, if you think this could be of use to the community as you suggest above, please disseminate it as an enhancement, bug, whatever ...) which was remarkably easy, once I found the relevant code. FYI, Firebug does not appear to be of much use tracking down things like these. To change the search default of "Check out, Check in, Search patrons, Search the catalog" in the tabs at: <http://koha-admin3/cgi-bin/koha/mainpage.pl> edit /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/home-search.inc and reorder lines 32-35 to put "your preference" at top: [% IF ( CAN_user_catalogue ) %]<li><a href="/cgi-bin/koha/catalogue/search.pl#catalog_search">Search the catalog</a></li>[% END %] [% IF ( CAN_user_circulate ) %]<li><a href="/cgi-bin/koha/circ/circulation.pl#circ_search">Check out</a></li>[% END %] [% IF ( CAN_user_circulate ) %]<li><a href="/cgi-bin/koha/circ/returns.pl#checkin_search">Check in</a></li>[% END %] [% IF ( CAN_user_borrowers ) %]<li><a href="/cgi-bin/koha/members/members-home.pl#patron_search">Search patrons</a></li>[% END %] The focus will always be on the first tab. Best regards, Paul

6 8

Questions from the great wall of install...
by Mark Tompsett 18 Sep '12

18 Sep '12

Greetings, As I am putting finishing touches on the Ubuntu great wall of install, for the purposes of *splitting* and organizing (packages/git/tarball – the latter of which will be hidden), I have written down questions that I thought perhaps the list may be able to clarify. 1) When doing a packages install, a message about upgrading from 3.2 to 3.4 pops up. What is the recommended upgrade path from pre-3.4 to current? Is that message accurate? 2) I noticed that Mime::Lite (forgive wrong capitalizations) triggers the install of nullmailer under a fresh install of Ubuntu 12.04 LTS Server. Seeing as Koha has cronjobs that do mailing, are their any external links (like Vimal Kumar V.’s link to a gmail relay set up) which would be recommended for getting those functions to work properly? I understand that a “configuring mailing” wiki page is beyond the scope of Koha, but surely a “look here for suggested hints, but configuration of mailing is out of scope” page is okay? 3) In the Ubuntu documentation the ordering of /etc/perl/XML/SAX/ParserDetails.ini is supposedly important, as “You must be sure you're using the XML::LibXML SAX parser, not Expat or PurePerl, both of which have outstanding bugs with pre-composed characters.” During a packages installation, I decided to look at the ini file, and found it wasn’t in the recommended order. Is this a problem with the packages or has this point become irrelevant? 4) Does the packages installation method set up apache2 correctly, or does AddCharset UTF-8 .utf8 AddDefaultCharset UTF-8 Still need to be added to a configuration file and a restart issued? It’s not in the Debian instructions for packages. 5) In MySQL “select variables like ‘%colla%’;” and “select variables like ‘%char%’;” generate non-utf8 entries. Is this correct? Nothing like this is mentioned in the Debian instructions for packages. I think that’s it for now. I hope to start the splitting in the near future, and be done before the end of the week. I’ve got an upgrade (3.6.3 tarball to 3.8.5 packages) to do this weekend. GPML, Mark Tompsett

5 6

RFC: Koha needs a logger!
by Kyle Hall 17 Sep '12

17 Sep '12

Hey all, I've been thinking about this for quite a while now. I feel that Koha would benefit greatly from having a traditional logger, rather than relying on warn's being written to the apache logs. This would give us many benefits. First, we would be able to log everything to one or more standard files, regardless of whether that file was running under apache or not. Second, we could implement standard logging levels ( trace, debug, info, warn, error, fatal ). It would also help us debug ajax-related issues where child processes no longer write to the apache module. The Catalyst Perl framework has been a primary inspiration for this. We could have C4::Context->log->debug('this is a test message'); Our logger would detect the current error level and output or ignore the message accordingly. My research has lead me to Log4perl, which seems to be an outstanding logging module. It can even capture existing warns and dies. It would work perfectly except for one scenario I was hoping for. I have been thinking it might be useful for developers and even just experienced Koha users of the we could dump all the log output to the webpage. So mainpage.pl?debug=1 would not only enable debug messages, but then append all those debug messages to the bottom of the returned html. Log4perl is meant to be used as a singleton, so even if we can get the logged message back out, it would have messages from other koha scripts that were running concertedly. If I am incorrect, please let me know! So the options are: 1) Forget about the dump-to-screen feature, and just use Log4perl 2) Write our own logger from scratch with all these features, largely duplicating the effor of Log4perl and other loggers 3) Write our own logger that can handle the dump-to-screen feature, but use Log4perl within Koha::Logger for all other logging. Another idea, implement dbi tracing to allow dumping of all queries to the screen and log. Also, Perhaps the dump-to-screen could create a popup window instead of appending to the bottom of the screen. I'm looking for any and all opinions or ideas on this subject. Thanks! Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com )

5 10

Re: [Koha-devel] Questions from the great wall of install...
by Robin Sheat 17 Sep '12

17 Sep '12

Op 17-09-12 13:43, Mark Tompsett schreef: > And again, what about a git install? You need the instructions still for > that. Well, I'm talking about the packages. The git process is presumably quite different anyway. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D

1 0

any error in update database (on master)
by Paul Poulain 17 Sep '12

17 Sep '12

Hi koha-devel, Chris noted an error on jenkins when upgrading after patch 5911 has been pushed: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5911#c59 > DBD::mysql::db do failed: Can't create table 'koha.transport_cost' (errno: 150) at ./installer/data/mysql/updatedatabase.pl line 5703. > (150 is foreign key constraints) > This might be specific to the jenkins machine, but just noting why it didnt update properly Is there someone else who saw this error ? Should I worry/investigate more ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]
by Paul 15 Sep '12

15 Sep '12

At 04:41 PM 8/22/2012 -0300, Tomas Cohen Arazi wrote: [snip] > > The tarball has always worked extremely well on i386 machines -- I just > get the impression (not proven) that Ubuntu 12.04 gets its knickers in a > twist on AMD64. Â But with a little time and effort workarounds can be > found. Â Probably nothing wrong, just new quirks, with either Ubuntu or > Koha, but I do not need to be under pressure for the production upgrade. > >is not a 12.04 problem, is a problem with the specific file you're using >with dpkg, which lists some files not available anymore on 12.04. >As Mark said that file has already been patched and its waiting for >inclusion on next release. Thanks for the reply. But, as you say, "its waiting for inclusion on next release" so it's broken in this release. >That said, you can do a clean install using the instructions and ommiting >that --set-selections step. And installing the dependencies by hand. As >Mark also said. More or less what I've done -- but it would not be rocket science to edit install_misc/ubuntu.packages to avoid a certain amount of grief (and before anyone asks "well why don't you do it?" I will as soon as I'm certain that my experience is reproducible and bullet-proof. It may involve looking at the upstream .pl file to see how the list is invoked.) >I also use the tarball in our deployment (38 instances on a single BIG >server) without issues. I'm only trying a test install on relatively BIG server (64-bit, 6 core Intel i7-980X, solid state raided drives, 16Gb ram), mileage varies... > Besides that i386 packages pull which I reported and has been solved. When, where, how? I had to 'sudo apt-get purge .*:i386' for about 50 dependencies in the pull in koha-3.08.04.tar.gz >Anyway, I think we should go back to what your original problem was.Â Is >your incremental indexing working? That was 3.8.3, now trashed, but it never worked -- I'll try it on a 3.8.4 install as soon as I'm away from this machine. >Have you properly set your sax parser? [snip] Yes. Best - P. --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

13 42

String freeze for 3.8.5
by Chris Cormack 14 Sep '12

14 Sep '12

Hi All I will not be pushing any more patches that involve string changes from now on, until 3.8.5 is released on the 22nd of September. Frederic when time permits can you update the 3.8.x po files in pootle please. Thank you Chris

3 3

Overdue Notices
by glaws 14 Sep '12

14 Sep '12

I have a question about overdue notices in Koha 3.8.3. Not sure if this is a bug or not... When a patron has overdue items, the "First Overdue Notice" will generate a list of those items. Perfect. When other overdue items subsequently become overdue within an undetermined but limited amount of time, a "First Overdue Notice" is generated for those items, but if the first set of items have not been resolved (by returning them), they are repeated in the second "First Overdue Notice". See attached .pdf. Desired/correct functionality? -- Greg Lawson Network Administrator Rolling Hills Consolidated Library 1912 N. Belt Highway St. Joseph, MO 64506

3 3

Please include a test plan for your patches!
by Owen Leonard 14 Sep '12

14 Sep '12

With Global Bug-Squashing Day in full swing, I want to test some patches and sign off what I can. The list of bugs needing signoff (http://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=dorem&remactio…) has no low-hanging fruit, so that makes it really important that every bug report include a good test plan. Here are the basics for what I should know after reading the bug report: 1. What the problem is. 2. How to reproduce the problem. 3. What the patch does to solve the problem. 4. What (if any) configuration steps need to be taken after the patch is applied. 5. What steps to take to test that the patch is working correctly. A lot of patches seem to be added with only #3, which in some ways is the least important step from the point of view of people testing. If you have bug on Paul's list of patches which won't be pushed after the feature freeze (in the RM newsletter: http://koha-community.org/koha-release-manager-newsletter-10-2012-08/) and you want to make sure it can be tested, please add a thorough test plan! -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 1