[med-svn] r15160 - in trunk/packages/gnumed-server/trunk/debian: . patches

Andreas Tille tille at alioth.debian.org
Fri Nov 8 23:08:54 UTC 2013


Author: tille
Date: 2013-11-08 23:08:53 +0000 (Fri, 08 Nov 2013)
New Revision: 15160

Added:
   trunk/packages/gnumed-server/trunk/debian/patches/
   trunk/packages/gnumed-server/trunk/debian/patches/make_sure_user_has_set_organisation_in_v18.patch
   trunk/packages/gnumed-server/trunk/debian/patches/series
Modified:
   trunk/packages/gnumed-server/trunk/debian/NEWS.Debian
   trunk/packages/gnumed-server/trunk/debian/README.Debian
   trunk/packages/gnumed-server/trunk/debian/changelog
Log:
Several means to teach users about injecting organisation + unit data before upgrading database


Modified: trunk/packages/gnumed-server/trunk/debian/NEWS.Debian
===================================================================
--- trunk/packages/gnumed-server/trunk/debian/NEWS.Debian	2013-11-08 09:22:00 UTC (rev 15159)
+++ trunk/packages/gnumed-server/trunk/debian/NEWS.Debian	2013-11-08 23:08:53 UTC (rev 15160)
@@ -1,3 +1,13 @@
+gnumed-server (19.0-1) unstable; urgency=low
+
+  Before upgrading your existing GNUmed database v18 to the v19 schema it
+  is very advisable to make sure you have created (by using the 1.3
+  client) -- an organization and a unit thereof to serve as your praxis
+  and praxis location. During the very first start of the 1.4 client you
+  will be asked which organization/unit represents your praxis/location.
+
+ -- Andreas Tille <tille at debian.org>  Fri, 08 Nov 2013 15:25:40 +0100
+
 gnumed-server (16.1-1) unstable; urgency=low
 
   If you are using postgresql-common version < 122 you need to

Modified: trunk/packages/gnumed-server/trunk/debian/README.Debian
===================================================================
--- trunk/packages/gnumed-server/trunk/debian/README.Debian	2013-11-08 09:22:00 UTC (rev 15159)
+++ trunk/packages/gnumed-server/trunk/debian/README.Debian	2013-11-08 23:08:53 UTC (rev 15160)
@@ -55,6 +55,11 @@
 	are ABSOLUTELY SURE you already have an uptodate backup !
 
 	This must be run as root on the database server.
+	
+	Remark: If your postgresql server is running on a non default
+	        port (5432) you should set the environment variable
+	          GM_DB_PORT
+	        accordingly.
 
 3) Adjust backend profiles in private .conf files.
 

Modified: trunk/packages/gnumed-server/trunk/debian/changelog
===================================================================
--- trunk/packages/gnumed-server/trunk/debian/changelog	2013-11-08 09:22:00 UTC (rev 15159)
+++ trunk/packages/gnumed-server/trunk/debian/changelog	2013-11-08 23:08:53 UTC (rev 15160)
@@ -1,9 +1,15 @@
-gnumed-server (19.0-1) UNRELEASED; urgency=low
+gnumed-server (19.0-1) unstable; urgency=low
 
   * New upstream version
-  * Update README.Debian to new version
+  * Update README.Debian to new version; mention GM_DB_PORT to enable
+    specifying non-default port
+  * debian/NEWS.Debian: Hint to inject an organisation by using old
+    version of gnumed-client
+  * debian/patches/make_sure_user_has_set_organisation_in_v18.patch:
+    before running database initialising script ask again whether
+    organisation + unit is set
 
- -- Andreas Tille <tille at debian.org>  Tue, 29 Oct 2013 21:04:52 +0100
+ -- Andreas Tille <tille at debian.org>  Fri, 08 Nov 2013 15:25:40 +0100
 
 gnumed-server (18.9-1) unstable; urgency=low
 

Added: trunk/packages/gnumed-server/trunk/debian/patches/make_sure_user_has_set_organisation_in_v18.patch
===================================================================
--- trunk/packages/gnumed-server/trunk/debian/patches/make_sure_user_has_set_organisation_in_v18.patch	                        (rev 0)
+++ trunk/packages/gnumed-server/trunk/debian/patches/make_sure_user_has_set_organisation_in_v18.patch	2013-11-08 23:08:53 UTC (rev 15160)
@@ -0,0 +1,39 @@
+Author: Andreas Tille <tille at debian.org>
+LastChanged: Fri, 08 Nov 2013 15:25:40 +0100
+Description: We want to make really sure that the user has
+ set organisation + unit in his old database (v18) before we
+ are upgrading to v19.  The patch can be droped again for
+ later (major) versions.
+ 
+--- a/server/gm-bootstrap_server
++++ b/server/gm-bootstrap_server
+@@ -1,4 +1,28 @@
+-#!/bin/sh
++#!/bin/bash
++
++# if any GNUmed database is available ...
++if psql -l | grep -qi gnumed ; then
++  # ... ask user whether he has injected organisation + unit
++  cat <<EOT
++========================================================================
++
++Before upgrading your existing GNUmed database v18 to the v19 schema it
++is very advisable to make sure you have created (by using the 1.3
++client) -- an organization and a unit thereof to serve as your praxis
++and praxis location. During the very first start of the 1.4 client you
++will be asked which organization/unit represents your praxis/location.
++
++Did you have definte organization and unit thereof?
++
++EOT
++  read -e -p "[y / N]: "
++  if test "${REPLY}" = "y" ; then
++    echo "OK. Start upgrading server."
++  else
++    echo "Upgrading aborted by user."
++    exit 1
++  fi
++fi
+ 
+ #==============================================================
+ # This wrapper is intended to be installed into a systemwide

Added: trunk/packages/gnumed-server/trunk/debian/patches/series
===================================================================
--- trunk/packages/gnumed-server/trunk/debian/patches/series	                        (rev 0)
+++ trunk/packages/gnumed-server/trunk/debian/patches/series	2013-11-08 23:08:53 UTC (rev 15160)
@@ -0,0 +1 @@
+make_sure_user_has_set_organisation_in_v18.patch




More information about the debian-med-commit mailing list