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

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

29 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

Can't call method "append_fields"
by constantine 13 Oct '09

13 Oct '09

Yes, the previous problem was solved, indeed... I do not understand why I have so many problems installing koha,.. maybe the last years I was too used to Joomla! installations :D So the challenging koha that its concept I so much admire and embrace makes me face another problem. Trying to add a MARC record, (I retrieved its data from a z30.50 server, but that does not matter, I think) and then I am getting an error page (http://localhost:8080/cgi-bin/koha/cataloguing/additem.pl) Its contents are: " Koha error The following fatal error has occurred: Can't call method "append_fields" on an undefined value at /usr/local/share/perl/5.10.0/MARC/File/SAX.pm line 95. at /usr/local/lib/perl/5.10.0/XML/LibXML/SAX.pm line 64 at /usr/local/share/perl/5.10.0/MARC/File/XML.pm line 443 Apache Server version: Apache/2.2.9 (Debian) Server built: Jun 21 2008 10:35:35 Koha 3.00.00.094 Koha DB 3.0000094 MySQL mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 OS Linux sangre 2.6.25.9xx6-costis07 #1 SMP PREEMPT Wed Jul 2 02:35:38 EEST 2008 i686 GNU/Linux Perl 5.010000 " The laste contens of /var/log/koha/koha-error_log are [...] [error] [...] [...] addbiblio.pl: INDEXING :orignew at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :1 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :ocip at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :20 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :y-gencatlg at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :ddc at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :SR at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :pc15 2006-07-19 to SSCD at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :jp00 2006-07-26 CIP recd at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :jp20 2006-07-26 to subj at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :jp03 2006-07-26 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :aa05 2006-07-27 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :1 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] addbiblio.pl: INDEXING :1 at /usr/share/koha/lib/C4/Biblio.pm line 2319., referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [debug] mod_deflate.c(619): [...] Zlib: Compressed 37993 to 5966 : URL /cgi-bin/koha/cataloguing/additem.pl, referer: http://localhost:8080/cgi-bin/koha/cataloguing/addbiblio.pl?biblionumber=0&… [...] [error] [...] [...] additem.pl: Can't call method "append_fields" on an undefined value at /usr/local/share/perl/5.10.0/MARC/File/SAX.pm line 95. at /usr/local/lib/perl/5.10.0/XML/LibXML/SAX.pm line 64, referer: http://localhost:8080/cgi-bin/koha/cataloguing/additem.pl?biblionumber=1&fr… [...] [error] [...] [...] additem.pl: at /usr/local/share/perl/5.10.0/MARC/File/XML.pm line 443, referer: http://localhost:8080/cgi-bin/koha/cataloguing/additem.pl?biblionumber=1&fr… What could I do to solve this problem? Tsardounis Constantine http://costis.name _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

2 1

Authority in Koha 3 (English - Unimarc - NoZebra)
by Zeno Tajoli 28 Feb '09

28 Feb '09

Hi to all, I have found a but into installer data for Unimarc / English language. I'm using a NoZebra setting and I think this option is importan for this bug. The setup of Authority is based on the file installer/data/mysql/en/marcflavour/unimarc/mandatory/authorities_normal_unimarc.sql But this definition gives problems, see my e-mail "Problems on working with authority" in koha general list, 05 Jun 2008 09:14. A correct defintion is the frence definition. Probably the main problem is to insert authtypecode = '' into all records of tables auth_tag_structure and auth_subfield_structure. I think that the frence defintion could be good also for English Unimarc definition. My authority defintion (a transaltion of franch definition into english) is attached to this mail. Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @) _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

2 1

Problems with diacritics
by Rodríguez, José L. 22 Nov '08

22 Nov '08

Good morning, I'm a new member in this list. I,ve installed koha-3.00.00 and it works perfectly. But I have a problem with diacritics. In cataloguing, when I put a character whith diacritic mark (á, é ...) or the letter ñ, I get the next error The following fatal error has occurred: Can't call method "fields" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 193. Apache Server version: Apache/2.2.3 Server built: Jan 15 2008 20:33:41 Koha 3.00.00.107 Koha DB 3.0000107 MySQL mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (x86_64) using readline 5.0 OS Linux sanmillan.loading.es 2.6.18-028stab057.4 #1 SMP Fri Aug 1 10:47:59 MSD 2008 x86_64 x86_64 x86_64 GNU/Linux Perl 5.008008 The mysql, according to Joshua Ferraro http://wiki.koha.org/doku.php?id=encodingscratchpad is correct: mysql> show variables where variable_name LIKE "character_set%" OR variable_name LIKE "collation%"; +--------------------------+----------------------------+ | Variable_name | Value | +--------------------------+----------------------------+ | character_set_client | utf8 | | character_set_connection | utf8 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | utf8 | | character_set_server | utf8 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | | collation_connection | utf8_unicode_ci | | collation_database | utf8_unicode_ci | | collation_server | utf8_unicode_ci | +--------------------------+----------------------------+ 11 rows in set (0.00 sec) My question is: Which is the problem? Should I change the DBD::mysql configuration to enable utf-8? Thanks in advance. ---------- José Luis Rodríguez System Librarian Real Biblioteca - Patrimonio Nacional Palacio Real. C. Bailén, s.n. E28071 Madrid Tel. +34 914548700 #7582 Fax +34 914548867 http://www.realbiblioteca.es ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/

5 6

RFC: New System Preference to Determine which 'Types' and associated icons to display in advanced Search
by Joshua Ferraro 24 Oct '08

24 Oct '08

Hi all, It seems like every library has a different definition of what they want to display as 'Type' limits in the advanced search area. The API is currently flexible to support any defined indexes, but customizing this beyond the default itemtypes currently requires editing of the advsearch.tmpl templates -- not horrible, but still kinda annoying. I propose a new syspref that allows the user to specify either 'itemtypes' (default) or any codes from authorised_values to be the limits in place of itemtypes (so for example, ccode). This would allow every library to define their own authorised-values, and then use those as search limits in advsearch.tmpl, without any template modifications. It's a fairly trivial addition, and if we default to itemtypes, won't affect any existing Koha installations. Thoughts? Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

4 4

RFC 3.2 - general hold request changes
by Galen Charlton 23 Oct '08

23 Oct '08

Hi, I've already sent out a couple of RFCs about hold requests and friends, and will be sending out some more that relate to specific customer projects for LibLime, but I wanted to toss out a few ideas for general improvement. A large number of bugs have been turned up recently, most of which were postponed to 3.2, so I think the module is in need of some attention beyond the specific enhancements to be proposed. First, the reserves table needs at least one more column to handle item-level requests properly. Right now, reserves.itemnumber serves two purposes: (a) identifying the requested item if the hold is item-level and (b) identifying the item selected to fill a title-level request. This is a problem because it can be hard to distinguish between bib- and item-level requests, and impossible to do so once the request is filled and the item is waiting on the hold shelf. I propose to replace reserves.itemnumber with two columns: requested_itemnumber (NULL for bib-level requests, non-NULL otherwise) supplied_itemnumber (non-NULL once the request is filled) During a version upgrade, the value of reserves.itemnumber would be moved to requested_itemnumber if the priority > 0, and to supplied_itemnumber if the priority is 0. This is not a perfect heuristic, as a filled item-level request should set both columns, but I'm not sure we can do much better. Second, i think the reserveconstraints table needs to be removed. It appears to date to a time when a biblio could have more than one bilbioitem, but now that the relationship is one-to-one, it cannot serve its original purpose of limiting a request to only specific formats attached to a bib. Removing reserveconstraints would leave Koha supporting bib-level and item-level requests. If something in between bib-level and item-level is still needed, I suppose that it would have to be based on selecting which item types are suitable for filling a request on a given bib - for example, if the library attaches codex and audiobook items to the same bib and gives them different item types, reservecontraints (or its successor) might contain a list of item types. Third, since larger Koha libraries can have hold request queues a couple hundred patrons long or longer, I'm going to experiment with ways of managing the priority value so that it is possible to fill hold requests without having to touch every request in the queue, both to aid performance and to possibly avoid bugs where multiple requests for a given bib have the same priority. Fourth, I want to add an auto_increment reserve_id column to reserves to give us an opaque request ID to simplify FK relationships with tables such as the successor to reserveconstraints and additional tables that we may need as we extend the request system to handle recalls and other types of requests. Fifth, I want to do some work with C4::Reserves to cleanup the FIXMEs, improve the POD, and add functions to separate handling when items can be requested versus when they are available to fill hold requests. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

2 1

Installing 3.0 on FreeBSD - Web Installer Errors
by Thomas Sewell 15 Oct '08

15 Oct '08

I've been struggling to get Koha 3.0 installed on FreeBSD 7.0. I know, a glutton for punishment, right? After wading through the installation process (including installing additional cpan modules and rewriting the installed sample koha-conf.xml and koha-httpd.conf files to use the right file paths, since the installer didn't seem to configure them based on what the makefile used), I've finally run into an issue that I can't find enough information to solve. My understanding is that the web installer is supposed to install the tables into the database. At least, there is nothing in the koha database at this point. When going to http://intranet.example.net:8000/cgi-bin/koha/installer/install.pl I get the following html message: production mode - trapped fatal error And the following lines in koha-error_log: [Thu Sep 25 17:28:22 2008] [error] [client 63.230.9.45] [Thu Sep 25 17:28:22 2008] install.pl: DBD::mysql::st execute failed: Table 'koha.language_subtag_registry' doesn't exist at /usr/share/koha/lib/C4/Languages.pm line 178. [Thu Sep 25 17:28:22 2008] [error] [client 63.230.9.45] [Thu Sep 25 17:28:22 2008] install.pl: DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/C4/Languages.pm line 179. [Thu Sep 25 17:28:22 2008] [error] [client 63.230.9.45] [Thu Sep 25 17:28:22 2008] install.pl: DBD::mysql::db selectrow_array failed: Table 'koha.systempreferences' doesn't exist at /usr/share/koha/lib/C4/Context.pm line 479. [Thu Sep 25 17:28:22 2008] [error] [client 63.230.9.45] [Thu Sep 25 17:28:22 2008] install.pl: Use of uninitialized value in string eq at /usr/share/koha/lib/C4/Context.pm line 45. [Thu Sep 25 17:28:22 2008] [error] [client 63.230.9.45] [Thu Sep 25 17:28:22 2008] install.pl: Use of uninitialized value in string eq at /usr/share/koha/lib/C4/Context.pm line 45. [Thu Sep 25 17:28:22 2008] [error] [client 63.230.9.45] [Thu Sep 25 17:28:22 2008] install.pl: Can't call method "id" on an undefined value at InstallAuth.pm line 278. I can connect to mysql using the information in koha-conf.xml: `mysql -u kohaadmin --port 3306 --host localhost -p koha` connects fine. I have p5-DBD-mysql-4.006 installed (among other things). On a possibly unrelated issue, when running: /usr/local/bin/zebrasrv -f /etc/koha/koha-conf.xml All I get is: 17:39:54-25/09 [fatal] Unknown element 'include' in config /etc/koha/koha-conf.xml I'm currently stuck on both of those, so any help or suggestions would be appreciated. Thanks, Thomas

