Dear Étienne, thanks for looking into this.
> Thanks, it looks like there are no changes too involved. I saw > in the gnumed packages extensive logic to deal with various > issues and dispatch files in several locations and documentation > packages, but it seems most of the heavy lifting is already > done. It should be. Andreas had been packaging GNUmed for the last ten years or so. Off the top of my head I don't recall changes that would ask for a change in packaging infrastructure, this being a maintenance release. > > https://www.gnumed.de/downloads/client/1.8/ > > I could get gnumed-client 1.8.19, no problem so far. > > > https://www.gnumed.de/downloads/server/v22 > > I'm a bit confused by the gnumed-server 22.28 refresh I see on > your web page. Is the 22.28 source code from January already in > sid sufficient, or are there substancial changes? > > (I'm just checking I'm not assuming wrongly. With #1082672 and > the changelog only covering gnumed-client, I'd suppose only the > client is needed. But if not, a server version bump to 22.29 > would have been less confusing and would have had a chance to be > caught by our uscan tool.) I should have been more precise. 1) yes, the existing 22.28 gnumed-server package _should_ suffice because there are no semantic changes 2) however, there might be code cleanup in gnumed-common code which would also "affect" the -server package 3) yes it would have been less ambigous to bump the version Theoretically, only the client is needed. I'll upload 22.29 for good measure ;-) Nevertheless, for the record: any 1.8.19 client will work just fine with a 22.28 database, old or new... Thanks, Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
