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

koha-3.00.00 make fails
by Rick Welykochy 28 Dec '13

28 Dec '13

Hi all, I have downloaded http://download.koha.org/koha-3.00.00.tar.gz and began installing it on Debian/etch (in a Linux vserver environment). 0. FINE: cd koha-3.00.00 1. FINE: perl Makefile.PL 2. FAIL: make : : : Manifying blib/man3/C4::UploadedFile.3pm Manifying blib/man3/C4::BackgroundJob.3pm Manifying blib/man3/opac::opac-dictionary.3pm Manifying blib/man3/serials::member-search.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" fix-perl-path.PL blib /usr/bin/perl "-Iblib/arch" "-Iblib/lib" rewrite-config.PL blib/KOHA_CONF_DIR/koha-conf.xml Bad arg length for Socket::inet_ntoa, length is 0, should be 4 at rewrite-config.PL line 67. make: *** [blib/KOHA_CONF_DIR/koha-conf.xml] Error 255 Any ideas what went wrong and how to fix? Aside: there were a couple of other problems with this "out of the box" debian based install of Koha 3.0 which had to be fixed along the way, e.g. seven missing perl modules and libgd not found. I'll report on the entire process from unpacking to a running Koha/3.00.00 once I get to the end. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

4 5

Adding items in Acquisition 3.2
by Marcel de Rooy 18 Mar '11

18 Mar '11

Hi, The new feature (in Koha 3.2) of adding items in Acquisitions with the framework display is quite promising. It appears however that the framework plugins cannot be activated there. Do I overlook something? Or is anyone still working on this functionality? Regards, Marcel

2 1

Imported MARC notice and Authorities: : inconsistent database
by Frère Sébastien Marie 22 Feb '11

22 Feb '11

Hello, Recently, we have imported a set of notices, from another abbey, in the reservoir. When we create a new examplar using the previous imported notices, the field 700.9 (authority - internal koha number) refering the auth_id isn't updated or removed (still reference the old authority number, in the other catalog). As result, we have an examplar with 700.a (authority name) correct, but with an internal reference wrong (not valid in us catalog). If we search all notices linked with an authority, there is wrong attribution. Next an example. Starting with: - Notices in reservoir: - Title_A / Author_A (auth_id = 1) [from import] - Authority in catalog: - Author_B (auth_id = 1) [created locally] - Notice in catalog: - Title_B / Author_B (auth_id = 1) Next, we create a new examplar based on notice in reservoir, result: - Authority in catalog: - Author_B (auth_id = 1) [created locally] - Notice in catalog: - Title_A / Author_A (auth_id = 1) - Title_B / Author_B (auth_id = 1) (doubt if Author_A added in authorities or not) Now, if search notice attached with Author_B (auth_id = 1): results: - Title_A / Author_A (auth_id = 1) - Title_B / Author_B (auth_id = 1) The database is inconsistent. Where is the problem: - a misused of imported MARC: an option somewhere should be set... - a bug in importing MARC: 700.9 should be cleaned before import... - another possibility ? Currently, no bug report filled, as I don't no if it is a misusing or a bug. Thanks. -- Frère Sébastien Marie Abbaye Notre Dame de La Trappe 61380 Soligny-la-Trappe Tél: 02.33.84.17.00 Fax: 02.33.34.98.57 Web: http://www.latrappe.fr/

3 7

irc down ?
by Paul Poulain 31 Jan '11

31 Jan '11

Hi, It's probably already known, but IRC seems down. Side question: shouldn't we move to a wider irc server (like freenode) ? Wouldn't require katipo help to deal with problems. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

4 5

Using Unicode in Koha
by Prawesh Shrestha 31 Jan '11

31 Jan '11

Hi, I am from Nepal and using Koha Library Management System and very new to it. I want to use Nepali unicode to enter records in the system. Till now I know that its possible while researching on the net. However, eluded with details to make it work. How can I get the details to make it happen? With Regards, -- Prawesh Shrestha Project Engineer --------------------------------------------- Young Innovations Pvt. Ltd. GPO 8976 EPC 241 Pulchowk, Lalitpur, Nepal Tel: +977-01 2291892 http://yipl.com.np info[at]yipl[dot]com[dot]np ----------------------------------------------------