4 4

error when adding vendor
by mallikarjun dora 13 Oct '08

13 Oct '08

Dear ALL Koha error The following fatal error has occurred: Undefined subroutine &main::AddBookseller called at /usr/share/koha/intranet/cgi-bin/acqui/updatesupplier.pl line 92. Apache Server version: Apache/2.2.8 (Linux/SUSE) Server built: Jun 6 2008 23:42:07 Koha 3.00.00.107 Koha DB 3.0000107 MySQL mysql Ver 14.12 Distrib 5.0.51a, for suse-linux-gnu (i686) using readline 5.2 OS Linux susekoha 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux Perl 5.010000

3 2

RFC 3.2: stop copying item data to MARC and MARCXML
by Galen Charlton 01 Oct '08

01 Oct '08

Hi, Currently, item record data exists both in the items table and as MARC fields in the bib record (in biblioitems.marc and biblioitems.marcxml). The MARC serialization of the item record is controlled by the MARC framework, and unless one wants a maintenance headache, the same mapping of item fields to MARC subfields must be used for all frameworks. This has several deleterious effects: * updating an item record (e.g., in circulation), forces the ISO 2709 and MARCXML versions of the bib record to be recreated. This is an expensive operation, and if a bib record has several hundred items a checkout or return can take several seconds (or longer) to complete. * If a bib has a large number of items, the ISO 2709 version can go over the maximum length - see bug 2453. * unless one makes a special effort, one is stuck with the same MARC item mapping for both import and export. Some libraries need to import bib records from more than one source and don't always have the ability to dictate that their Koha item field mapping be used by the record supplier. * maintaining two versions of the same data can and has led to bugs. * changing the item field mapping requires one to change Zebra (and NoZebra) index definitions. * this is a denormalization of the database schema, and one that doesn't provide any performance gains. Consequently, I propose the following changes, in order of priority: 1. Take item data out of biblioitems.marc*. Instead, whenever item records need to be embedded in a MARC bib record (primarily during Zebra indexing or record export), do it on the fly. If a bib record has lots of items, this will still be an expensive operation, but it will take place in a batch job or indexing daemon. 2. Separate the item field mapping from the rest of the MARC framework. Allow multiple item field mappings, each identified by a code, and add the ability to specify a mapping to be used during record import, export, or indexing. 3. Switch to Zebra's DOM filter and supply item data for indexing outside of the MARC bib record; instead, define an XML schema to wrap bib, item, and summary records without force the last two to be embedded in the MARC. This is similar to an idea that I believe Tümer Garip proposed back in 2006. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

