[Koha] 1.2.0 Problems

[Pat Eyler]

On Fri, 21 Jun 2002 COURYHOUSE at 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 at eylerfamily.org">pate at eylerfamily.org</A>
> > To:<A HREF="mailto:broot at gslis.utexas.edu">broot at gslis.utexas.edu</A>
> > CC:<A HREF="mailto:koha at lists.katipo.co.nz">koha at lists.katipo.co.nz</A>, <A HREF="mailto:Koha-devel at lists.sourceforge.net">Koha-devel at 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
> >
> > >
>
>