Please sync gnumed-server 13.7-1 (universe) from Debian unstable (main)

you might want to subscribe ubuntu-sponsors for review there

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.

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.

Debian has 13.8-1. Shouldn't we sync it instead? If yes, please copy the upstream changelog for this version also to the bug report.
Please subscribe again sponsors when checked.

Thanks,
Fabrice

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.

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

> 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?

This bug was fixed in the package gnumed-server - 13.7-1

---------------
gnumed-server (13.7-1) unstable; urgency=low

  * New upstream version

gnumed-server (13.6-1) unstable; urgency=low

  * New upstream version
  * Standard-Version: 3.9.0 (no changes needed)
 -- Sabastian Hilbert <email address hidden> Mon, 19 Jul 2010 22:10:43 +0200