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

comments on bug #8 at bugs.koha.org
by Tonnesen Steve 24 Jun '02

24 Jun '02

The installer.pl in rel-1-2 adds the following directive to the apache config: TransferLog logs/koha-access_log common This caused an error in my installation because the second parameter "common" isn't allowed with the TransferLog directive. My reading of Apache's documentation states that the CustomLog directive is the one that allows this second parameter. Was this a typo? Can I remove the "common" from this line? Also, with my install, relative paths are placed under /etc/apache, which would be a strange place indeed for logfiles, even if the apache user could write there. My proposal is to search for an ErrorLog directive in httpd.conf and use the same directory for the koha logs. If there is no ErrorLog directive, it will default to the logs/koha-access_log value. Steve.

1 0

Manual Release Candidate Testing
by Tonnesen Steve 24 Jun '02

24 Jun '02

I've started a document on the wiki to list the things that should be manually tested on a release candidate. It's not complete, and I'm open to additions. What I'd like is a checklist that testers can go through. I'm thinking of maybe making it a cgi script so that it can direct testers to koha.bugs.org to fill in bug reports automatically, or even just email bug reports in directly. Steve.

1 0

Bugzilla
by Tonnesen Steve 24 Jun '02

24 Jun '02

I've started using Bugzilla for reporting bugs with Koha. I'd like to propose that we use bugs.koha.org for reporting _all_ bugs with Koha. Chris, I think we need to add some new components: Installation Circulation Members Reports Database And maybe add CVS as a version for reporting bugs against the current main branch? What about e-mail notifications of bug reports? I can't find a way to have bug reports e-mailed to me as they come in. Steve Tonnesen

1 0

/admin/ scripts and "Add New Member" graphic
by Tonnesen Steve 24 Jun '02

24 Jun '02

Is the "Add New Member" graphic that is used in all of the admin scripts a bug? Steve.

2 1

Re: [Koha-devel] the test bed is ready! - Mitel
by COURYHOUSE＠aol.com 24 Jun '02

24 Jun '02

Where is the best place to download the latest 1.2.x fixed most current to test? Ed

3 2

How can I contriute page
by Rachel Hamilton-Williams 24 Jun '02

24 Jun '02

Hi all http://koha-edit.katipo.co.nz/contribute/index.html I've seriously changed the how can I contribute page to specifically ask for help with particular projects/functionality. I'm keen to hear wether it is too "brash" or foward, wether there are really important things I've missed off (I got the suggestions from the roadmap and sourceforge), and wether the suggested time to do the things is close. Cheers Rachel _____________________________________________________________ Rachel Hamilton-Williams Katipo Communications WEBMISTRESS ph 021 389 128 or +64 04 934 1285 mailto:rachel@katipo.co.nz PO Box 12487, Wellington http://www.katipo.co.nz New Zealand Koha Open Source Library System http://www.koha.org

2 1

RE: Koha 1.2.1
by Nicholas Rosasco 24 Jun '02

24 Jun '02

> -----Original Message----- > From: koha-admin(a)lists.katipo.co.nz > [mailto:koha-admin@lists.katipo.co.nz]On Behalf Of Pat Eyler > Sent: Friday, June 21, 2002 7:58 PM > To: Jeff Williams > Cc: koha(a)lists.katipo.co.nz; koha-devel(a)lists.sourceforge.net > Subject: Re: [Koha] 1.2.1 > > > On Sat, 22 Jun 2002, Jeff Williams wrote: > > > Pat > > > > I am willing to look at producing a Windows Distribution that will > > install MySQL, Perl, Apache. > > > > This would work on win98/ME/2000/XP. > > > > Wow, this would be great! A couple of quick issues: > please make sure that any changes to the Koha core system are checked > back into CVS and are coordinated with the release managers > the code is under the GPL, while the installer needn't be (just the > koha software itself), it would be nice to keep it all under the > same license so as not to confuse things > it would be best to avoid adding additional requirements, please let us > know what if any additional requirements will be needed so that they > can be added to the documentation > > > I am also considering producing a windows client for Koha. Would there > > be interest here??? > > "Client"? I'm not sure exactly what he means -- I'm assuming he means the circ tools. I recommend we direct this guy to the various chunks of Perl code we have floating around. There are platform independent choices for GUIs, and I really think we should be using them for at least one of the circ systems -- I'd suggest > What programming language would you be developing in? > > > Could also have a windows forum area at > > http://schools.hardsoft.com.au/forums > > > > Sure, what would people need in order to make use of it? > > > > > Regards > > > > Jeff Williams > > HardSoft Solutions > > Australia > > ----- Original Message ----- > > From: "Pat Eyler" <pate(a)eylerfamily.org> > > To: "Pete Dubler" <pete(a)dublerfamily.com> > > Cc: <Koha-devel(a)lists.sourceforge.net>; <kohabiz(a)eylerfamily.org> > > Sent: Saturday, June 22, 2002 1:47 AM > > Subject: Re: [Koha] 1.2.1 > > > > > > On Fri, 21 Jun 2002, Pete Dubler wrote: > > > > > Pat, > > > > > > It would be awesome to have Koha come out as an rpm for redhat > > > installations. We've had packages for... ask the list who did them, I can't recall who made them. Might've been Steve? > > We would very much like people to produce pakages (.rpm, .deb., .pkg, > > .lpp, or whatever) which we could put up in a contrib area. This is something I think we can learn to automate... a fair amount of effort/research will be necessary, but this is a good area to "recruit" around, as the problems are widely applicable. I assume you've seen the commentary about the growing aggravations of things like RPM lately? > > We would also like to see turnkey koha systems (either a CD > that can be installed on a blank system or a full blown koha server). > > > > I think that these last two bits are excellent roles for koha support > > company to fill. It could give you a nice product and some good > > postioning. I concur -- especially in light of the fact there is no "one way" to install Koha. This

