This bug was fixed in the package gnumed-client - 0.8.6-2
--------------- gnumed-client (0.8.6-2) unstable; urgency=low
* debian/control: Fix server version in Recommends (s/v13/v14/) * debian/conf/gnumed-client.conf: New public server address
gnumed-client (0.8.6-1) unstable; urgency=low
* New upstream version
gnumed-client (0.7.10-2.1) testing-proposed-updates; urgency=low
* Non-maintainer upload. * Drop misplaced 0.8.5-1 changelog entry.
gnumed-client (0.7.10-2) testing-proposed-updates; urgency=low
* Fix /etc/gnumed/gnumed-client.conf which was referencing a future database version (v14) instead of v13 which fits gnumed-client version 0.7.x Closes: #608190 -- shilbert <email address hidden> Mon, 14 Feb 2011 22:11:05 +0100
This bug was fixed in the package gnumed-client - 0.8.6-2
---------------
gnumed-client (0.8.6-2) unstable; urgency=low
* debian/control: Fix server version in Recommends (s/v13/v14/) conf/gnumed- client. conf: New public server address
* debian/
gnumed-client (0.8.6-1) unstable; urgency=low
* New upstream version
gnumed-client (0.7.10-2.1) testing- proposed- updates; urgency=low
* Non-maintainer upload.
* Drop misplaced 0.8.5-1 changelog entry.
gnumed-client (0.7.10-2) testing- proposed- updates; urgency=low
* Fix /etc/gnumed/ gnumed- client. conf which was referencing a future
database version (v14) instead of v13 which fits gnumed-client
version 0.7.x
Closes: #608190
-- shilbert <email address hidden> Mon, 14 Feb 2011 22:11:05 +0100