3 2

Development workflow
by Paul Poulain 31 Jan '11

31 Jan '11

Hello koha-devel, The more time passes, the more I think we have a workflow for Koha development that does not work correctly/efficiently/fluently. The rule we have is: * create a branch for the feature * file a bug for it * submit your branch to koha-patches ML * the RM checks that everything apply smoothly on master & ask for QA * someone signs-off the branch/patch * the RM merge the branch. For the maintenance branch, this workflow is perfect and must be secured more and more to avoid any regression. As I see it, there is always someone that can find time to sign-off a patch or 2. As ppl have system live with it i'm sure it's cricital for many ppl to check & double check ! But for the next release/unstable branch this workflow does not work well. Here is a single line of something owen said on the chat today: <owen> paul_p: I would much prefer to be testing your stuff today, but other stuff is taking precedence. God knows i'll be forever thankfull to owen for the work he does. But this sentence reveals something: for most of us, there is always "other stuff taking precedence" :\ BibLibre has submitted many new features 3 months ago. I tried to motivate ppl to get feedback & sign-off. I even have organised an IRC meeting ... where no one came. Those patches includes new features, and requires a lot of work to be tested. 2 weeks ago, I did the same for a bunch of small improvements (and I have many many more pending). Once again, no feedback, except for one very easy-to-test (new images) : signed-off by Nicole & pushed by chris in less than 24H! Those 2 minor events (with owen & nicole) made me realize that it's technically and functionnaly hard & long to test: rebase, drop database, install, file test cases, check the new features,... At KohaCon, liz tested some of those features and said "wow, great, I want this feature for my library !" (I don't remember what it was exactly). The problem is that liz is not a techie woman, and can't test patches by her own. For our images, it was easy for Nicole to test, no need to updatedatabase or anything complex, just reach the itemtypes.pl page check the images are here. Easy for a librarian ! Other point: dependancies between new features. Let me take an example: Templates on those devs relies on html::template. Chris is working on moving everything to Template::Toolkit. Once he consider it's ready, he should submit for QA, as for every new features. Suppose no-one sign-off. And suppose someone sign-off, there are 2 options: * move master to T::T when it's signed-off. What happends with other branches not merged ? they can't be merged anymore, they have to be rewritten. wow, I can't imagine that something we've submitted for QA 3 months ago has to be rewritten because no-one took care of it ! * wait until those branches are merged. Two major problems here: the release date won't be respected, and we have switched again to feature based release. Or 3.4 will be released on time, but won't contain many things all those great features that are live in all our libraries since months. The second problem is that other devs are on the way. They still rely on H::T as master is based on that. Switching to T::T will cause problems for those branches later. well, I think that none of those solutions is a correct one. I can take an other example: the analytics record feature may/will probably overlap functionnaly with the new features we have submitted for cataloguing (not sure, but i think so). Suppose our cataloguing branch is integrated in 2 weeks. it has been submitted 3 months ago. It means our indian colleagues will have to rebase & face problems to get their analytical record branch working. If our branch had been merged quickly, they would have had 3 more months to deal with it. Our actual workflow, causes a lot of overhead ! And -worst- I don't think it improves the stability & security: there are merge problems that are difficults to detect. It means that any test done on analytical records would have to be done again if our cataloguing branch is merged : more work, more pain. And the later a branch is merged, the smaller the time to find a problem. My main conclusion is that we are not a large enough community to deal with testing/validating/merging new features in a short timeline. So I think we must change the way we integrate new features. The general idea being: remove the sign-off lock on the workflow. Here is a proposal: Let's go back to the timeline: we plan to release a version every 6 months. We could have a window of, say 4 months. During those 4 months a feature can be included if : 1- the submitter provides something that applies on master (ie: it's technically valid) 2- no-one object in 2 weeks (or 3, or 4, or defined by the RM when the branch is submitted) It put more pressure on others to test quickly, and don't put pain on parallels/parallelizing developments. Once a branch is merged if there is a problem, then everybody should see it, and it will be fixed ! Then, for 1 month, any new feature can be applied only if a newly submitted branch is approved/signed-off (less than 2 months to detect a problem in a new feature is a must-have) Then, feature freeze, 1 month debugging and translating. I know it is a big change in the workflow, but the actual one is not working well, so, we have to find another one. I humbly request to have this question being put on the next irc agenda (which does not mean you should not also start a thread here, of course) PS: pls don't say i'm wrong and the workflow works well. Having branches submitted 3 months ago, getting no feedback, and planning to have a release in less than 3 months, can't be considered as something working well. Friendly. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