2 1

translations of Koha
by COURYHOUSE＠aol.com 24 Jun '02

24 Jun '02

How is the translation process being done? Is there one central message file? It would be ackward to have many versions in many languages having to be kept up to date.. if the text messages are not in just a central message file now might be the time to think about doing it thus. Ed Sharpe archivist for SMECC

4 3

Re: [Koha] 1.2.0 Problems
by User genjimoto 24 Jun '02

24 Jun '02

> On Fri, 21 Jun 2002, ed sharpe wrote: > > Ed, this would be a wonderful place to get to. It will take time (and > some $$$) to do so though. > (or someone to pay us to pay staff to do do it). oh.. Where do i get a koha testing job? > We'll also need to build > a test harness that we can use to verify that the install went as >planned. Test harness? > Once those are handled, it will be important to account for >differences in > the way some tools get installed. (How many ways can apace be >installed > on a server?) > > Given all of the difficulties, I hope that this is one area that emerging > koha support companies can/will take on. I also hope it is an area where > libraries (or other interested parties) will be willing to step up and > commit resources. A koha support business... hmm.. how would i create one? > > > > what needs to be done is to determine which environments this should be I > > suppose. > > > > We could build a wishlist, but since we're talking about volunteers, I > think we're going to end up supporting whatever people are willing to work > on (probably Red Hat and Debian at first), or people are willing to pay > people to work on (I'm not sure what systems fall into this category). > > > -pate > > > ed sharpe archivist for smecc > > ----- Original Message ----- > > From: "Pat Eyler" <pate(a)eylerfamily.org> > > To: <COURYHOUSE(a)aol.com> > > Cc: <koha(a)lists.katipo.co.nz>; <Koha-devel(a)lists.sourceforge.net> > > Sent: Friday, June 21, 2002 7:20 AM > > Subject: Re: [Koha] 1.2.0 Problems > > > > > > > On Fri, 21 Jun 2002 COURYHOUSE(a)aol.com wrote: > > > > > > > I think there needs to be tighter Quality control on the releases. > > > > > > This sounds like a good challenge for us to take up. We're working on > > > quality control, believe it or not ;). the 1.2 release series mark the > > > first non-katipo releases, which mean that there will be a bit of a > > > learning curve for us all. Hopefully as we crest theat curve, you'll be > > > seeing things improve (note for example the 1.2.1 release, coming soon, > > > that is undergoing additional testing prior to its release). > > > > > > Beyond this, it would be nice if people who where willing to test > > > pre-releases would sign up on the devel list. We announce the releases > > > and make release candidate (RC) tarballs to that list (The 1.2.0 release > > > had three RC tarballs before we got to the release.) > > > > > > If anyone else has thoughts about how we can improve the quality of > > > upcoming releases, I'd love to hear them. > > > > > > -pate > > > > > > > > > > > > > > Ed Sharpe archivist for SMECC > > > > > > > > > > > > > Subj:Re: [Koha] 1.2.0 Problems > > > > > Date:6/20/2002 4:34:41 PM US Mountain Standard Time > > > > > From:<A HREF="mailto:pate@eylerfamily.org">pate(a)eylerfamily.org</A> > > > > > To:<A HREF="mailto:broot@gslis.utexas.edu">broot(a)gslis.utexas.edu</A> > > > > > CC:<A > > HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A>, <A > > HREF="mailto:Koha-devel@lists.sourceforge.net">Koha- devel(a)lists.sourceforge. > > net</A> > > > > > Sent from the Internet > > > > > > > > > > > > > > > > > > > > On Thu, 20 Jun 2002, Shane Williams wrote: > > > > > > > > > > > I've been watching Koha's progress for a couple of years now. I > > tried > > > > > > 1.04, had some install troubles (with CDK in particular) and put it > > on > > > > > > the backburner. > > > > > > > > > > Thanks for sticking with Koha. > > > > > > > > > > > > > > > > > In any case, I decided 1.20 was a good point to reassess things. > > > > > > Things are looking much better (thank you so much for the web > > > > > > interface, now I don't have to monkey with CDK). That said, I've > > had > > > > > > a number of problems with 1.20 as well. Looking at the recent list > > > > > > archive I can see that others are having trouble with 1.2.0 as well. > > > > > > > > > > > > > > > > Yep, there are some issues with 1.2.0, a 1.2.1 release to fix the > > things > > > > > we've seen should be out shortly. > > > > > > > > > > > I just wanted to lay out a few of the problems I've had (some may be > > > > > > repititions of other's posts). > > > > > > > > > > > > 1) Several links to koha.some.where/cgi-bin/koha/etc. that failed > > > > > > based on the example <VirtualHost> entries. My solution was to > > change > > > > > > my ScriptAlias entry in httpd.conf to: > > > > > > > > > > > > ScriptAlias /cgi-bin/koha/ /home/httpd/koha/cgi-bin/ > > > > > > instead of: > > > > > > ScriptAlias /cgi-bin/ /home/httpd/koha/cgi-bin/ > > > > > > > > > > > > > > > > > > 2) On the members/index.html there's a link to > > members/results-add.html, > > > > > > but no such file exists. > > > > > > > > > > > > > > > > > > 3) The other problem, which Pete mentioned in his "koha install > > problems > > > > > > on RH 7.2 MORE DATA" is that all but one of the scripts in > > > > > > koha/cgi-bin/admin/ have compilation problems. For instance, > > running > > > > > > perl -cw branches.pl leads to: > > > > > > > > > > > > Scalar value @biblioitems[$x] better written as $biblioitems [$x] at > > > > > > /usr/lib/perl5/site_perl/5.6.0/i386-linux/C4/Reserves2.pm line 189, > > > > > > <KC> line 6. > > > > > > "my" variable $sth masks earlier declaration in same scope at > > > > > > branches.pl line 192, <KC> line 6. > > > > > > Too many arguments for C4::Output::mklink at branches.pl line 262, > > > > > > near "'')" > > > > > > branches.pl had compilation errors. > > > > > > > > > > > > > > > > > > 4) A few other notes. In the INSTALL file, there are a few > > confusing > > > > > > spots. One is that database name in all the mysql commands is Koha, > > > > > > but in the sample koha.conf file it's koha. Also, at least with > > perl > > > > > > 5.005 the -I option must come before the script name, so the > > command: > > > > > > > > > > > > perl scripts/updater/updatedatabase -I /pathtoC4 > > > > > > should probably read (and why not point to the pathtoC4 dir): > > > > > > > > > > > > perl -I modules/ scripts/updater/updatedatabase > > > > > > > > > > > > > > > > > > All in all though, things are looking good. Once the admin scripts > > > > > > get fixed up, I'll start showing it off to the folks here at the > > > > > > Library and Information Science School. Thanks for all the hard > > work. > > > > > > > > > > > > > > > > Great! Please let us know how things go. And what we can do to help > > make > > > > > the presentation go more smoothly. > > > > > > > > > > -pate > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Koha mailing list > > > Koha(a)lists.katipo.co.nz > > > http://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > >

1 0

1.2 bugs
by Tonnesen Steve 24 Jun '02

24 Jun '02

marcimport.pl calls &newbiblio() which doesn't exist outside of Biblio.pm, and Biblio.pm is not included in 1.2.1 or 'use'd in the script. updatebibitem.pl also calls newbiblioitem() which also doesn't appear to exist outside of Biblio.pm. Biblio.pm _is_ in the CVS rel-1-2 branch, so I'm not sure why it isn't in the tarball. It's almost like the C4 directory got updated (when newbiblio and newbiblioitem got moved from Acquisitions.pm to Biblio.pm) and the scripts didn't. That doesn't sound right either, since Biblio.pm is missing. :) The 1.2.0 tarball has newbiblio and newbiblioitem routines in Acquisitions.pm. Do we have a bugzilla yet? I'm getting behind on fixing these problems. Steve.

3 2