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

String freeze for 3.6.7
by Jared Camins-Esakov 20 Jul '12

20 Jul '12

Good morning. Apologies for the late notice, but as of right now 3.6.x is in string freeze in preparation for the release of 3.6.7 in one week. Thank you to the translation teams for their hard work. Regards, Jared Camins-Esakov -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

4 4

Bug 8375 is unfortunatly wrong solution for wrong problem
by Dobrica Pavlinusic 20 Jul '12

20 Jul '12

I'm trying to make label printing work for utf-8 characters. I noticed that Bug 8375[1] got included in master, and I think it's a wrong solution to problem. 1: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8375 I'm copy/pasting my comment on this bug here to give it wider exposure because I think this is somewhat critical: I'm getting Wide character in compress at /usr/share/perl5/PDF/Reuse.pm line 825. errors when I try to use label printing with utf-8 characters (with or without this patch). However, when changing utf8::decode to utf8::encode in this patch, everything works. Let me try to explain why: PDF::Reuse does binmode on it's file-handle so we shouldn't pass any utf-8 characters ("wide characters") to it. However, this patch proposes using utf8::decode which (according to perldoc utf8) does: · $success = utf8::decode($string) Attempts to convert in-place the octet sequence in UTF-X to the corresponding character sequence. The UTF-8 flag is turned on only if the source string contains multiple-byte UTF-X characters. If $string is invalid as UTF-X, returns false; otherwise returns true. So decode is used when we are converting bytes into utf-8 strings, not the other way around. However, utf8::encode does exactly what we need: · utf8::encode($string) Converts in-place the character sequence to the corresponding octet sequence in UTF-X. The UTF8 flag is turned off, so that after this operation, the string is a byte string. Returns nothing. Which is exactly why I'm proposing to change this patch to use encode instead of decode. I guess that this patch has passed sign-off and QA because it's a special case: We are not correctly converting latin-1 characters into utf-8 when using Z39.50 search, so we get utf-8 marked string which contains latin1 umlauts inside it. In that case, utf8::decode correctly strips utf-8 flag and everything works, but this change also breaks real string which have utf-8 characters in them. -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

3 2

Ubuntu support
by Tomas Cohen Arazi 19 Jul '12

19 Jul '12

I've been struggling with $ dselect --set-selections install_misc/ubuntu.packages $ dselect install pulling i386 packages and trying to break my poor amd64 12.04 PVM, and started to dig on problems related to Ubuntu support and docs problems. The most bugs reported have to do with docs being outdated. And whether a patch should be applied or not depends on this question: What Ubuntu versions should we support? My vote is for the current LTS revisions only (lucid and precise, the first being outdated for master i guess, not sure). Their 2-year release cycle seems to be enough for having a fair recent version of the required libs. So, this files might need being updated/deleted and new ones created: INSTALL.ubuntu INSTALL.ubuntu.lucid ubuntu_maverick.packages (delete or at least rename!) ubuntu.packages ubuntu-pkg-check.sh I propose: INSTALL.ubuntu.lucid INSTALL.ubuntu.precise install_misc/ubuntu_lucid.packages install_misc/ubuntu_precise.packages The idea is avoiding confusion. I'd volunteer to help on this task. Bugs related to this: - http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7764 - INSTALL.ubuntu needs updating - http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7759 - Use Koha-Contrib-Tamil to update Zebra data in background (needs to be documented in the INSTALL.* files) - http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7858 - Missing packages from install_misc/ubuntu.packages - http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8192 - Update libraries and Missing library in install_misc/ubuntu.packages - http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5217 - INSTALL.ubuntu Packages/CPAN notes out of date for Ubuntu 10.04 LTS (Lucid) Regards To+

5 5

some Koha qa-tools
by Mason James 19 Jul '12

19 Jul '12

