hello to all, I have struggel past 3 month to install Koha. Now, my effort seems to be fruitful. From an obidience Windows user, I have become a Linux fans.. thanks to Koha for opening my eyes to Open Source Solutions. Now I am enjoying installing Koha on several Linux Distro. I have eventually faced a similar problems mentioned by many of mailing list User before. I am not a goo programmer or an experience System Analyst. But, maybe the following guidelines can help you out there: 1. Try to upgrade Apache version 1.3.33 to 2.0.xx (.54 If I am not mistaken), as this will help you running Perl Modules and Environment Variables without problems.(It is working for me) You can use dpkg or aptitude to do this. 2. You need CLEAN installation of PERL modules required by KOHA (using CPAN) without any disruption or error message. Also for the YAZ toolkit, which can be obtained from indexdata.dk. If you are using Sarge installation, make sure, you downloads YAZ Toolkit ofr Sarge package*. *Currently, I am using debian SARGE, while current guidelines installing Koha in debian is for woody. So, you need several adjustment for finding right package for Debian Sarge, If you are using Sarge Installation. Thank you and enjoy Koha! --- koha-request@lists.katipo.co.nz wrote:
Send Koha mailing list submissions to koha@lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request@lists.katipo.co.nz
You can reach the person managing the list at koha-owner@lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..."
Today's Topics:
1. To implement koha (javier@ayto-daganzo.org) 2. Re: I need to add a path to @INC for KOHA, how? (Stephen Hedges) 3. Re: I need to add a path to @INC for KOHA, how? (Andro Gagne) 4. Thanks all, but I am no closer to getting KOHA working.... (Marty Jongepier) 5. Z39.50 (javier@ayto-daganzo.org) 6. Shelflist report (David Miner)
----------------------------------------------------------------------
Message: 1 Date: Wed, 04 Jan 2006 00:48:10 +0100 From: "javier@ayto-daganzo.org" <javier@ayto-daganzo.org> Subject: [Koha] To implement koha To: koha@lists.katipo.co.nz Message-ID: <20060103234810.6141.qmail@correo2.acens.net> Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Hello to all: We are implanting koha in a library in Daganzo, a town of España.This project we want it integramente to translate Spanish. We are having problem with script to pass the files tmpl to po in the part of opac. Can you pass somebody the file in format po of opac-tmpl/default/en to be able to translate it? Another problem that we are having is with Z39.50 and at the time of concerning registry marc of other libraries. Me podeis on the matter to pass information of like forming it?
Happy 2006
------------------------------
Message: 2 Date: Tue, 3 Jan 2006 18:58:24 -0500 (EST) From: "Stephen Hedges" <shedges@skemotah.com> Subject: Re: [Koha] I need to add a path to @INC for KOHA, how? To: "Andro Gagne" <apgagne@frontiernet.net> Cc: koha@lists.katipo.co.nz Message-ID:
<32802.65.24.138.126.1136332704.squirrel@webmail.skemotah.com>
Content-Type: text/plain;charset=iso-8859-1
You don't normally need to worry about these environment variables, unless you are running one of the exceptional command-line scripts like bulkmarcimport.pl. The routine Koha functions should be no problem.
When you do have some reason to run a special-use script like bulkmarcimport.pl, you somehow need to tell the script where you installed Koha. My Koha (and koha.conf and modules) may have been installed in a completely different location than yours.
Stephen
Mr. Laurent,
At 09:32 AM 1/3/06 +0100, Henri-Damien Laurent wrote:
Normally, when using a koha script, you need to set two environment variables. PERL5LIB and KOHA_CONF KOHA_CONF contains the path to your koha.conf PERL5LIB the path to your koha
standard install.
You can set them with export command as such : export KOHA_CONF=/path/to/koha.conf export PERL5LIB=/path/to/koha/intranet/modules And then you can launch your scripts.
Thank you for your helpful reply. I understand that the setting of these environment variables is necessary. That makes sense to me, and I don't have any problem with it. What I don't understand is why Mr. Jongepier and I are having this problem in the first place. Either Koha is programmed to set these variables on its own when it is started up, or it isn't. If it is supposed to set these variables when being started, why is it not doing so? I believe I followed the installation instructions very faithfully, so I have reason to expect that Koha will start up properly and set the variables it needs to be set. If Koha is not programmed to set these variables on its own when it is started up, clearly it is my responsibility to set these variables. But if the latter is the case, why didn't the installation instructions tell me this and tell me how the variable setting needs to be done so that Koha's environment variables are set up properly when Koha is started up? (I am referring to the installation instructions that were available at www.kohadocs.org last June.) All I'm trying to do is to understand where the real problem lies so that, hopefully, I can fix the real
who caused the problem in some way--rather than applying what seems like a Band-Aid and not understanding where things went wrong. The Band-Aid approach probably will work for a while, but it is
good a fix as fixing the underlying problem, especially as Koha gets upgraded over time.
I really want to show the museum--and other organizations that cannot afford integrated library systems that have
Andro Gagne said: directories/intranet/modules on a problem--especially if I am the one likely not to be as prices in the 5- or
6-figure range--that Koha can do the job they need to be done. If you can help me understand where the underlying problem is in regard to setting environment variables for Koha, I will appreciate it very much. I would be glad to send any information needed about how I installed Koha to solve this issue. Thank you for your patience and understanding.
Andro P. Gagné P.O. Box 715 Canandaigua, NY 14424
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
------------------------------
=== message truncated === __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com
Hi, you said you are now have installing koha on several linux distro. have you try to install koha on ubuntu linux? if you have, please share your experience with me. Thanks Regards, Wahyu Wijaya H. Amzari Abu Bakar <amzari79@yahoo.com> wrote: hello to all, I have struggel past 3 month to install Koha. Now, my effort seems to be fruitful. From an obidience Windows user, I have become a Linux fans.. thanks to Koha for opening my eyes to Open Source Solutions. Now I am enjoying installing Koha on several Linux Distro. I have eventually faced a similar problems mentioned by many of mailing list User before. I am not a goo programmer or an experience System Analyst. But, maybe the following guidelines can help you out there: 1. Try to upgrade Apache version 1.3.33 to 2.0.xx (.54 If I am not mistaken), as this will help you running Perl Modules and Environment Variables without problems.(It is working for me) You can use dpkg or aptitude to do this. 2. You need CLEAN installation of PERL modules required by KOHA (using CPAN) without any disruption or error message. Also for the YAZ toolkit, which can be obtained from indexdata.dk. If you are using Sarge installation, make sure, you downloads YAZ Toolkit ofr Sarge package*. *Currently, I am using debian SARGE, while current guidelines installing Koha in debian is for woody. So, you need several adjustment for finding right package for Debian Sarge, If you are using Sarge Installation. Thank you and enjoy Koha! --- koha-request@lists.katipo.co.nz wrote:
Send Koha mailing list submissions to koha@lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request@lists.katipo.co.nz
You can reach the person managing the list at koha-owner@lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..."
Today's Topics:
1. To implement koha (javier@ayto-daganzo.org) 2. Re: I need to add a path to @INC for KOHA, how? (Stephen Hedges) 3. Re: I need to add a path to @INC for KOHA, how? (Andro Gagne) 4. Thanks all, but I am no closer to getting KOHA working.... (Marty Jongepier) 5. Z39.50 (javier@ayto-daganzo.org) 6. Shelflist report (David Miner)
----------------------------------------------------------------------
Message: 1 Date: Wed, 04 Jan 2006 00:48:10 +0100 From: "javier@ayto-daganzo.org"
Subject: [Koha] To implement koha To: koha@lists.katipo.co.nz Message-ID: <20060103234810.6141.qmail@correo2.acens.net> Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Hello to all: We are implanting koha in a library in Daganzo, a town of España.This project we want it integramente to translate Spanish. We are having problem with script to pass the files tmpl to po in the part of opac. Can you pass somebody the file in format po of opac-tmpl/default/en to be able to translate it? Another problem that we are having is with Z39.50 and at the time of concerning registry marc of other libraries. Me podeis on the matter to pass information of like forming it?
Happy 2006
------------------------------
Message: 2 Date: Tue, 3 Jan 2006 18:58:24 -0500 (EST) From: "Stephen Hedges" Subject: Re: [Koha] I need to add a path to @INC for KOHA, how? To: "Andro Gagne" Cc: koha@lists.katipo.co.nz Message-ID:
<32802.65.24.138.126.1136332704.squirrel@webmail.skemotah.com>
Content-Type: text/plain;charset=iso-8859-1
You don't normally need to worry about these environment variables, unless you are running one of the exceptional command-line scripts like bulkmarcimport.pl. The routine Koha functions should be no problem.
When you do have some reason to run a special-use script like bulkmarcimport.pl, you somehow need to tell the script where you installed Koha. My Koha (and koha.conf and modules) may have been installed in a completely different location than yours.
Stephen
Mr. Laurent,
At 09:32 AM 1/3/06 +0100, Henri-Damien Laurent wrote:
Normally, when using a koha script, you need to set two environment variables. PERL5LIB and KOHA_CONF KOHA_CONF contains the path to your koha.conf PERL5LIB the path to your koha
standard install.
You can set them with export command as such : export KOHA_CONF=/path/to/koha.conf export PERL5LIB=/path/to/koha/intranet/modules And then you can launch your scripts.
Thank you for your helpful reply. I understand that the setting of these environment variables is necessary. That makes sense to me, and I don't have any problem with it. What I don't understand is why Mr. Jongepier and I are having this problem in the first place. Either Koha is programmed to set these variables on its own when it is started up, or it isn't. If it is supposed to set these variables when being started, why is it not doing so? I believe I followed the installation instructions very faithfully, so I have reason to expect that Koha will start up properly and set the variables it needs to be set. If Koha is not programmed to set these variables on its own when it is started up, clearly it is my responsibility to set these variables. But if the latter is the case, why didn't the installation instructions tell me this and tell me how the variable setting needs to be done so that Koha's environment variables are set up properly when Koha is started up? (I am referring to the installation instructions that were available at www.kohadocs.org last June.) All I'm trying to do is to understand where the real problem lies so that, hopefully, I can fix the real
who caused the problem in some way--rather than applying what seems like a Band-Aid and not understanding where things went wrong. The Band-Aid approach probably will work for a while, but it is
good a fix as fixing the underlying problem, especially as Koha gets upgraded over time.
I really want to show the museum--and other organizations that cannot afford integrated library systems that have
Andro Gagne said: directories/intranet/modules on a problem--especially if I am the one likely not to be as prices in the 5- or
6-figure range--that Koha can do the job they need to be done. If you can help me understand where the underlying problem is in regard to setting environment variables for Koha, I will appreciate it very much. I would be glad to send any information needed about how I installed Koha to solve this issue. Thank you for your patience and understanding.
Andro P. Gagné P.O. Box 715 Canandaigua, NY 14424
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
------------------------------
=== message truncated === __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha --------------------------------- To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.
participants (2)
-
Amzari Abu Bakar -
Wahyu Wijaya H.