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

Current Loan, speaks of money?
by Benedykt P. Barszcz 23 Feb '04

23 Feb '04

HI, I need explanation about Current Loan in opac-user.pl does it pertain to money or to items? thanks Benedict

1 0

Re: [Koha-devel] anyone knows why?
by Bolan Meek 22 Feb '04

22 Feb '04

On Sun, 22 Feb, "Benedykt P. Barszcz" <kb2qzv(a)poczta.wp.pl> wrote: > cvs -f -z3 add 'koha-tmpl/opac-tmpl/default/pl/images' 2>&1 > cvs [add aborted]: cannot make directory CVS in > koha-tmpl/opac-tmpl/default/pl/images: Permission denied Need more info: Do you have permission to create a subdirectory to your current working? cwd? ls -ld .? Do any of ./koha-tmpl, ./koha-tmpl/opac-tmpl, et al. already exist? ls -ld <the directories above>? whoami?

1 0

I need to talk with anyone that has set KOHA on a commercial hosting service....
by COURYHOUSE＠aol.com 22 Feb '04

22 Feb '04

I need to talk with anyone that has set KOHA on a commercial hosting service.... Thanks Ed Sharpe, Archivist for SMECC - - See the Museum's Web Site at www.smecc.org We are always looking for items to add to the museum's display and ref. library - please advise if you have anything we can use. Coury House / SMECC 5802 W. Palmaire Ave. Phone 623-435-1522 Glendale Az 85301 USA CONFIDENZIALE: Questo messaggio e gli eventuali allegati sono confidenziali e riservati. Se vi è stato recapitato per errore e non siete fra i destinatari elencati, siete pregati di darne immediatamente avviso al mittente. Le informazioni contenute non devono essere mostrate ad altri, né utilizzate, memorizzate o copiate in qualsiasi forma. CONFIDENTIAL: This e-mail and any attachments are confidential and may contain reserved information. If you are not one of the named recipients, please notify the sender immediately. Moreover, you should not disclose the contents to any other persons, nor should the information contained be used for any purpose or stored or copied in any form.

1 0

anyone knows why?
by Benedykt P. Barszcz 22 Feb '04

22 Feb '04

cvs -f -z3 add 'koha-tmpl/opac-tmpl/default/pl/images' 2>&1 cvs [add aborted]: cannot make directory CVS in koha-tmpl/opac-tmpl/default/pl/images: Permission denied Benedict

1 0

Koha Wiki Update
by Roger Buck 21 Feb '04

21 Feb '04

Koha Wiki will be off line for approx 24 hours to allow for server maintenance and software update. The koha wiki was orignally thrown together very quickly using a pre-existing, shared mysql database. During the maintenance outage I will export all existing koha data from shared database and create a new, koha only database. I'll provide more detailed information as soon as server upgade is complete. In the meantime, you should be able to view an alternative copy of the koha data here: http://www.saas.nsw.edu.au/saas_wiki/index.php?page=KohaProject Best not to add new data to this database until the new koha wiki comes on line tomorrow. Apologies for any inconvenience. R.

1 0

koha wiki => save impossible
by paul POULAIN 20 Feb '04

20 Feb '04

Hi Roger & al, when trying to submit changes in the koha wiki, i get : *Warning*: gethostbyaddr(): Address is not a valid IPv4 or IPv6 address in */var/www/SAAS.EDU/html/wiki/action/save.php* on line *35* *Warning*: gethostbyaddr(): Address is not a valid IPv4 or IPv6 address in */var/www/SAAS.EDU/html/wiki/action/save.php* on line *56* *Warning*: Cannot modify header information - headers already sent by (output started at /var/www/SAAS.EDU/html/wiki/action/save.php:35) in */var/www/SAAS.EDU/html/wiki/template/save.php* on line *16 *It seems it's saved anyway.* * -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

z3950 search debug
by paul POULAIN 20 Feb '04

20 Feb '04

Hi, I'm working/testing z3950 client at the moment. I've some problems to reproduce the "server has gone away" problem. In fact, I don't succeed at all. It works fine for me (except minor problem rendering UNIMARC records). WHAT I do : * my z3950 server contains 2 servers : INSERT INTO z3950servers VALUES ('z3950.bnf.fr', 2211, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ1456', 'Z3950', 'Z3950_BNF', 'BNF', 1, 1, 1, 'UNIMARC'); INSERT INTO z3950servers VALUES ('bubase.univ-angers.fr', 210, 'ADVANCE', '', '', 'ANGERS', 2, 1, 1, 'MARC21'); * I open a rxvt and launch ./processqueue, after defining PERL5LIB and KOHA_CONF (KOHA_CONF being defined because my dev conf is in /etc/koha-stable.conf file, that is not the default conf) * I type an ISBN, or a title, and I can see in the console : starting loop 4834/23 : Processing isbn=2226075178 at BNF z3950.bnf.fr:2211 ABCDEFGHIJKLMNOPQRSTUVWXYZ1456 UNIMARC (1 forks) 4835/23 : Processing isbn=2226075178 at ANGERS bubase.univ-angers.fr:210 ADVANCE MARC21 (2 forks) 4834/23 : 2 >> 4834/23 : creating and 4834/23 : working on results entry 34 4834/23 : connected to BNF 4834/23 : BNF : 1 records found, retrieving them (max 80) 4835/23 : 2 >> 4835/23 : creating and 4835/23 : working on results entry 35 4835/23 : connected to ANGERS 4835/23 : ANGERS : no records found 4835/23 : bubase.univ-angers.fr:210 search done. 4834/23 : BNF : z3950.bnf.fr:2211 records retrieved 1 SPEED: 1 4834/23 : z3950.bnf.fr:2211 search done. starting loop starting loop starting loop starting loop starting loop 4843/24 : Processing isbn=2715805586 at BNF z3950.bnf.fr:2211 ABCDEFGHIJKLMNOPQRSTUVWXYZ1456 UNIMARC (1 forks) 4844/24 : Processing isbn=2715805586 at ANGERS bubase.univ-angers.fr:210 ADVANCE MARC21 (2 forks) 4843/24 : 2 >> 4843/24 : creating and 4843/24 : working on results entry 36 4843/24 : connected to BNF 4843/24 : BNF : 1 records found, retrieving them (max 80) 4844/24 : 2 >> 4844/24 : creating and 4844/24 : working on results entry 37 4844/24 : connected to ANGERS 4843/24 : BNF : z3950.bnf.fr:2211 records retrieved 1 SPEED: 1 4843/24 : z3950.bnf.fr:2211 search done. 4844/24 : ANGERS : no records found 4844/24 : bubase.univ-angers.fr:210 search done. starting loop I tried 5 differents books, each more than once, without relaunching ./processqueue. and NEVER had "server has gone away". So, does anyone have an idea ? I had one : "maybe i should use daemon-launch.pl script to launch the daemon". I tried, but get : " standard in must be a tty " and I don't know what to do with this message (I tried on TTY1 and got the same error message) Any idea ? -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Next release
by paul POULAIN 20 Feb '04

