Koha 3.2.5 is now available
Please note: This release is a security release. It is strongly recommended that users apply this upgrade immediately to production systems. If you are installing a new system, please use this version rather than earlier versions. It is with pleasure that I announce the release of Koha 3.2.5. The package can be retrieved from: http://download.koha-community.org/koha-3.02.05.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.05.tar.gz.MD5 http://download.koha-community.org/koha-3.02.05.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.05.tar.gz.sig Release notes for 3.2.5 are below. Come and get it! RELEASE NOTES FOR KOHA 3.2.5 - 24 February 2011 ======================================================================== Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is http://koha-community.org/ Koha 3.2.5 can be downloaded from: http://download.koha-community.org/koha-3.02.05.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation Highlights of 3.2.5 ====================== NOTE: This release is a security release. It is strongly recommended that users apply this upgrade immediately to production systems. If you are installing a new system, please use this version rather than earlier versions. Bugs fixed in 3.2.5 ====================== 1953 remove possible SQL injection attacks 2742 Wrong language name in the preferences 5745 overdues with fines not showing titles 5759 When printing a borrowers information the secondary email address is not printed 5769 notice tab disappearing on edit patron System requirements ====================== Changes since 3.0: * The minimum version of Perl required is now 5.8.8. * There are a number of new Perl module dependencies. Run ./koha_perl_deps.pl -u -m to get a list of any new modules to install during upgrade. Upgrades ====================== The structure of the acquisitions tables have changed significantly from 3.0.x. In particular, the budget hierarchy is quite different. During an upgrade, a new database table is created called fundmapping that contains a record of how budgets were mapped. It is strongly recommended that users of Koha 3.0.x acquisitions carefully review the results of the upgrade before resuming ordering in Koha 3.2.x. Documentation ====================== As of Koha 3.2, the Koha manual is now maintained in DocBook. The home page for Koha documentation is http://koha-community.org/documentation/ As of the date of these release notes, several translations of the Koha manual are available: English: http://koha-community.org/documentation/3-2-manual/ Spanish: http://koha-community.org/documentation/3-2-manual-es/ French: http://koha-community.org/documentation/3-2-manual-fr/ The Git repository for the Koha manual can be found at http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Translations ====================== Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: * Chinese * Danish * English (New Zealand) * English (USA) * French (France) * French (Canada) * German * Greek * Hindi * Italian * Norwegian * Portuguese * Spanish * Turkish Partial translations are available for various other languages. The Koha team welcomes additional translations; please see http://www.kohadocs.org/usersguide/apb.html for information about translating Koha, and join the koha-translate list to volunteer: http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate The most up-to-date translations can be found at: http://translate.koha-community.org/ Release Team ====================== The release team for Koha 3.2 is Release Manager: Galen Charlton <gmcharlt@gmail.com> Documentation Manager: Nicole Engard <nengard@gmail.com> Translation Manager: Chris Cormack <chris@bigallofwax.co.nz> Release Maintainer (3.0.x): Henri-Damien Laurent <henridamien.laurent@biblibre.com> Release Maintainer (3.2.x): Chris Nighswonger <cnighswonger@foundations.edu> Credits ====================== We thank the following individuals who contributed patches to Koha 3.2.5: Owen Leonard Chris Nighswonger marcel@libdevelop.rijksmuseum.nl Paul Poulain We regret any omissions. If a contributor has been inadvertantly missed, please send patch against these release notes to koha-patches@lists.koha-community.org. The 3.2.x Release Maintainer especially thanks the 3.4 Release Team and all who participated in QA for their diligent labors in testing and pushing well over 330 patches since the 3.2.0 relese. Their continued work very much makes possible the release of 3.2.5 on its announced schedule. Revision control notes ====================== The Koha project uses Git for version control. The current development version of Koha can be retrieved by checking out the master branch of git://git.koha-community.org/koha.git The branch for Koha 3.2.x (i.e., this version of Koha and future bugfix releases) is 3.2.x. The next major feature release of Koha will be Koha 3.4.0. Bugs and feature requests ====================== Bug reports and feature requests can be filed at the Koha bug tracker at http://bugs.koha-community.org/ Naku te rourou, nau te rourou, ka ora ai te iwi.
Chris Nighswonger schreef op do 24-02-2011 om 16:22 [-0500]:
Please note: This release is a security release. It is strongly recommended that users apply this upgrade immediately to production systems. If you are installing a new system, please use this version rather than earlier versions.
The stable packages have been updated to this just now, I'm about to make some new squeeze-dev ones too. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
On behalf of all us lazy and/or noob sysadmins, thanks much Robin! To anyone - sorry to repeat some previous questions; I'd welcome a simple pointer as to where this may have been documented (where I should have learned it already). --------- Is it safe to just update from 3.2.3 with an existing database? If so, is that generally safe with point releases at that third level (3.2.6 through 2.2.9 but perhaps not 3.3?) Does everything just automagically work while the system is in use, or does Apache or something need to be restarted, or is there an upgrade-data script that needs to be run?
Sorry I didn't specifically state my questions are regarding updating automatically via the Debian package management system, not the traditional, more manual methods, whatever those might be. . .
Is it safe to just update from 3.2.3 with an existing database?
If so, is that generally safe with point releases at that third level (3.2.6 through 2.2.9 but perhaps not 3.3?)
Does everything just automagically work while the system is in use, or does Apache or something need to be restarted, or is there an upgrade-data script that needs to be run?
On 25 February 2011 09:00, <hansbkk@gmail.com> wrote:
Is it safe to just update from 3.2.3 with an existing database?
If so, is that generally safe with point releases at that third level (3.2.6 through 2.2.9 but perhaps not 3.3?)
Does everything just automagically work while the system is in use, or does Apache or something need to be restarted, or is there an upgrade-data script that needs to be run?
Sorry I didn't specifically state my questions are regarding updating automatically via the Debian package management system, not the traditional, more manual methods, whatever those might be. . .
That would be this, from INSTALL.debian (http://git.koha-community.org/gitweb/?p=koha.git;a=blob_plain;f=INSTALL.debi...): UPGRADE ======= If you are upgrading from a previous installation of Koha 3, you can use the following: ./koha_perl_deps.pl -u -m # to identify new Perl dependencies perl Makefile.PL --prev-install-log /path/to/koha-install-log make make test sudo make upgrade After you have done that you should immediately go to your Intranet and if there are required changes to the database you will be prompted to login and and the web installer will do the updates for you. The OPAC will display a "this system is under maintenance" type message until you have done that. I imagine that last bit would work much the same way with the packages, although I haven't had much time to play with them yet... Best regards, Magnus Enger libriotech.no
On Fri, Feb 25, 2011 at 3:05 PM, Magnus Enger <magnus@enger.priv.no> wrote:
Is it safe to just update from 3.2.3 with an existing database?
If so, is that generally safe with point releases at that third level (3.2.6 through 2.2.9 but perhaps not 3.3?)
Does everything just automagically work while the system is in use, or does Apache or something need to be restarted, or is there an upgrade-data script that needs to be run?
Sorry I didn't specifically state my questions are regarding updating automatically via the Debian package management system, not the traditional, more manual methods, whatever those might be. . .
That would be this, from INSTALL.debian (http://git.koha-community.org/gitweb/?p=koha.git;a=blob_plain;f=INSTALL.debi...):
Thanks much for replying Magnus. The link above returns "no such project" for me, perhaps a permissions issue? I went ahead and did "aptitude update" and everything came down OK. I couldn't find an INSTALL.debian file - but did find a README.debian, but that doesn't seem to have anything other than information pertaining to the original install, nothing about upgrades. However after the "Setting up koha-common 3.2.5-1" came: ----------------------- Installing new version of config files Starting Zebra (one for each koha site) and Upgrading database schema (.03.001-3, then .04, .04) again one set per site. ----------------------- The web interfaces for both admin and OPAC seem as normal, and About Koha reports 3.02.05.000. So it looks like Robin got the packaging stuff setup to automate all the post-install steps? If so, more kudos to him! (koha kudos heehee 8-)
On 25 February 2011 09:42, <hansbkk@gmail.com> wrote:
On Fri, Feb 25, 2011 at 3:05 PM, Magnus Enger <magnus@enger.priv.no> wrote:
Is it safe to just update from 3.2.3 with an existing database?
If so, is that generally safe with point releases at that third level (3.2.6 through 2.2.9 but perhaps not 3.3?)
Does everything just automagically work while the system is in use, or does Apache or something need to be restarted, or is there an upgrade-data script that needs to be run?
Sorry I didn't specifically state my questions are regarding updating automatically via the Debian package management system, not the traditional, more manual methods, whatever those might be. . .
That would be this, from INSTALL.debian (http://git.koha-community.org/gitweb/?p=koha.git;a=blob_plain;f=INSTALL.debi...):
Thanks much for replying Magnus. The link above returns "no such project" for me, perhaps a permissions issue?
Or an URL-in-email-interpretation issue... These should work: http://tinyurl.com/64b384w http://preview.tinyurl.com/64b384w
So it looks like Robin got the packaging stuff setup to automate all the post-install steps?
If so, more kudos to him! (koha kudos heehee 8-)
Again, I don't really know the packages, but yeah, definitely kudos to Robin (and Lars W. who worked on the packages before him)! Regards, Magnus Enger libriotech.no
On Fri, Feb 25, 2011 at 4:23 PM, Magnus Enger <magnus@enger.priv.no> wrote:
Or an URL-in-email-interpretation issue... These should work: http://tinyurl.com/64b384w http://preview.tinyurl.com/64b384w
The URL works, but I believe it's been superceded by the README.debian, doesn't show up on my system at all. Everything seems to be fine doing nothing but "aptitude upgrade", even on a live system. . .
Again, I don't really know the packages, but yeah, definitely kudos to Robin (and Lars W. who worked on the packages before him)!
Thanks all 'round!
Op vrijdag 25 februari 2011 23:41:00 schreef hansbkk@gmail.com:
Everything seems to be fine doing nothing but "aptitude upgrade", even on a live system. . .
Just to confirm, part of the package update process is to upgrade your database schema as it installs. I think it does an apache restart as part of this. So, if you're running off packages, schedule a little downtime (about a minute or two, in an ideal world - I still do it outside of operational hours just to be paranoid), upgrade them, and (fingers crossed) no one will notice a thing. Also, the packages were updated earlier today (NZ time) so you should see the new versions there already. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204
On Fri, Feb 25, 2011 at 3:42 AM, <hansbkk@gmail.com> wrote:
On Fri, Feb 25, 2011 at 3:05 PM, Magnus Enger <magnus@enger.priv.no> wrote:
Is it safe to just update from 3.2.3 with an existing database?
If so, is that generally safe with point releases at that third level (3.2.6 through 2.2.9 but perhaps not 3.3?)
Does everything just automagically work while the system is in use, or does Apache or something need to be restarted, or is there an upgrade-data script that needs to be run?
Sorry I didn't specifically state my questions are regarding updating automatically via the Debian package management system, not the traditional, more manual methods, whatever those might be. . .
That would be this, from INSTALL.debian ( http://git.koha-community.org/gitweb/?p=koha.git;a=blob_plain;f=INSTALL.debi... ):
Thanks much for replying Magnus. The link above returns "no such project" for me, perhaps a permissions issue?
Works fine from my neck of the woods. Kind Regards, Chris
participants (4)
-
Chris Nighswonger -
hansbkk＠gmail.com -
Magnus Enger -
Robin Sheat