[Bug 878679] Re: Please sync gnumed-server 15.11-1 (universe) from Debian testing (main)
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 Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnumed-server/+bug/878679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878676] Re: Please sync gnumed-client 0.9.11-1 (universe) from Debian testing (main)
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 the current release it would make sens to SRU it along with the needed SRU for gnumed-server to proactively prevent future breakage which otherwise would hit anyone upgrading GNUmed-server during the Ubuntu 12.04 release cycle. And since 12.04 really is intended to be a LTS release it would make sense to prevent any possible bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878676 Title: Please sync gnumed-client 0.9.11-1 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnumed-client/+bug/878676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878679] [NEW] Please sync gnumed-server 15.11-1 (universe) from Debian testing (main)
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 escaped string. [Development Fix] To make it work in Ubuntu 11.11 gnumed-server 15.11 has been released. http://ftp.de.debian.org/debian/pool/main/g/gnumed-server/gnumed- server_15.11-1.dsc This is strictly a bugfix release. See the upstream changes here. server 15.11 FIX: trf_do_not_update_substance_if_taken_by_patient() on ref.consumable_substance FIX: properly E''-ify escape containing strings in bootstrapper SQL scripts (this fixes the no-bootstrap-under PostgreSQL-9.1 issue server 15.10 FIX: cannot restore --single-transaction because CREATE DATABASE does not transact [thanks S.Reus] IMPROVED: better commenting of informative messages in -roles.sql Debian changelog: gnumed-server (15.11-1) unstable; urgency=low * New upstream version * debian/copyright: s/Maintainer/Upstream-Contact/, s/Name/Upstream-&/ -- Andreas Tille Wed, 19 Oct 2011 12:01:07 +0200 gnumed-server (15.10-1) unstable; urgency=low * New upstream version -- Andreas Tille Fri, 09 Sep 2011 13:09:41 +0200 [Regression Potential] Users trying to run GNUmed on Ubuntu 11.11 will find that they cannot get a working GNUmed database. So for gnumed-server a SRU is highly appreciated. ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- 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 Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnumed-client/+bug/878679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878676] [NEW] Please sync gnumed-client 0.9.11-1 (universe) from Debian testing (main)
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 escaped string. [Development Fix] To make it work in Ubuntu 11.11 gnumed-client 0.9.11 has been releases as well as gnumed-server 15.11 http://ftp.de.debian.org/debian/pool/main/g/gnumed-client/gnumed- client_0.9.11-1.dsc This is strictly a bugfix release. See the upstream changes here. 0.9.11 IMPROVED: add SQL reports to find duplicate streets/urbs/regions client 0.9.10 FIX: include latest GPL v2.0 license text from FSF [thanks Ankur] FIX: gracefully handle invalid DOB (future, DOB > DOD) [thanks Wim] IMPROVED: substance intake table: "amount per unit" = "Strength", not "Dose" [thanks J.Busser] Debian changelog: gnumed-client (0.9.11-1) unstable; urgency=low * New upstream version * debian/copyright: s/Maintainer/Upstream-Contact/, s/Name/Upstream-&/ -- Andreas Tille Wed, 19 Oct 2011 13:28:53 +0200 gnumed-client (0.9.10-2) unstable; urgency=low * Add libreoffice-writer as alternative Recommends to openoffice.org-writer -- Andreas Tille Fri, 09 Sep 2011 14:57:28 +0200 gnumed-client (0.9.10-1) unstable; urgency=low * New upstream version -- Andreas Tille Fri, 09 Sep 2011 14:51:06 +0200 [Regression Potential] Users trying to run GNUmed on Ubuntu 11.11 will find that they cannot get a working GNUmed database. So at least for gnumed-server a SRU is highly appreciated. The client itself is not in a critical condition although the bugs mentioned above have been fixed and a synced microrelease for gnumed-client and gnumed-server has been provided. ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878676 Title: Please sync gnumed-client 0.9.11-1 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnumed-client/+bug/878676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 828562] [NEW] [Sync request] Please sync gnumed-client 0.9.9-1 (universe) from Debian testing (main)
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 experience of GNUmed on Ubuntu. http://cdn.debian.net/debian/pool/main/g/gnumed-client/gnumed- client_0.9.9-1.dsc gnumed-client (0.9.9-1) unstable; urgency=low * New upstream version * Recommends: ginkgocadx Closes: #633947 (while the bug requested a "Depends" this is currently most probably not wanted as long as ginkgocadx is not in testing because it would prevent gnumed-client migration to testing) -- Andreas Tille Mon, 01 Aug 2011 13:38:27 +0200 gnumed-client (0.9.7-1) unstable; urgency=low * New upstream version * Fixed Vcs fields -- Andreas Tille Fri, 08 Jul 2011 14:32:35 +0200 ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/828562 Title: [Sync request] Please sync gnumed-client 0.9.9-1 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnumed-client/+bug/828562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719365] Re: gnumed-client 0.7.9 in Maverick cannot connect to salaam.homeunix.com
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 in Maverick cannot connect to salaam.homeunix.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnumed-client/+bug/719365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719365] [NEW] gnumed-client 0.7.9 in Maverick cannot connect to salaam.homeunix.com
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. http://lists.gnu.org/archive/html/gnumed-devel/2011-02/msg00030.html Unless the GNUmed team will get a stable release update into Maverick the workarounds are: 1.) Update to GNUmed 0.8.6-2 and higher from the GNUmed PPA 2.) manually correct the config file to point to publicdb.gnumed.de instead of salaam.homeunix.com We will file a stable request update bug seperately. Best regards, GNUmed team ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- 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 in Maverick cannot connect to salaam.homeunix.com -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719361] [NEW] Please sync gnumed-client 0.8.6-2 (universe) from Debian unstable (main)
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- client_0.8.6-1.dsc 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 -- Andreas Tille Mon, 14 Feb 2011 22:11:05 +0100 Background: The public server salaam.homeunix.com is not available any more. Anone selecting that (default) in the login dialog will not get connected. The above version ship an updated config file (new server publicdb.gnumed.de) Thanks, GNUmed team ** Affects: gnumed-client (Ubuntu) Importance: Wishlist Assignee: Bhavani Shankar (bhavi) Status: In Progress ** Description changed: Binary package hint: gnumed-client - Binary package hint: gnumed-server - 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. + 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- client_0.8.6-1.dsc 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 + * debian/control: Fix server version in Recommends (s/v13/v14/) + * debian/conf/gnumed-client.conf: New public server address - -- Andreas Tille Mon, 14 Feb 2011 22:11:05 +0100 + -- Andreas Tille Mon, 14 Feb 2011 22:11:05 +0100 Background: The public server salaam.homeunix.com is not available any more. Anone selecting that (default) in the login dialog will not get connected. The above version ship an updated config file (new server publicdb.gnumed.de) Thanks, GNUmed team -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719361 Title: Please sync gnumed-client 0.8.6-2 (universe) from Debian unstable (main) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 607394] Re: Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main)
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 ideal solution would be to sync the client (0.7.8) and the server to sync the version numbers. Since maverick is only 26 days away I doubt that 0.7.8 will make it into Maverick. server 13.7 and 13.8 are identical so I vote for server 13.7 if there is no sync of client 0.7.8 Sebastian -- Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/607394 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607394] Re: Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main)
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 printing shutdown message and debugging enabled by previous exception but no log window FIX: exception when shutting down backend listener because connection can already be closed The upgrade does NOT require any changes to your existing (13.7) gnumed_v13 database. -- Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/607394 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607394] Re: Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main)
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607394] Re: Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main)
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 FreeDIAMS [thanks J.Busser] FIX: be more careful around changing CWD when creating document from LaTeX [thanks S.Hilbert] FIX: exception when save-all'ing multiple notelets [thanks S.Reus, J.Busser] FIX: exception when saving medication where is_long_term is true [thanks J.Busser] 13.6 -> 13.7 NEW: improved detection of unicode support in server encoding NEW: work around os.getcwd() permission problem on Mac FIX: even more robust gmPsql.py unicode logging [thanks E.Kuznetsov] This release does NOT require a database upgrade. and for 13.5 to 13.6 I have released GNUmed 0.7.6 which is a bug fix only maintenance release: 0.7.6 FIX: faulty variable access when detecting OOo UNO bridge [thanks S.Hilbert] FIX: fail on "allergy_state" placeholder when date-last-checked not available [thanks Marc] FIX: fail to properly log non-ascii PostgreSQL messages on ASCII configured Pythons [thanks E.Kuznetsov] FIX: faulty access to PG connection filedescriptor when polling for notifications [thanks J.Busser] FIX: exception when aborting person creation while adding new staff [thanks Manuel] FIX: def_country undefined when def_region not set Going from 0.7.5 to 0.7.6 does NOT require a database upgrade, as usual. I hope you manage to include gnumed-server 13.7 as otherwise a flood of already fixes bugs will be reported. We have seen that before. -- Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/607394 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607394] Re: Please sync gnumed-server 13.6-1 (universe) from Debian unstable (main)
** 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 the experience of GNUmed on Ubuntu. http://ftp.de.debian.org/debian/pool/main/g/gnumed-server/gnumed- - server_13.6-1.dsc + server_13.7-1.dsc - gnumed-server (13.6-1) unstable; urgency=low + gnumed-server (13.7-1) unstable; urgency=low * New upstream version -* Standard-Version: 3.9.0 (no changes needed) - -- Andreas Tille Tue, 29 Jun 2010 09:53:11 +0200 + -- Andreas Tille Mon, 19 Jul 2010 22:10:43 +0200 + + gnumed-server (13.6-1) unstable; urgency=low + + * New upstream version + * Standard-Version: 3.9.0 (no changes needed) + + -- Andreas Tille Tue, 29 Jun 2010 09:53:11 +0200 ** Summary changed: - Please sync gnumed-server 13.6-1 (universe) from Debian unstable (main) + Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main) -- Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/607394 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607394] [NEW] Please sync gnumed-server 13.6-1 (universe) from Debian unstable (main)
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 GNUmed on Ubuntu. http://ftp.de.debian.org/debian/pool/main/g/gnumed-server/gnumed- server_13.6-1.dsc gnumed-server (13.6-1) unstable; urgency=low * New upstream version * Standard-Version: 3.9.0 (no changes needed) -- Andreas Tille Tue, 29 Jun 2010 09:53:11 +0200 ** Affects: gnumed-server (Ubuntu) Importance: Undecided Status: New -- Please sync gnumed-server 13.6-1 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/607394 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607393] [NEW] Please sync gnumed-server 13.6-1 (universe) from Debian unstable (main)
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 GNUmed on Ubuntu. http://ftp.de.debian.org/debian/pool/main/g/gnumed-server/gnumed- server_13.6-1.dsc gnumed-server (13.6-1) unstable; urgency=low * New upstream version * Standard-Version: 3.9.0 (no changes needed) -- Andreas Tille Tue, 29 Jun 2010 09:53:11 +0200 ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: gnumed-client (Ubuntu) Status: New => Invalid -- Please sync gnumed-server 13.6-1 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/607393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607246] [NEW] [Sync request] Please sync gnumed-client 0.7.7 (universe) from Debian unstable (main)
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 related to the experience of GNUmed on Ubuntu. http://ftp.de.debian.org/debian/pool/main/g/gnumed-client/gnumed-client_0.7.7-1.dsc http://ftp.de.debian.org/debian/pool/main/g/gnumed-server/gnumed-server_13.6-1.dsc gnumed-client (0.7.7-1) unstable; urgency=low * New upstream version * Recommends: texlive-latex-recommended, texlive-latex-extra * Recommends: freediams -- Andreas Tille Sat, 17 Jul 2010 22:28:55 +0200 gnumed-client (0.7.6-2) unstable; urgency=low * Moved Pre-Depends: adduser from gnumed-common to Depends gnumed-client-de (actually it is only used to clean up previosely introduced group gnumed and should be removed after next release cycle) * Move delgroup call for cleaning up now unused group from debian/gnumed-client-de.postrm to debian/gnumed-client-de.prerm to make sure adduser really is installed at the time of calling Closes: #586200 -- Andreas Tille Fri, 02 Jul 2010 08:38:18 +0200 gnumed-client (0.7.6-1) unstable; urgency=low * New upstream version * Standards-Version: 3.9.0 (no changes needed) * debian/gnumed-client-de.README.Debian explains how to work with chipcards in Germany -- Andreas Tille Tue, 29 Jun 2010 09:38:14 +0200 ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- [Sync request] Please sync gnumed-client 0.7.7 (universe) from Debian unstable (main) https://bugs.launchpad.net/bugs/607246 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580949] Re: new upstream version available: 0.6.3 (bug-fix-only)
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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518784] Re: new upstream (0.6.1) available at Debian/Unstable
** 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: http://ftp.de.debian.org/debian/pool/main/g/gnumed-client /gnumed-client_0.6.1-1.diff.gz Thanks, Sebastian -- new upstream (0.6.1) available at Debian/Unstable https://bugs.launchpad.net/bugs/518784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518784] [NEW] new upstream (0.6.1) available at Debian/Unstable
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 /gnumed-client_0.6.1-1.diff.gz Thanks, Sebastian ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- new upstream (0.6.1) available at Debian/Unstable https://bugs.launchpad.net/bugs/518784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 517170] Re: new upstream (0.6) available at Debian/Testing and PPA
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 the FeatureFreeze so please consider syncing the bugfix release. client version 0.6.1 and server 12.1 http://packages.qa.debian.org/g/gnumed-client.html http://ftp.debian.org/debian/pool/main/g/gnumed-client/gnumed-client_0.6.1-1.dsc http://packages.qa.debian.org/g/gnumed-server.html http://ftp.debian.org/debian/pool/main/g/gnumed-server/gnumed-server_0v12.1-1.dsc Thanks, Sebastian -- new upstream (0.6) available at Debian/Testing and PPA https://bugs.launchpad.net/bugs/517170 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330473] Re: Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable (main)
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330473] Re: Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable (main)
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) https://bugs.launchpad.net/bugs/330473 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330473] Re: Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable (main)
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411954] [NEW] [Sync request]: gnumed-client_0.4.7-1 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 unstable (main) https://bugs.launchpad.net/bugs/411954 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 375874] Re: gnumed - SRU - "new upstream available" - 0.4.4
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
development branch.
Done. https://bugs.launchpad.net/ubuntu/+source/gnumed-
client/+bug/375874
>Update the bug report description and make sure it contains the following
information:
>A statement explaining the impact of the bug on users and justification for
backporting the fix to the stable release
Done in bug report
> An explanation of how the bug has been addressed in the development branch,
including the relevant version numbers of packages modified in order to
implement the fix.
Done in bug report
> A minimal patch applicable to the stable version of the package. If
preparing a patch is likely to be time-consuming, it may be preferable to get
a general approval from the SRU team first.
Patch does not make sense. If only the single issue is fixed than we skip the
other (not neccessarly reported) bugs.
Debdiff is here: https://launchpad.net/~gnumed/+archive/ppa/+files/gnumed-
client_0.3.12-ubuntu1~ppa3_0.4.4-1.diff.gz
> Detailed instructions how to reproduce the bug. These should allow someone
who is not familiar with the affected package to reproduce the bug and verify
that the updated package fixes the problem. Please mark this with a line "TEST
CASE:".
Test case:
#1 Set your timezone to CLT and run GNUmed. This bug will appear:
> 2009-04-20 00:26:49 WARNING gm.database (/var/lib/python-
support/python2.6/Gnumed/pycommon/gmPG2.py::__validate_timezone() #186): time
zone [CLT] seems invalid
> 2009-04-20 00:27:04 ERROR gm.person (/var/lib/python-
support/python2.6/Gnumed/business/gmPerson.py::__init__() #762): cannot
instantiate staff instance
...
> DataError: unable to parse time
Set your timezone to GMT and try again to see it works.
> A discussion of the regression potential of the patch and how users could
get inadvertently effected.
The upgrade could have introduced ne bugs. We know our userbase that has this
running in production very well. They have confirmed that it works. Most
user's affected are the drive-by tryout user which are not affected as they do
not run production systems.
>Use Nominate for release to mark the bug as an SRU candidate for the
appropriate Ubuntu releases (e. g. the current LTS and latest stable release),
then subscribe ubuntu-sru for packages in main/restricted, or motu-sru for
packages in universe/multiverse.
Done.
> Upload the fixed package to release-proposed with the patch in the bug
report, a detailed and user-readable changelog, and no other unrelated
changes.
This requires upload previledges, doesn't it. I have the fixed version in the
PPA
https://launchpad.net/~gnumed/+archive/ppa
Changelog:
gnumed-client (0.4.4-1) unstable; urgency=low
* New upstream version
-- Andreas Tille Sat, 02 May 2009 00:12:23 +0200
gnumed-client (0.4.3-1) unstable; urgency=low
* New upstream version
* Do not ship /etc/gnumed/gnumed-client_public.conf any more
-- Andreas Tille Mon, 20 Apr 2009 14:54:58 +0200
gnumed-client (0.4.2-1) unstable; urgency=low
* New upstream version
* debian/control: gnumed-doc only suggests dwww to not force
people installing Apache.
* Depends: ${misc:Depends} (as suggested by lintian)
* Do not Recommmend libchipcard3-tools any more because it is
outdated
* Standards-Version: 3.8.1 (no changes needed)
* Provides: ${python:Provides} for gnumed-client and gnumed-common
* Removed outdated {Provides,Replaces,Conflics} for old packaging
stuff.
* debian/pyversions: s/2\.3/2.4/
* debian/tools/gnumed: Add GNUmed dir to PYTHONPATH
* Depends: python-egenix-mxdatetime
-- Andreas Tille Wed, 18 Mar 2009 12:00:27 +0100
gnumed-client (0.3.12-1) unstable; urgency=low
* New upstream version
* Watch file now parses developer release page to work around
unsifficient uscan - watch file magic which is not sufficient
to ignore RC releases of upcoming new version (Thanks to Paul
Wise)
* New /usr/bin/gnumed according to a suggestion of Josselin
Mouette and Karsten Hilbert to work better with new python-support
Closes: #516037
(Remark: The GNUmed Python modules do remain for the moment in
usr/share/python-support/gnumed-client do keep compatibility with
Lenny for some time.)
-- Andreas Tille Mon, 02 Mar 2009 15:46:15 +0100
gnumed-client (0.3.10-1) unstable; urgency=low
* New upstream version.
-- Andreas Tille Wed, 11 Feb 2009 22:08:07 +0100
> Make sure that the version number does not conflict with any later and
future version in other Ubuntu releases (the security policy document has a
well-working scheme which can be used for SRUs.) Also be sure to reference the
SRU bug number in the changelog using the 'LP
[Bug 375874] Re: gnumed - SRU - "new upstream available" - 0.4.4
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 375874] [NEW] gnumed - SRU - "new upstream available" - 0.4.4
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] seems invalid
2009-05-12 05:22:54 ERROR gm.person
(/var/lib/python-support/python2.6/Gnumed/business/gmPerson.py::__init__()
#762): cannot instantiate staff instance
Traceback (most recent call last):
File "/var/lib/python-support/python2.6/Gnumed/business/gmPerson.py", line
760, in __init__
rows, idx = gmPG2.run_ro_queries(queries = [{'cmd': cmd}],
get_col_idx=True, verbose=True)
File "/var/lib/python-support/python2.6/Gnumed/pycommon/gmPG2.py", line 815,
in run_ro_queries
data = curs.fetchall()
File "/usr/lib/python2.6/dist-packages/psycopg2/extras.py", line 60, in
fetchall
return _cursor.fetchall(self)
DataError: unable to parse time
This happens for all users that live in a timezone which cannot be
properly handled by postgresql. We have updated GNUmed to new packages.
These packages are in Ubuntu 9.10 already and really need to be
backported as we receive about two bug reports per week where GNUmed
crashes for those users.
Please consider a stable release update. Packages for GNUmed are in
https://launchpad.net/~gnumed/+archive/ppa
Please sync with gnumed-client 0.4.4 and gnumed-server v10.4
** Affects: gnumed-client (Ubuntu)
Importance: Undecided
Status: New
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330473] [NEW] Please sync gnumed-client 0.3.10-1 (universe) from Debian unstable (main)
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 Wed, 11 Feb 2009 22:08:07 +0100 ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238537] Re: Backport python-psycopg2 2.0.7 to hardy?
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224077] Re: Outdated (buggy) GNUmed version (0.2.8.2) in Hardy
** 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 releases. We are up to 0.2.8.6 now which fixes the reported bugs. Please consider updating the version in Hardy as it really just a bugfix release and no new dependencies or code was introduced. This is a drop in replacement. - Meanwhile a slightly less buggy (but still not yet up to date) version is here: - deb http://ppa.launchpad.net/daniel-rocher/ubuntu hardy main - Please read about it in our Wiki: http://wiki.gnumed.de/bin/view/Gnumed/UbuntuGuideShort + + Update: A to-be-tested version is in the hardy-proposed updates + repository. Please test -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224077] Re: Outdated (buggy) GNUmed version (0.2.8.2) in Hardy
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224077] Re: Outdated (buggy) GNUmed version (0.2.8.2) in Hardy
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224077] Re: Outdated (buggy) GNUmed version (0.2.8.2) in Hardy
(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 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224077] [NEW] Outdated (buggy) GNUmed version (0.2.8.2) in Hardy
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 0.2.8.6 now which fixes the reported bugs. Please consider updating the version in Hardy as it really just a bugfix release and no new dependencies or code was introduced. This is a drop in replacement. Meanwhile a slightly less buggy (but still not yet up to date) version is here: deb http://ppa.launchpad.net/daniel-rocher/ubuntu hardy main Please read about it in our Wiki: http://wiki.gnumed.de/bin/view/Gnumed/UbuntuGuideShort ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154136] Re: gnumed - "new upstream available" - 0.2.7.1
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 a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154136] Re: gnumed - "new upstream available" - 0.2.7.1
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" http://launchpadlibrarian.net/10187855/gnumed.conf.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 of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154136] Re: gnumed - "new upstream available" - 0.2.7.1
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 of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 118435] please backport from gutsy to feisty
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 runs in feisty without problems. reason for request: major bug fixes. gutsy version is the first version really usable while feisty carries more of a demo. Thanks for considering. ** Affects: gnumed-client (Ubuntu) Importance: Undecided Status: Unconfirmed ** Description changed: Hi, Please consider backporting gnumed from gutsy to feisty. - Version in gutsy : https://launchpad.net/ubuntu/+source/gnumed- - client/0.2.5.0-1ubuntu1">0.2.5.0-1ubuntu1 + 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">0.2.4.2-1ubuntu1 + Version in feisty: https://launchpad.net/ubuntu/+source/gnumed- + client/0.2.4.2-1ubuntu1 Initial tests show gutsy version runs in feisty without problems. reason for request: major bug fixes. gutsy version is the first version really usable while feisty carries more of a demo. Thanks for considering. -- please backport from gutsy to feisty https://bugs.launchpad.net/bugs/118435 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104153] please merge with 0.2.5.0-1
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 bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57818] Re: [Bug 57818] Re: Crash at program start
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 welcome, HTML ->/dev/null Faire Angebote beim Internetshoppen gibt es in meinem Onlineshop fairdeal.profiseller.de -- Crash at program start https://launchpad.net/bugs/57818 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57818] Re: Crash at program start
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28754] Re: wxPython bindings missing to start GNUMed
It's not a bug in GNUmed but rather the Debian package of it which carries different dependencies than Ubuntu Dapper provides. There a three ways to fix this. 1) Use GNUmed from source instead of packages and it will work fine on Dapper 2) Use new version 0.2.x from upstream Debian but needs additional packages Dapper doesn't carry (newer version) 3) Change the Debian package into a Dapper package and fix the dependencies All is fine with GNumed on Edgy -- wxPython bindings missing to start GNUMed https://launchpad.net/bugs/28754 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57818] Re: Crash at program start
Please provide us with the GNUmed log file It's called gnumed.log and can be found in '~/.gnumed/gnumed.log'. We will be happy to investigate the issue. A new version has been released upstream including Debian package of fixes. Please let me know how it works out. Sebastian Hilbert GNUmed project -- Crash at program start https://launchpad.net/bugs/57818 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