8 20

Zebra issues
by Tiago Murakami 30 Jan '11

30 Jan '11

Hi, I Installed Koha 3.2.2 by koha-common debian package and it works very well. But, when I restart the server, the zebra stop works. I try koha-start-zebra (instance) but don´t work Anybody can help me? -- Tiago Murakami Librarian Brazil

2 2

utf8 in labels pdf -- kernel of a solution
by Reed Wade 30 Jan '11

30 Jan '11

I was poking around at bug 2246 for some reason and thought it might be more fun to step back a bit. The result is a perl fragment that does the basic work of creating a pdf which has a barcode and text in Greek, Cyrillic, all the latins, Japanese, Thai, Hindi and Gujarati (I'm not conversant in most of those languages so I might have some silly mistakes there) all on one page. It uses PDF::API2 instead of PDF::Reuse. If you're curious, have a look at http://reedwade.net/koha/labels/ for the perl script and the pdf output. The enabling feature of interest is the ability in PDF::API2 to build a font from a set of ttf fonts and assigning different unicode code pages (or ranges) for each. It might be possible to rejigger C4/Creators/PDF.pm to use PDF::API2 instead of PDF::Reuse. This is something I predict I will not have time to pursue further anytime soon -- I'm hoping someone else might enjoy that? -reed

2 1

make test fails on BackgroundJob.t
by Koustubha Kale 28 Jan '11

28 Jan '11

Hi All, I am doing a dev install with a fresh git clone on a new machine. make test fails with following.. Test Summary Report ------------------- t/BackgroundJob.t (Wstat: 65280 Tests: 1 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 8 tests but ran 1. Files=99, Tests=6821, 53 wallclock secs ( 1.57 usr 0.24 sys + 26.95 cusr 2.46 csys = 31.22 CPU) Result: FAIL Failed 1/99 test programs. 0/6821 subtests failed. make: *** [test_dynamic] Error 255 Looking back on the make test output I see t/BackgroundJob.t ................... DBD::mysql::db selectrow_array failed: Table 'kohadev.systempreferences' doesn't exist at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Context.pm line 480. DBD::mysql::db selectrow_array failed: Table 'kohadev.systempreferences' doesn't exist at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Context.pm line 480. t/BackgroundJob.t ................... 1/8 DBD::mysql::db selectrow_array failed: Table 'kohadev.systempreferences' doesn't exist at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Context.pm line 480. Use of uninitialized value $timeout in pattern match (m//) at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Auth.pm line 606. DBD::mysql::db selectrow_array failed: Table 'kohadev.systempreferences' doesn't exist at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Context.pm line 480. DBD::mysql::db selectrow_array failed: Table 'kohadev.systempreferences' doesn't exist at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Context.pm line 480. OPAC Install required, redirecting to maintenance at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Auth.pm line 560. # Looks like you planned 8 tests but ran 1. t/BackgroundJob.t ................... Dubious, test returned 255 (wstat 65280, 0xff00) Failed 7/8 subtests Can someone please tell me whats going on here? PS : And I also see a bunch of " DBD::mysql::db selectrow_array failed: Table 'kohadev.systempreferences' doesn't exist at /home/kk/kohaclone/blib/PERL_MODULE_DIR/C4/Context.pm line 480." lines in the make test output. I can login to the kohadev database with the credentials I am supplying perl Makefile.PL Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

2 2

Official Koha Newsletter: Volume 2, Issue 1: January 2011
by Nicole Engard 27 Jan '11

27 Jan '11

Please read the newsletter online for live links: http://koha-community.org/koha-newsletter-volume-2issue-1-january-2011/ Official Koha Newsletter (ISSN 2153-8328) Volume 2, Issue 1: January 2011 Table of Contents * Koha Developments o RFC Roundup: Members/Patrons o Koha 3.2.3 is now available * Koha Libraries o 7 Public Libraries in Pampanga Receive Koha Computers o National Folk Archive in the UK Launches Online Catalog * Koha Events o OS Academy a big success for Koha o KUDOS Conference in May Koha Developments RFC Roundup: Members/Patrons by MJ Ray The following Patrons management improvement ideas have Requests For Comments listed on the Koha Community Wiki. If you have suggestions you could make about these topics, please add comments to the relevant page by logging in and clicking the “Edit” tab at the top of the page. Alternatively, you could start a discussion on the email list or web forum. * Calculate fines in days debarred RFC o Koha 3.0 lets the library define fines in money only. Some libraries needs to be able to set “debarred” fines. When a patron returns books lately, he is debarred for some days. * Enhancements to debarred patron o Gonenoaddress, lost or debarred are currently just toggle choices. Enhancements proposed include adding a comment field to each choice and adding an expiry date for debarring. * Duplicate card button o This feature would add a new button to duplicate a patron card. A new form with the duplicated values will open up and when the librarian puts the cursor on a field, the value will be erased ready to write the new value. Then the librarian can save the new card. * Enhancements to the display of extended patron attributes in circ o This RFC proposes having some extended attributes display in circ/circulation.pl and jumping straight to the patron details page if there is only one match for a patron search. * Fines Tab o Redesign the fines tab to allow partial payment and record/show more information about fines, such as the librarian taking the fine, the transaction time and payment method. * Patron Reading record management RFC and Patron self-managing privacy RFC o The laws in some countries requires that the library cleans the reading record after some time. These new features would let the user himself decide what to do with the reading record. The current behaviour will be the initial default and changed through a system preference. ** Please Contribute! ** Please, if you have any feedback or encouragement for any of the above, follow the link and add comments, or start a discussion. Koha 3.2.3 is now available by Chris Nighswonger It is with pleasure that I announce the release of Koha 3.2.3. The package can be retrieved from: http://download.koha-community.org/koha-3.02.03.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.03.tar.gz.MD5 http://download.koha-community.org/koha-3.02.03.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.03.tar.gz.sig Release notes for 3.2.3 are below the fold. Come and get it! Read more. Koha Libraries 7 Public Libraries in Pampanga Receive Koha Computers by Pampanga PIO City of San Fernando – The National Library of the Philippines (NLP) turned over seven Koha computer units to seven public libraries in the province in ceremonies held recently at the Pampanga Provincial Library. Read More. National Folk Archive in the UK Launches Online Catalog by Elaine Bradtke The first collection of the Vaughan Williams Memorial Library catalogue has been launched into cyberspace: http://catalogue.efdss.org. More on this story can be found on WorldCentralMusic.org. Koha Events OS Academy a big success for Koha by Chris Cormack Over the last 2 weeks Catalyst has been running a pilot of an ‘Academy’ for high school age students. I was very happy to be a part of what, in my opinion, turned out to be a very well run and most worthwhile exercise. During the first week the students were treated to tutorial sessions, including installing ubuntu on their laptops, using git, perl, php, postgresql, configuring a server, copyright, licenses, freedom, community, graphics (inkscape & the gimp), html css and javascript. Quite a list now I see it all written down. Read More. KUDOS Conference in May by David Schuster Put May 2 and 3, 2011 on your calendars for the KUDOS conference to be held in Madison, Wisconsin we are finalizing the venue. More information on transportation and housing to come. This will be a conference for and by users of Koha in collaboration with vendors that support or interact with Koha. We are hopeful that this conference will be a low cost/no cost option with the help of sponsorships from vendors and libraries. We are looking for volunteers to serve on the planning and program committees. If you are interested in helping out, please let me know. We need to get to work on this right away! This is NOT going to be a KohaCon and at this time no Hackfest is being organized. Newsletter edited by Nicole C. Engard, Koha Documentation Manager. Please send future story ideas to me.

1 0