koha-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Koha-devel] New Feature: Improved Z39.50 Client


From: Alex King
Subject: Re: [Koha-devel] New Feature: Improved Z39.50 Client
Date: Fri, 03 Nov 2006 17:46:36 +1300
User-agent: Thunderbird 1.5.0.7 (X11/20060915)

Chris Cormack wrote:
On Thu, Nov 02, 2006 at 07:39:49PM -0800, Joshua Ferraro said:
Hi all,

Tumer Garip has back-ported his improvements to the Z39.50 client to
dev_week and I have backported them to rel_2_2. Please update your
systems, test it out, and if everyone agrees and everything seems to be
working as you expect, I propose to release 2.2.7 with the bugfixes
applied since 2.2.6 as well as the MAJOR improvement to the Z39.50
client.
Can we get the fixes for mysql 5 in there as well.
They are small and harmless, no changes of the database, just a change
in the koha.msyql. And a couple of edits in Search.pm and SearchMARC.pm

If people are happy ill commit the fixes

Chris

I'd certainly be happy if the changes are as you say small and harmless, but there has been an opinion put out on the koha list based on http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1089 that major changes are needed for mysql5 support.

To my mind there are two ways you could read the (non)resolution of that bug report. One is that there never was a problem in the areas the submitter was talking about, and he was fixing things that weren't broken. The other is that there are complex and not understood problems with koha-2.2 and mysql5 and it's in the too hard basket, unless extensive work and testing is done.

I suspect the (2.2) release manager is in the latter camp as this bug report is referenced in the release notes of 2.2.6.

It's certainly a good thing to have a warning in the 2.2.6 release mentioning mysql5 incompatibility. However, I think that bug report is not a good description the incompatibility.

My own experience has been that I have installed Koha 2.2.5 with mysql5, and it is (mostly) working, but I haven't tested it extensively enough to be sure. What doesn't work (barcode printing) is I think a problem with the perl modules I have installed rather than the db.

Cheers,

Alex


PS. Update on Debian packaging: I haven't done much, but I had trouble when trying to upgrade my 2.2.5 install to 2.2.6. The upgrade script complained of missing perl modules even after I loaded the modules through CPAN. I need to try a fresh install.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]