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

Re: [Koha-devel] QohA
by Mason James 31 Jul '12

31 Jul '12

On 2012-07-31, at 3:54 AM, Jonathan Druart wrote: > Hi Mason (and QA team), > > I made some refactoring of your code. > > Several things are still not good, but I hope I helped to improve your code and to make it more maintainable. > > Please have a look a the TODO file I created at the root of the project. > > I hope these modification are going the same way that you planed. yes, thank you - you have done much of what i planned to do :) my next improvement is to re-use the existing ./koha/t/*.t tests, rather than cut/pasting them into the qa-repo > > Regards, > Jonathan > > > https://github.com/joubu/koha-qa-tools/tree/qoha cheers, Mason -- KohaAloha, NZ

1 0

Re: [Koha-devel] Koha on Ubuntu LTS
by Paul 31 Jul '12

31 Jul '12

At 03:58 PM 7/30/2012 -0400, Jared Camins-Esakov wrote: [snip] >However, using a normal sudo account for crontab -e, use vi, add: > >KOHA_CONF=/etc/koha/koha-conf.xml >KOHAPATH=/usr/share/koha >PERL5LIB=$KOHAPATH/lib >* * * * * Â koha Â >$KOHAPATH/bin/migration_tools/<http://rebuild_zebra.pl>rebuild_zebra.pl -a >-b -z 2>&1 > /dev/null > >makes a fully functional cron for incrementing Zebra, albeit in >/var/spool/cron/crontab/ with root:root ownership. All that remains to be >done is to rename the koha file in /etc/cron.d to koha.old (or plain >remove it.) [N.B. the job is quasi-instantaneous, so running every minute >is imperceptible as overhead.] > > >The ownership of the file doesn't matter. What matters is that you >shouldn't have this configured in two different crontabs, which you >currently do. This may cause problems. Very minor point: I wrote "All that remains to be done is to rename the koha file in /etc/cron.d to koha.old (or plain remove it.)" I should have said that I already did it: paul@server2:/var/log$ sudo cat syslog | grep CRON Jul 30 16:09:01 server2 CRON[3345]: (root) CMD (koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null) Jul 30 16:10:01 server2 CRON[3351]: (root) CMD (koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null) Jul 30 16:11:01 server2 CRON[3354]: (root) CMD (koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null) Also thanks for correcting the Wiki, but there was something strange going on (char set glitch?) Copy/paste from Firefox to Putty screen gives: perl .I /usr/share/koha/lib /usr/share/koha/bin/migration_tools/rebuild_zebra.pl .b .w Not the "." rather than "-" for I, b and w I did an edit, which worked in the "show preview" so I saved it. Best - Paul

2 1

Re: [Koha-devel] Koha on Ubuntu LTS
by Archives and Collections Society 30 Jul '12

30 Jul '12

Over the last few days, I've looked into the cron "problem" that I raised the other day and just to be sure, I've just reformatted and installed the whole server+Koha again, using 3.6.7's INSTALL.ubuntu, Tomas' Wiki page and my own notes. I created the user koha by: $ sudo adduser koha but did not use either of the following: $ sudo adduser koha sudo [to give sudo rights] $ sudo adduser koha adm [to give full admin rights] This gives rise to user=koha not being able to use crontab -e, as can be seen: paul@server2:/$ su koha Password: koha@server2:/$ crontab -e crontabs/koha/: fdopen: Permission denied koha@server2:/$ sudo crontab -e [sudo] password for koha: koha is not in the sudoers file. This incident will be reported. koha@server2:/$ However, using a normal sudo account for crontab -e, use vi, add: KOHA_CONF=/etc/koha/koha-conf.xml KOHAPATH=/usr/share/koha PERL5LIB=$KOHAPATH/lib * * * * * koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null makes a fully functional cron for incrementing Zebra, albeit in /var/spool/cron/crontab/ with root:root ownership. All that remains to be done is to rename the koha file in /etc/cron.d to koha.old (or plain remove it.) [N.B. the job is quasi-instantaneous, so running every minute is imperceptible as overhead.] ALSO, I've had to relook at how to do a complete Zebra re-index, given the permissions to user=koha. The following is fully functional: $ su koha $ cd usr/share/koha $ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -a -r -v $ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -b -r -v -x [N.B. This differs from the Wiki Appendix C., which relies on user=koha having sudo rights.] All of this could possibly be avoided by giving user=koha sudo rights [$ sudo adduser koha sudo], but I am for various reasons loath to do so. The solution outlined above works, and I have not yet found a specific user=koha task that fails. So my question is 'have I missed something else that requires user=koha to have sudo rights?' If not, I would suggest that a revamp of the Ubuntu installation should be written -- I'll be happy to do so. Best - Paul

2 1

Re: [Koha-devel] Koha on Ubuntu LTS
by Paul 30 Jul '12

30 Jul '12

Over the last few days, I've looked into the cron "problem" that I raised the other day and just to be sure, I've just reformatted and installed the whole server+Koha again, using 3.6.7's INSTALL.ubuntu, Tomas' Wiki page and my own notes. I created the user koha by: $ sudo adduser koha but did not use either of the following: $ sudo adduser koha sudo [to give sudo rights] $ sudo adduser koha adm [to give full admin rights] This gives rise to user=koha not being able to use crontab -e, as can be seen: paul@server2:/$ su koha Password: koha@server2:/$ crontab -e crontabs/koha/: fdopen: Permission denied koha@server2:/$ sudo crontab -e [sudo] password for koha: koha is not in the sudoers file. This incident will be reported. koha@server2:/$ However, using a normal sudo account for crontab -e, use vi, add: KOHA_CONF=/etc/koha/koha-conf.xml KOHAPATH=/usr/share/koha PERL5LIB=$KOHAPATH/lib * * * * * koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null makes a fully functional cron for incrementing Zebra, albeit in /var/spool/cron/crontab/ with root:root ownership. All that remains to be done is to rename the koha file in /etc/cron.d to koha.old (or plain remove it.) [N.B. the job is quasi-instantaneous, so running every minute is imperceptible as overhead.] ALSO, I've had to relook at how to do a complete Zebra re-index, given the permissions to user=koha. The following is fully functional: $ su koha $ cd usr/share/koha $ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -a -r -v $ KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha/lib ./bin/migration_tools/rebuild_zebra.pl -b -r -v -x [N.B. This differs from the Wiki Appendix C., which relies on user=koha having sudo rights.] All of this could possibly be avoided by giving user=koha sudo rights [$ sudo adduser koha sudo], but I am for various reasons loath to do so. The solution outlined above works, and I have not yet found a specific user=koha task that fails. So my question is 'have I missed something else that requires user=koha to have sudo rights?' If not, I would suggest that a revamp of the Ubuntu installation should be written -- I'll be happy to do so. Best - Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

1 0

XSLT output method
by Fridolyn SOMERS 30 Jul '12

30 Jul '12

Hie, I've worked on Bug 8513 : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8513 The source of this bug is that an anchor tag (<a>) is build without content. With actual version, the generated code is : <a href="..." /> That is what causes a really odd broken page (see bug details). Now, I notices that in XSLTs, the output method is XML. If I use XHTML method, the anchor is generated like this : <a href="..." ></a> And in this case, page is not broken. The anchor is just not visible. I corrected bug in XSLT without changing method but I wonder, why using XML method ? XHTML method corresponds to the usage, and can avoid a lot of bugs like n°8513. I even prefer HTML method. It is not good to break if generated code is not XHTML but just HTML. Best regards, -- Fridolyn SOMERS Biblibre - Pôle Support fridolyn.somers(a)biblibre.com <mailto:fridolyn.somers@biblibre.com>

1 0

Re: [Koha-devel] Koha on Ubuntu LTS
by Paul 30 Jul '12

30 Jul '12

At 06:30 PM 7/28/2012 -0400, Jared Camins-Esakov wrote: >[snip] >Did you try rerunning updatedatabase? Many thanks for the reply. Yes, but I ran paul@server2:/usr/share/koha/intranet/cgi-bin/installer/data/mysql$ perl -I updatedatabase.pl overnight - it only took a few minutes when initiated by Koha after the install. If I've made an error, could you please assist with the syntax? Also, Chris N. suggested "Also double check to be sure that OpacMaintenance did not get set somehow" -- it was set (not sure how - I didn't even realize that this preference existed) and now the OPAC is up and running. Thanks Chris. >The instructions all assume a user crontab. If you are using >/etc/cron.d/koha, you should not be using the user crontab (as all the >instructions assume), or you could do things vice versa. Hidden in a corner under the name 'root' I finally found it, and the cron is now working perfectly (except 'mail', see below). For the archives: $ cd /var/spool/cron $ sudo chmod 755 crontabs $ sudo vi root [change 5 mins to 1 min] :x $ cd .. $ sudo chmod 1770 crontabs >So, remove nullmailer. nullmailer needs to be configured appropriately if >you are using it. Done, and get (once a minute) syslog entries: Jul 29 13:38:01 server2 CRON[1854]: (CRON) info (No MTA installed, discarding output) which was why I was asking if there was an easy way of "turning it off" in Koha (I've looked unsuccessfully for a global O/S method to turn off "warnings) - I don't need an email every minute, 24/7 :-} -- and I'd like to reinstall nullmailer to verify all the "wanted" patron emails (no intention of installing sendmail on this sandbox; on the production server I've got sendmail to selectively dev/null unwanted messages.) Many thanks all around. I'll continue comparing this to our production box, and get some of our cataloguers to have a look over the next few days. As and when we come up with more bits and pieces, I'll have a look at helping with the Wiki page -- Tomas, I see that you have done all the editing, but have a blank "talk" page. Would you prefer to email (either on- or off-list) or use the "talk page"? Regards -- Paul

3 3

Koha on Ubuntu LTS
by Paul 29 Jul '12

29 Jul '12

On 7/24/2012 I wrote: [snip] >Anyway, I've just repartioned the sandbox, installed a fresh 12.04 server, >and am right now wget'ting 3.6.7 >More later ... Just got back after a few days away. Installation all went well (did not install php package, but used php-pear leaving Apache2 as worker) OPAC and staff client both functional from LAN workstations. Restored a working db (3.6.1) to MySQL, Koha "did its thing" updating the db format, OPAC showed a "System Maintenance" placard, I re-indexed biblios and authorities (no problem), checked the cron-job for the incremental zebra indexing (working properly.) So everything fine except: MAJOR: OPAC is stuck with the "System Maintenance" page - I've rebooted (same result), so am looking for ideas, please, as to where to start looking. This is _not_ a browser cache problem. SEMI-MAJOR: The cron /etc/cron.d/koha (exactly as per Wiki, README, etc) only works if owner:group is root:root or root:koha (fails completely if koha:koha). This (because the "user koha" appears in field #6, and without it, it fails) is leading to the zebra incremental running twice: Jul 28 17:20:01 server2 CRON[2132]: (root) CMD (koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z &> /dev/null) Jul 28 17:20:01 server2 CRON[2135]: (koha) CMD ( $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z &> /dev/null) This leads to another: SEMI-MAJOR: From Koha dependencies (I think) nullmailer got installed. It is doing a serious job of bloating the mail.log and mail.err (both up to over half a Gig in a couple of hours, because each "double cron" appears to want to email: Jul 28 17:20:01 server2 CRON[2136]: (koha) MAIL (mailed 1 byte of output; but got status 0x0001, #012) Is there any way in Koha to turn off this type of mailing? Or should I look for another way of sending these things to /dev/null without logging? (I get the nasty feeling that nullmailer is attempting to recursively retry to send the whole queue *every minute* i.e. whenever another input is detected from the one minute zebra cronjob. MINOR: "Superlibrarian" permission flags (not names|passwords) got lost (so I couldn't log in until I reset them; same for two other staff members, and with no permissions even the correct password doesn't let you in.) All other "less than supers" were fine ... Looking forward to suggestions, thanks - Paul [Notes, fairly detailed, at <http://navalmarinearchive.com/research/koha_ubuntu.html>

4 3

Official Koha Newsletter: Volume 3, Issue 7: July 2012
by Daniel Grobani 27 Jul '12

27 Jul '12

[Below is the text of the newsletter. For active links and a more readable format, please visit http://koha-community.org/koha-newsletter-volume-3-issue-7-july-2012] Official Koha Newsletter (ISSN 2153-8328) Volume 3, Issue 7: July 2012 Edited by Daniel Grobani, Koha Community Newsletter Editor. Please submit news items to danielg.koha(a)gmail.com. Table of Contents Koha Development Koha 3.8.3 Released Koha 3.6.7 Released Koha Statistics Release Manager’s Newsletter Roles for Koha 3.12 Testing, Testing Koha Dashboard Koha Community New Koha Libraries Community Gossip Past Koha Events July General IRC Meeting Upcoming Koha Events August General IRC Meeting KohaCon13 Venue Decided Koha Development Koha 3.8.3 Released by Chris Cormack The Koha community is proud to release Koha version 3.8.3. This is a bugfix release, and contains a number of important fixes You can obtain Koha 3.8.3 here. Debian packages will be available here soon. Release notes are here. Koha 3.6.7 Released by Jared Camins-Esakov The Koha release team is happy to announce the release of Koha 3.6.7. This is a stable release and contains bugfixes as well as updated translations. You can download Koha 3.6.7 here. Release notes are here. Go forth, download, and enjoy. Koha Statistics Chris Cormack, Koha Community statistics wizard, has posted statistics for Koha 3.6.7, Koha 3.8.3, and Bugzilla statistics for June. Release Manager’s Newsletter Paul Poulain, Koha 3.8 Release Manager, publishes a monthly newsletter dedicated to Koha 3.8 development. It can be found on the Koha Community website in the Koha News category. The latest issue is here. Roles for Koha 3.12 With the release of Koha 3.10.0 scheduled for 22 October 2012, the community is thinking about roles for 3.12. Release Manager candidate Jared Camins-Esakov has submitted a proposal outlining his intentions should he be elected RM. Testing, Testing There are a lot of developments in testing and signing off this month. Pages on the community wiki have been created on unit tests, continuous integration, interface testing with WWW::Mechanize, and sandboxes. Koha Dashboard Chris Cormack has created a dashboard showing the last five sign-offs, the five oldest bugs needing sign-offs, new features recently pushed, new developers, Jenkins status, bug activity, bug statuses, a random bug, a monthly scorecard, important dates, and statistics on commits to master. The dashboard is a work in progress and can benefit from your contribution to its development. Koha Community New Koha Libraries Biblioteca Nacional De Venezuela (Venezuela) Chinook Library Network (USA) (via ByWater Solutions) Converse Free Library (USA) (via ByWater Solutions) Shire of Derby West Kimberley (Australia) (via Calyx) Waimate District Library (New Zealand) (via Catalyst) Community Gossip Elliott Davis has joined ByWater Solutions as Development Support Specialist. Elliott is also working on a proof-of-concept to port Koha to the Catalyst MVC perl framework. He’s also posted a guide to configuring LDAP with Koha. Stefano Bargioni has prepared an experimental Dewey AutoSuggester that retrieves data from dewey.info using SPARQL in jsonp format. He’s working on integrating it into Koha. In the meantime, a demo is available. Plano Independent School District, in Plano, Texas, has set up their own VM internally running Koha 3.6.x and gone independent from their original support company as of June 6th. Nicole Engard is working on adding to Koha the ability to search for items by color. Vimal Kumar V. has created Koha Live CD Lite, a lightweight Koha live CD based on Ubuntu 10.04 Gnome desktop and Koha 3.8.2. Joy Nelson has posted some recommendations for naming conventions when creating codes in Koha. Past Koha Events July General IRC Meeting The July general IRC meeting was held on 18 July 2012. More information, including the agenda and links to the minutes, is here. Upcoming Koha Events August General IRC Meeting The August general IRC meeting will be held on 8 August 2012. More information, including the agenda, is here. KohaCon13 Venue Selected The voting for the venue for KohaCon13 has ended and the top choice was Reno, Nevada, USA. Complete voting results are here.

1 0

Koha Catalyst Work
by Travis Elliott Davis 27 Jul '12

27 Jul '12

Hi Everyone, I have semi-recently been working on a port of Koha to the Catalyst framework. I started right after school was out and didn¹t get a chance to spend much time working on it. I am taking my last class this summer and will be done in August and would like to pick my work back up on this port. What I would like to do is solicit opinions for what I could do as a proof of concept. I started work on re-writing notices when it occurred to me that this may not be something that anyone is interested in seeing. For those of you that don't know Catalyst is an MVC based framework written in perl. I believe that moving Koha to Catalyst would not only clean up the codebase but also help with the logical flow of code. I know when I first started developing for Koha the two most daunting tasks were navigating the codebase, and figuring out what pointed where. I am not suggesting that we all jump on a giant rebase project right now, but I would like to look into it and get opinions. Catalyst has a very active development community and seems to be very well supported. It already has support for Template Toolkit, Apache Solr, Plack, and a whole lot more. If you want to find out what is supported (which I encourage) you can hit up their website at http://www.catalystframework.org/. You can also find my latest work at: https://github.com/libsysguy/koha-catalyst. It is obviously not complete but it will run and give you a basic idea of the code structure. Let me know your thoughts and ideas, I'm excited to hear what you have to say (Even if it is "Elliott you've lost your mind"). All the Best, Elliott Davis

4 4

Koha 3.4 end of life?
by Owen Leonard 26 Jul '12

26 Jul '12

This question has come up in the last few IRC meetings, but we need a broader consensus: Should development of 3.4 be officially ended? If so, how should this be handled? Discussion in today's IRC meeting brought up the question of whether it should be "killed" or merely "orphaned." I would appreciate some explanation from both sides about the definition of those choices so we can proceed to an informal vote. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

5 6