hi QA-ers i've been working on some qa-tools for Koha, here... https://github.com/KohaAloha/koha-qa-tools they are pretty clever! :) the clever thing about them is they run the qa-tests both before and after a series of commits (using git) they only generate errors for problems introduced by the commits, and nothing else (so, no false-positives on existing errors) they have been saving me much time when qa-testing, and also finding errors in patches that i did not see they are also fast, as they only test the modified files, nothing else so... fast and clever :p the workflow is... 1) cd to your Koha git repo $ cd your/koha.git 2) apply some patch(es) $ git bz apply 4460 3 run QA tests, for last $x patches... $ koha-qa.pl -c 2 - fb11ab9 Bug 4460 - Amazon's AssociateID tag not used in links so referred revenue lost koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/detail.tt koha-tmpl/opac-tmpl/prog/en/modules/opac-readingrecord.tt C4/Auth.pm koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/detail.tt koha-tmpl/opac-tmpl/prog/en/modules/opac-detail.tt koha-tmpl/opac-tmpl/prog/en/modules/opac-readingrecord.tt koha-tmpl/opac-tmpl/prog/en/modules/opac-user.tt - perlcritic-progressive tests... OK - perl -c syntax tests... OK - xt/tt_valid.t tests... OK - xt/author/vaild-template.t tests... FAIL koha-tmpl/opac-tmpl/prog/en/modules/opac-user.tt FAIL the code is currently a little 'hacky' ;) , but functional... (so good enough) cheers, Mason -- KohaAloha, NZ

1 0

Re: [Koha-devel] Release cycle [was: Ubuntu support]
by Paul 19 Jul '12

19 Jul '12

At 03:35 PM 7/18/2012 -0300, Tomas Cohen Arazi wrote: >I've been struggling with I'd be happy to try and assist with this documentation. I struggled with 3.8 on our sandbox (maybe less than Tomas, as it's a i386) and will probably struggle again if/when I put 3.8.x onto a production 686 server. For the record, the Ubuntu LTS release cycle is not quite "pure" 2-year as Tomas suggests below. New LTSs are released every two years, but end-of-life is after five years (e.g. current 12.04 LTS is valid until April 2017.) The 10.04 server (Lucid) is valid until April 2015, and the older 8.04 Heron server is still valid until April 2013 and could probably be dropped (together with 10.10 (Maverick) which was never an LTS.) This Ubuntu cycle has the great advantage of being able to "jump" one LTS, and still have a year of "old" validity before deploying "new". Is there any chance of using a similar "release cycle" as far as LTS is concerned for Koha? I've been trying to follow the emails on this subject, but have problems wrapping my greycells around gits and masters, releases and sub-releases, bugs on a scale from trivial to blocker, enhancements announced as bugs, etc. I realize, of course, that all of you who put in tireless effort on Koha (and I certainly respect and thank you for it), have developed a release cycle that suits your input as efficiently as possible. But also, I have to admit that I'm more used to LTS, stable and "beta" (for whatever values of "at your own risk" they might take) with enhancements clearly differentiated from security updates. Having followed the Koha Users list as far as 3.8 is concerned (and I'm not really suggesting that it's not stable) I'm taking a lot more time than I did with 3.6 to consider putting it into production. And I haven't even looked at 3.6.2-7 because 3.8 was available by the time I got our people trained on 3.6.1 In our production environment (two fairly big servers), the first consideration when looking at updates is stability, whether it's for Apache, SendMail, SQL, OpenOffice, whatever. ROI (cost versus enhancement) comes later. I'd be interested to know, from your (developers') point of view, which version of Koha you consider closest to "Long Term Stable"? Best - Paul At 03:35 PM 7/18/2012 -0300, Tomas Cohen Arazi wrote: >I've been struggling with > >$ dselect --set-selections install_misc/ubuntu.packages >$ dselect install > >pulling i386 packages and trying to break my poor amd64 12.04 PVM, and >started to dig on problems related to Ubuntu support and docs >problems. >The most bugs reported have to do with docs being outdated. And >whether a patch should be applied or not depends on this question: >What Ubuntu versions should we support? > >My vote is for the current LTS revisions only (lucid and precise, the >first being outdated for master i guess, not sure). Their 2-year >release cycle seems to be enough for having a fair recent version of >the required libs. So, this files might need being updated/deleted and >new ones created: > >INSTALL.ubuntu >INSTALL.ubuntu.lucid >ubuntu_maverick.packages (delete or at least rename!) >ubuntu.packages >ubuntu-pkg-check.sh > >I propose: > >INSTALL.ubuntu.lucid >INSTALL.ubuntu.precise >install_misc/ubuntu_lucid.packages >install_misc/ubuntu_precise.packages > >The idea is avoiding confusion. I'd volunteer to help on this task. >Bugs related to this: > >- http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7764 - >INSTALL.ubuntu needs updating >- http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7759 - Use >Koha-Contrib-Tamil to update Zebra data in background > (needs to be documented in the INSTALL.* files) >- http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7858 - >Missing packages from install_misc/ubuntu.packages >- http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8192 - >Update libraries and Missing library in install_misc/ubuntu.packages >- http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5217 - >INSTALL.ubuntu Packages/CPAN notes out of date for Ubuntu 10.04 LTS >(Lucid) > >Regards >To+ >_______________________________________________

