HomeEvergreen: Basic System Admin FunctionsApplying patchesChecking for Patches

7.1. Checking for Patches

Oftimes when working with an issue regarding the Evergreen system, a patch will need to be located and verified. You may, or may not have the proper location of the said file, and if not, must locate and retrieve it.


If the patch was sent to the Open-ILS Dev mailing list:

When a developer states that a patch, or work was submitted to the mailing list, they are referring to the Open-ILS Dev Mailing List. If you do not subscribe to the mailing list, or have an exact submission, estimate the date range within a month and year that the patch would have been submitted. You may browse a list by month and year here.

Then, you may browse these archives for the month by Thread, Subject, Author, or Date.

Once the proper thread regarding your issue is found, read the full thread. After the request, and any appropriate comments have been tendered, a "commit" has usually been applied, with the proper committing developer's name and changeset applied.

Verify Your Version:

Changesets are handled at http://svn.open-ils.org. Once you view the changeset, there may be multiple entries for the same set of inducted code. Do not get confused. You should have (generally) one commit for "trunk", which is the development branch, one for the major release (e.g. 1.6), and finally one for the minor release (e.g. 1.6.0). Instead of the periods in the example, do not be surprised to find underscores instead, like 1_6 or 1_6_0.

The proper selection is the version closest to the server being patched.


Review The Code First!

Always review the original file in a text editor first to ensure that the patch being applied is in fact different from the file already possessed in the system. If this file contains the portions being removed, or is exempted from the code being added, then proceed to the next article on SVN patch retrieval and installation.

Related Pages
This page was: Helpful | Not Helpful