For the time being gnumed-server 15.11 packages are avaialble via the
GNUmed team PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878679
Title:
Please sync gnumed-server 15.11-1 (universe) from
Public bug reported:
Binary package hint: gnumed-client
[Impact]
Ubuntu 11.11 has been released but unfortunately the version of GNUmed
that is shipped does not give a working installation. This is due to the
fact that 11.11 ships with Postgresql 9.1 which enforces even tighter
checks on
Public bug reported:
Binary package hint: gnumed-server
[Impact]
Ubuntu 11.11 has been released but unfortunately the version of GNUmed
server that is shipped does not give a working installation. This is due
to the fact that 11.11 ships with Postgresql 9.1 which enforces even
tighter checks on
The SQL reports added in 0.9.11 (really just a few lines of sql queries)
are needed to prospectively search for/fix data duplicates which have
the potential to break a future update of the GNUmed database. So while
the gnumed-client is not in a critical condition with regards to being
broken in
Bug has been fixed in newer GNUmed versions.
** Changed in: gnumed-client (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719365
Title:
gnumed-client 0.7.9
Public bug reported:
Binary package hint: gnumed-client
Hi,
https://wiki.ubuntu.com/OneiricReleaseSchedule indicates that Debian
import freeze is in effect. Please consider syncing the purely
maintainence release gnumed-client 0.9.9 since there are some bugfixes
directly related to the
Public bug reported:
Binary package hint: gnumed-client
Hi,
Please consider syncing the purely bugfix release gnumed-client 0.8.6-2 since
there are some bugfixes directly related to the experience of GNUmed on Ubuntu.
http://ftp.debian.org/debian/pool/main/g/gnumed-client/gnumed-
Public bug reported:
Binary package hint: gnumed-client
gnumed-client 0.7.9 in Maverick is affected by the problem that the
domain salaam.homeunix.com is unreachable. Therefore the public database
is unreachable and cannot be used.
Problems is know by the GNUmed team.
13.8 is no different from 13.7. It is only a increased version number to
match the client update.
0.7.8. This fixes
the following bugs:
0.7.8
FIX: exception on substance listing because ref.v_substance_in_brand
does not have external_code_type_brand
FIX: exception when
On Sunday 05 September 2010 16:38:22 you wrote:
13.8 is no different from 13.7. It is only a increased version number
to match the client update.
Should we not sync 13.8 then?
Not really since the client in Maverick is 0.7.7 only. While this clients
works with server 13.8 just fine the
Here is it the upstream changelog for 13.6 to 13.7
I am happy to announce the GNUmed 0.7.7 maintenance release:
0.7.7
FIX: DOB could become today in certain corner cases when creating new
person [thanks S.Reus]
FIX: check_drug_interactions() failed with
By the way GNUmed released version 0.8.1 and server 14.1 but because the
0.7 series is such a well tested release we would like to see that
series go in.
--
Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/607394
You received this bug
** Description changed:
Binary package hint: gnumed-server
Hi,
https://wiki.ubuntu.com/MaverickReleaseSchedule indicates that Debian
import freeze is in effect. Please consider syncing the purely bugfix
release gnumed-server 13.6 since there are some bugfixes directly
related to
This version is oudated. GNUmed 0.7.5 is available from the GNUmed PPA.
** Changed in: gnumed-client (Ubuntu)
Status: New = Invalid
--
new upstream version available: 0.6.3 (bug-fix-only)
https://bugs.launchpad.net/bugs/580949
You received this bug notification because you are a member
Public bug reported:
Binary package hint: gnumed-client
Hi,
https://wiki.ubuntu.com/MaverickReleaseSchedule indicates that Debian
import freeze is in effect. Please consider syncing the purely
maintainence release gnumed-client 0.7.7 and gnumed-server 13.6 since
there are some bugfixes directly
Public bug reported:
Binary package hint: gnumed-client
Hi,
https://wiki.ubuntu.com/MaverickReleaseSchedule indicates that Debian
import freeze is in effect. Please consider syncing the purely bugfix
release gnumed-server 13.6 since there are some bugfixes directly
related to the experience of
Public bug reported:
Binary package hint: gnumed-server
Hi,
https://wiki.ubuntu.com/MaverickReleaseSchedule indicates that Debian
import freeze is in effect. Please consider syncing the purely bugfix
release gnumed-server 13.6 since there are some bugfixes directly
related to the experience of
** Description changed:
Binary package hint: gnumed-client
- Binary package hint: gnumed-client
+ Binary package hint: gnumed-server
Upstream has released the new stable version 0.61 which is available
from Debian/Testing
Please sync for Lucid Lynx.
diff is here:
Public bug reported:
Binary package hint: gnumed-client
Binary package hint: gnumed-client
Upstream has released the new stable version 0.61 which is available
from Debian/Testing
Please sync for Lucid Lynx.
diff is here: http://ftp.de.debian.org/debian/pool/main/g/gnumed-client
It has been synced as of Feb. 5th. However in the meantime we have
release version 0.6.1 which is a bug fix release. So please sync that
one from Debian unstable. It will not move into Debian testing until Feb
15th and therefore miss the DebianImportFreeze by a few days. It will
however not miss
** Changed in: gnumed-client (Ubuntu)
Status: New = Invalid
--
Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/330473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: gnumed-client (Ubuntu)
Status: New = In Progress
--
Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/330473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is most likely not going to happen. The solution is to upgrade to
version 0.4.6 or higher from the GNUmed PPA
** Changed in: gnumed-client (Ubuntu)
Status: In Progress = New
--
Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable (main)
Public bug reported:
The package builds and installs fine, no ubuntu changes needed.
http://ftp.de.debian.org/debian/pool/main/g/gnumed-client/gnumed-
client_0.4.7-1.dsc
** Affects: ubuntu
Importance: Undecided
Status: New
--
[Sync request]: gnumed-client_0.4.7-1 from Debian
Public bug reported:
Binary package hint: gnumed-client
Hi,
Jaunty ships an outdated GNUmed version which crashes for many users
like this
2009-05-12 05:22:37 WARNING gm.database
(/var/lib/python-support/python2.6/Gnumed/pycommon/gmPG2.py::__validate_timezone()
#186): time zone [IST]
Fix has been released as of version 0.3.12 but is handled saner in 0.4.4
** Changed in: gnumed-client (Ubuntu)
Status: New = Fix Released
--
gnumed - SRU - new upstream available - 0.4.4
https://bugs.launchpad.net/bugs/375874
You received this bug notification because you are a member of
On Mittwoch 13 Mai 2009 12:24:48 James Westby wrote:
Hi
Check that the bug is fixed in the current development release, and that its
bug report task is Fix released. It is, in general, not appropriate to
release bug fixes for stable systems without first testing them in the current
Public bug reported:
Binary package hint: gnumed-client
Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable
(main).
Changelog since current jaunty version 0.3.9-1:
gnumed-client (0.3.10-1) unstable; urgency=low
* New upstream version.
-- Andreas Tille ti...@debian.org
For GNUmed this backport is needed as well. see wiki.gnumed.de
We have tested it with 2.0.7 and the 'unable to parse time' error is
fixed.
Sebastian
--
Backport python-psycopg2 2.0.7 to hardy?
https://bugs.launchpad.net/bugs/238537
You received this bug notification because you are a member of
** Description changed:
Binary package hint: gnumed-client
SInce Hardy has been released the semi-automatic reporter has reported
quite some bugs. Most of them are due to Hardy shipping an oudated
version (0.2.8.2).
Meanwhile the Debian packages have seen quite a few bug fix
Bug reports on the old version keep coming in. To get the update do
this:
Go to synaptic and into Settings, Repositories. then switch to updates
tab and enable pre-release updates
Sebastian
--
Outdated (buggy) GNUmed version (0.2.8.2) in Hardy
https://bugs.launchpad.net/bugs/224077
You
Works flawlessly in a Vmware virtual machine. Updated through synaptic
Sebastian
--
Outdated (buggy) GNUmed version (0.2.8.2) in Hardy
https://bugs.launchpad.net/bugs/224077
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
(bug 249891) has been fixed. Please proceed with the inclusion into
hardy-updates as this will save us (GNUmed team) a lot of bug reports
not to speak of give your users the opportunity to try GNUmed for the
first time.
Thanks a lot,
Sebastian
--
Outdated (buggy) GNUmed version (0.2.8.2) in
Public bug reported:
Binary package hint: gnumed-client
SInce Hardy has been released the semi-automatic reporter has reported
quite some bugs. Most of them are due to Hardy shipping an oudated
version (0.2.8.2).
Meanwhile the Debian packages have seen quite a few bug fix releases. We
are up to
works now. I have attached another patch which is needed. It patches the
gnumed.conf config file so the user connects to the correct port on our
postgres database.
It's a one-liner.
** Attachment added: changes port for postgres database
BTW. The patches fix GNUmed 0.2.6.3 in Gutsy. Please sync with Debian testing
for Hardy.
At the time of writing this should be 0.2.7.1
Thanks,
the GNUmed team
--
gnumed - new upstream available - 0.2.7.1
https://bugs.launchpad.net/bugs/154136
You received this bug notification because you are
see attached patch
** Attachment added: ubuntu-gutsy-gibbon-gmPG2.py.diff
http://launchpadlibrarian.net/10071440/ubuntu-gutsy-gibbon-gmPG2.py.diff
--
gnumed - new upstream available - 0.2.7.1
https://bugs.launchpad.net/bugs/154136
You received this bug notification because you are a member
Public bug reported:
Hi,
Please consider backporting gnumed from gutsy to feisty.
Version in gutsy : https://launchpad.net/ubuntu/+source/gnumed-
client/0.2.5.0-1ubuntu1
Version in feisty: https://launchpad.net/ubuntu/+source/gnumed-
client/0.2.4.2-1ubuntu1
Initial tests show gutsy version
Public bug reported:
Binary package hint: gnumed-client
Please merge with version 0.2.5.0-1 from Debian unstable
** Affects: gnumed-client (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
please merge with 0.2.5.0-1
https://bugs.launchpad.net/bugs/104153
You received this
On Thursday 07 September 2006 14:39, Wouter Stomp wrote:
There is no log file in my .gnumed directory. Will look for the rest
later.
you are right. Please try apt-get install gnumed-common.
This is fixed in the next release
--
Sebastian Hilbert
Leipzig / Germany
[www.gnumed.de] - PGP
Have you installed gnumed-common ?
gnumed-client should pull this as a dependency and will do so.
updated packages are in Debian unstable as of 6 Sep 2006 and should move
to testing shortly.
Sebastian Hilbert
GNumed project
--
Crash at program start
https://launchpad.net/bugs/57818
--
41 matches
Mail list logo