20 Feb '04

Hi, I will speak of the next releases. My opinion, as 2.0.0 release manager is that the next release should be called 2.0.0, without anything else. It's used in 6 libraries in France, and some others around the world. It's not perfect, but everything works. The DB has not been modified (except for indexes) since a long time. That proves, imho, that Koha 2.0.0 is stable. Except for z3950 client. But i've a customer that pays me to install Koha with a working z3950 client, so i'll work on it until it works fine (hoping it won't need 2 years :-D ) What's next ??? A lot of features are asked, here in France. Some of them may/should have funders in the next few months. Some of them require only a few hours (like the bookshelf improvement i've commited today : done yesterday in the TGV between Paris & Lyon). The french mailing list is quite active since 2 weeks : users ask for improvements. I'll write a summary of their needs next week, probably. I'll put an english version on the wiki. So, what should we put in 2.0.0 and what in 2.2.0 (HEAD branch of CVS) My opinion is : * bugfixes are put in rel_2_0 cvs branch. New releases occurs when an important bugfix is done, or some minors. * Any new translation (chinese, german, spanish...) can be put in 2.0.0. A new release occurs when a new translation is published. * everything new is put in HEAD. * CODE cleaning is done in HEAD, to avoid side effect on buggy clean. I'll begin to clean some things soon i think. BUT : * MINOR improvement, that don't need DB changes, or a really minor one, *can* be backported to rel_2_0 if the 2.0.0 maintainer want to do it. * MAJOR improvements are done in HEAD, for 2.1.x unstable and 2.2.x stable. WHO-DO-WHAT. We have a useless 2.0.0 Release Manager, as the 2.0.0 is stable. We need : * a 2.0.0 Release Maintainer * a 2.2.0 Release Manager. I don't apply as Release Maintainer. Do we have a volunteer around ? I apply as Release Manager for 2.2.0 if other ppl here like this idea. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 3

another problem installing koha with buidrelease tarball
by Benedykt P. Barszcz 20 Feb '04

20 Feb '04

HI, Thank you guys for the help about the mysql problem I mentioned the other day. In fact it was the 'delete from db' and delete from user' issue. Now, I need to know what is going on here: ./misc/buildrelease [I answer questions] a tarball is created in /tmp/. I do a fresh installation of Koha. Everything works but the aqciusition module. I get this in the logs: [Fri Feb 20 11:20:25 2004] [error] [client 127.0.0.1] Premature end of script headers: acqui-home.pl, referer: http://localhost:8080/cgi-bin/koha/mainpage.pl [Fri Feb 20 11:20:25 2004] [error] [client 127.0.0.1] Global symbol "$query" requires explicit package name at /usr/local/koha/intranet/modules/C4/Catalogue.pm line 114., referer: http://localhost:8080/cgi-bin/koha/mainpage.pl [Fri Feb 20 11:20:25 2004] [error] [client 127.0.0.1] Global symbol "$query" requires explicit package name at /usr/local/koha/intranet/modules/C4/Catalogue.pm line 115., referer: http://localhost:8080/cgi-bin/koha/mainpage.pl [Fri Feb 20 11:20:25 2004] [error] [client 127.0.0.1] Compilation failed in require at /usr/local/koha/intranet/cgi-bin/acqui/acqui-home.pl line 10., referer: http://localhost:8080/cgi-bin/koha/mainpage.pl [Fri Feb 20 11:20:25 2004] [error] [client 127.0.0.1] BEGIN failed--compilation aborted at /usr/local/koha/intranet/cgi-bin/acqui/acqui-home.pl line 10., referer: http://localhost:8080/cgi-bin/koha/mainpage.pl The problem did not occur when I first installed koha from the tarball realeased in the sourceforge, by the mantainer. What could be wrong? thanks. Benedict

2 1

reinstalling koha with same error DB
by Benedykt P. Barszcz 19 Feb '04

19 Feb '04

What is this? I did the following: mysql -u root -p mysql After password I was dropped into mysql database. drop database Koha; successfull. DELETE from user WHERE User='kohaadmin'; successful. SELECT * from user; It shows there is no kohaadmin user in it. Now the error below, what can it be? thanks for any hints. CREATING DATABASE Creating the MySQL database for Koha... 0ERROR 1062 at line 1: Duplicate entry '%-Koha-kohaadmin' for key 1 connected to your DB. Checking & modifying it Adding marc_word table... Adding marc_biblio table... Adding bookshelf table...

2 1