3 2

KohaCon13 Voting Closed - Venue Chosen
by Nicole Engard 18 Jul '12

18 Jul '12

Hello all, The voting closed at 3am EST this morning and the tallies are in. I have shared the files (without names) on the Wiki: http://wiki.koha-community.org/wiki/Kohacon2013 The final point totals from the voting are: Reno, NV, USA [Sept or Oct] :: 2256 Ibadan, Nigeria [Jul, Aug, or Sept] :: 1411 Córdoba, Argentina [Jul, Aug, or Sept] :: 1381 The National Capital Region, USA [Oct or Mar] :: 1366 Erie, Pennsylvania, USA [Summer] :: 1344 The voting rules were shared with you all, but here they are again: If you vote for someplace as #1 it gets 5 points, #2 it gets 4 points, and so on. In the end we tally the points to see where the conference takes place. That way if everyone picks one place as #1 but more people pick it as second and third it still might win. So basically if you won't go somewhere no matter what then don't vote for that location and it will get no points from you. And so the numbers above are not the total votes for first place, they are the tallies using the math described above. I did do some checking for duplicates voters. If you voted more than once your final vote was saved and the others deleted. If you left out your email address (which was required and which we used to find duplicates) your vote was deleted. Other than that no modifications were made to the votes. Thanks Nicole C. Engard

2 1

Some suggestions for dashboard
by Paul Poulain 18 Jul '12

18 Jul '12

Hi koha-devel, and mainly Chris_c, http://dashboard.koha-community.org/ is really an interesting tool, that will, I hope, become more and more used ! I've some suggestions: * The "Last 5 sign-off" is less important than "Needs signoff" and "New features recently pushed". It could be in 3rd place * whey does the "Needs signoff" not have the date information ? That would highlight old bugs. * Maybe we could set a red color to "needs signoff" had no activity for more than 1 month? * Why having only 5 for each case ? Would it be possible to have 5, and a link "show more", that would display -say- 20 ? * Bug status could have 2 values the total and the "unmodified since more than 1 month", for example Need Signoff 122 (15 old) Signed off 30 ( 3 old) Passed QA 8 ( 1 old) * Bug status could have colors (green / yellow / red). I would say * signoff <40 green, <80 yellow >80 red * signed off <15 green, <30 yellow >30 red * passed QA <10 green, <20 yellow, > 20 red (for "old", I would say <5 green, <10 yellow >10 red) * random bug = I think the update every 10 seconds is a little bit too often. 30 seconds would be better. and/or display 3 change the oldest one every 10 seconds * put the random bug on top & in the middle, will be more eye-attracting * Important dates = they should be before monthly scoreboard-july * Update "Dashboard" title to "Koha ILS dashboard" * not sure we need the hours on all dates (which timezone is it ? it's not highly readable) * monthly scoreboard = what about having only the 5 first by default, with "show more" option ? * Bug Activity = what about seeing a graph ? listing 5 days and "show more" option ? Note = Chris, if you give me access and some explanations, I can deal with some of these suggestions myself -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 1

Sandbox improved
by Paul Poulain 18 Jul '12

18 Jul '12

Hello Koha users & developers, Irma & Bob, from Calyx sent me a file with some MARC21 records. I just added them on the MARC21 database you can load in sandboxes. So if you choose database 1 (MARC21) when setting up your sandbox, you will have 101 biblios and 130+ items. For more informations: http://wiki.koha-community.org/wiki/Sandboxes -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 2

Giving credit where credit is due
by Jared Camins-Esakov 17 Jul '12

17 Jul '12

Good morning. I have been working on polishing the release notes generator script, and encountered a problematic section: the section of the release notes that thanks libraries which have sponsored developments. In order to make it so that the section can be automatically generated (and to make sure that no one is missed) I propose adding the following to patches which were sponsored by a particular library: Sponsored-by: The Library Unless there are any strong objections, I will create an empty commit on 3.6.x that lists the libraries that sponsored developments in the 3.6.x branch, and starting with 3.6.7 will automatically generate the listing. Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

4 4

Call for News for the July Newsletter
by Daniel Grobani 16 Jul '12

16 Jul '12

Dear Koha Kommunitarians, I'm harvesting news for the July newsletter. Please send me by the 25th anything you think your fellow community members might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two for the gossip/society column about what you're currently working on. And if you know of a go-live not announced on the list, please be sure to let me know about it. Thanks, Daniel Grobani

1 0