The July-August issue of the Evergreen newsletter is now available for consumption:
http://evergreen-ils.org/dokuwiki/doku.php?id=communications:newsletter:july-aug-2012
Evergreen 2.2.1 released
Hi all,
Evergreen 2.2.1 has been released. This release contains a number of bugfixes over the 2.2.0 release from early June. See this page for links to the source code, staff client, release notes, changelog and more: Evergreen Downloads Page.
The bugfixes covered in this releases include improvements to Acquisitions, the TPAC, the documentation (the official DIG documentation is now bundled with the source code) and more.
There are too many people who ought to be thanked for this release, but I’ll go ahead and name some anyway. Thanks in particular for this one to Dan Scott, Ben Shum, Robert Soulliere (and all DIG contributors!), Bill Erickson and Jason Stephenson, plus three of our newest contributors of code: Kathy Lussier, Melissa Lefebvre, and Steven Chan.
Cheers! And by the way, I hope to be able to issue a 2.2.2 release in less time than it took to pull this release together, as bug-fixing effort continues apace.
Evergreen 2.2.0, 2.1.2 rc2, and 2.0.12 released – with SECURITY fixes
I would like to announce the long awaited Evergreen 2.2.0, the first official, stable release with the new Template Toolkit OPAC, and a whole passel of other new features.
You can download it now!
The release notes for 2.2.0 are here.
2.1.2 rc2 and 2.0.12 are also announced (thanks to Dan Scott and Jason Stephenson, respectively)!
2.0.12 is a security update only, and contains no new features.
The technical changelog for 2.2.0 is here.
THESE RELEASES CONTAINS SECURITY UPDATES, so you will want to upgrade as soon as possible.
Upgrading to the latest release in your series (2.2, 2.1, or 2.0) is sufficient to protect your site with these security updates:
- Give away less information with the LOGIN_FAILURE event
- Prevent deleted and barred users from logging in at all
- Require the UPDATE_MARC permission rather than only the CREATE_MARC permission for users to update biblio graphic records
More information about the security updates can be found in the ChangeLog.
If you don’t wish to upgrade outright to the latest version, sites running any 2.0, 2.1, or 2.2 code today can get the benefit of the security updates by following these steps:
- Download the Evergreen 2.2.0, 2.1.2-rc2, or 2.0.12 release tarball; whichever belongs to the release series you’re currently running.
- Untar the tarball
- In the source directory, run
./configure --prefix=/openils --sysconf=/openils/conf && maketo build the libraries - Install the chrpath tool (aptitude install chrpath on Debian / Ubuntu systems)
- Run
chrpath -d Open-ILS/src/c-apps/.libs/oils_auth.soto enable the library to link to the appropriate location - Copy your existing oils_auth.so library to a safe location; for example,
cp /openils/lib/oils_auth.so /openils/oils_auth.so.20120613 - Copy your new oils_auth.so library into place:
cp Open-ILS/src/c-apps/.libs/oils_auth.so /openils/lib/ - As the root user, run ldconfig to refresh your dynamic linking cache.
- As the root user:
- Find the location of Cat.pm running on your system. For systems running Evergreen 2.1 and up, this looks something like
/usr/local/share/perl/5.10.1/OpenILS/Application/Cat.pm, but the Perl version number could vary by system. For systems running 2.0.x, this is likely/openils/lib/perl5/OpenILS/Application/Cat.pm. - Open the file in a text editor and find a line exactly like this:
return $e->die_event unless $e->allowed('CREATE_MARC', $e->requestor->ws_ou); - Replace ‘CREATE_MARC’ with ‘UPDATE_MARC’.
- Save your changes.
- Find the location of Cat.pm running on your system. For systems running Evergreen 2.1 and up, this looks something like
- Restart your OpenSRF services:
osrf_ctl.sh -a restart_all(NOTE: you may require the -l flag on that command, depending on your system).
* To slightly paraphrase Galen Charlton who once referred to similar instructions for a previous security update:
Note that /openils/lib/oils_auth.so is normally a symbolic link to oils_auth.so.2.0.0. When applying Dan’s fix procedure, make sure that the final result has all versions of the file name oils_auth.so[.*] pointing to the same shared object.