1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
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@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
install the file
/usr/share/doc/gnumed-server/gm-pg_upgradecluster-helper
into the directory
/etc/postgresql-common/pg_upgradecluster.d/
This script modifies the GNUmed databases such that an upgrade
using pg_upgradecluster of earlier versions of postgresql-common
will succeed.
-- Andreas Tille <tille@debian.org> Fri, 04 Nov 2011 22:15:01 +0100
gnumed-server (0v10.4-1) unstable; urgency=low
The database needs a fixup if deleting documents fails for
you. The fixup scripts are in
/var/lib/gnumed/server/sql/v9-v10/fixups/
and run the scripts with:
psql -d gnumed_v10 -U gm-dbo -f <filename>
-- Andreas Tille <tille@debian.org> Sun, 03 May 2009 21:15:41 +0200
|