3 6

koha code cleaning bug?
by Marc Chantreux 01 Oct '08

01 Oct '08

hello all, the code that ends this email comes from zebra_rebuild.pl. It can be rewritten as: for('',qw( lock register shadow tab key )) { next if -d; $created_dir_or_file++; system("mkdir -p $authorityserverdir"); print "Info: created $authorityserverdir/$_"; } That is not a bug but it is currently written makes the things harder to read and maintain and it discourages to provide a patch to improve the code(imho). I would like to provide a patch to clean this code. This code is not the only one and so i wonder if the koha communauty wants to have this kind of patch. I also wonder how to do this because of the "fill a bug first" policy. It can be possible to create a "code cleaning" bug that will stay unfixed and our patches can be related to this one. regards, unless (-d "$authorityserverdir") { system("mkdir -p $authorityserverdir"); print "Info: created $authorityserverdir\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/lock") { mkdir "$authorityserverdir/lock"; print "Info: created $authorityserverdir/lock\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/register") { mkdir "$authorityserverdir/register"; print "Info: created $authorityserverdir/register\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/shadow") { mkdir "$authorityserverdir/shadow"; print "Info: created $authorityserverdir/shadow\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/tab") { mkdir "$authorityserverdir/tab"; print "Info: created $authorityserverdir/tab\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/key") { mkdir "$authorityserverdir/key"; print "Info: created $authorityserverdir/key\n"; $created_dir_or_file++; ... -- Marc Chantreux http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc

9 24