open source

Hi everyone,

Dear community

GNU Health 4.2.2 patchset has been released !

Priority: High

Table of Contents

• About GNU Health Patchsets
• Updating your system with the GNU Health control Center
• Installation notes
• List of other issues related to this patchset

About GNU Health Patchsets

We provide “patchsets” to stable releases. Patchsets allow applying bug fixes and updates on production systems. Always try to keep your production system up-to-date with the latest patches.

Patches and Patchsets maximize uptime for production systems, and keep your system updated, without the need to do a whole installation.

NOTE: Patchsets are applied on previously installed systems only. For new, fresh installations, download and install the whole tarball (ie, gnuhealth-4.2.2.tar.gz)

Updating your system with the GNU Health control Center

Starting GNU Health 3.x series, you can do automatic updates on the GNU Health HMIS kernel and modules using the GNU Health control center program.

Please refer to the administration manual section ( https://en.wikibooks.org/wiki/GNU_Health/Control_Center )

The GNU Health control center works on standard installations (those done following the installation manual on wikibooks). Don’t use it if you use an alternative method or if your distribution does not follow the GNU Health packaging guidelines.

Installation Notes

You must apply previous patchsets before installing this patchset. If your patchset level is 4.2.1, then just follow the general instructions. You can find the patchsets at GNU Health main download site at GNU.org (https://ftp.gnu.org/gnu/health/)

In most cases, GNU Health Control center (gnuhealth-control) takes care of applying the patches for you. 

Pre-requisites for upgrade to 4.2.2: None

Now follow the general instructions at

 https://en.wikibooks.org/wiki/GNU_Health/Control_Center

 

After applying the patches, make a full update of your GNU Health database as explained in the documentation.

When running “gnuhealth-control” for the first time, you will see the following message: “Please restart now the update with the new control center” Please do so. Restart the process and the update will continue.

 

• Restart the GNU Health server

List of bugs and tasks related to this patchset

• bug #64269: get_serial function of LabTest class in health_crypto_lab.py need conside add units.name
• bug #64386: Automatically update the appointment sequence when state is confirm
• bug #64432: Gestational weeks show floating point instead of weeks
• bug #64457: Patient automatic critical information entries should be unique
• bug #64530: traceback on evaluation page of life if no institution is given
• bug #64665: Product cost_price needs to be passed as an argument in stock moves

For detailed information about each issue, you can visit :

 https://savannah.gnu.org/bugs/?group=health

 

About each task, you can visit:

 https://savannah.gnu.org/task/?group=health

For detailed information you can read about Patches and Patchsets

• https://en.wikibooks.org/wiki/GNU_Health/Patches_and_Patchsets

If you reach this page, you may be interested into this new category of Linux distributions labeled “immutable”. In this category, one can find by age (oldest → youngest) NixOS, Guix, Endless OS, Fedora Silverblue, OpenSUSE MicroOS, Vanilla OS and many new to come. I will give examples of immutability implementation, then detail my thoughts about immutability, and why I think this naming can be misleading. I spent a few months running all of those distributions on my main computers (NAS, Gaming, laptop, workstation) to be able to write this text. I haven’t given any of these a try just yet, but I feel like this is where the Linux desktop is going. I’m not sure if that’s a good or a bad thing – I need both more experience as well as read more informed opinions about it – but I do like the concept.