Re: Sponsor request: gnumed-client 1.8.24+dfsg-1 and gnumed-server 22.34-1 (new upstream)

--ckkrOr0wN92BLLch
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Marc

Marc Angermann, on 2026-04-16:
> I've prepared new upstream releases for both GNUmed packages and
> would like to ask for a sponsored upload.
>=20
> =C2=A0 * gnumed-client 1.8.24+dfsg-1
> =C2=A0 * gnumed-server 22.34-1
>=20
> Both are straightforward upstream updates, no packaging changes
> beyond debian/changelog. Upstream tarballs were imported with
> pristine-tar; signed source packages built with
> "dpkg-buildpackage -S -sa" and pass lintian --pedantic with only
> pre-existing warnings (newer-standards-version 4.7.3, missing
> Priority field).

Thanks for your work on these packages, I reviewed changes and
have no problems with your inclusion of the newer upstream
release in its current form, so I proceeded to upload.  :)

I have not been very reactive to the present mail thread, sorry
about that.  I thought the newer upstream release was important
enough before nitpicking on implementation details, so went
ahead.  For next iterations, you may like to investigate whether
reducing the number of issues flagged by lintian is manageable.
Sometimes, changes are pretty routine, like looking up what
changes were brought in the latest Debian Packaging Manual
version[1] and adjust the Standards-Version field appropriately.
Sometimes, changes may be not actionable and it might be
justified to override lintian flags.  Tip: I'm using the command
lintian-explain-tags, followed by the name of the tag, to
rapidly make sense what the issues flagged are about.

[1]: https://www.debian.org/doc/debian-policy/upgrading-checklist.html#vers=
ion-4-7-4

> A short note on gnumed-client: upstream has started publishing
> 1.9 release candidates under downloads/client/1.9/, which makes
> plain `uscan` stop before reaching 1.8/. I used
> `uscan --download-version=3D1.8.24 --force-download` for this build;
> no watch-file change was needed.

Yes, I noticed when looking up how to eventually bump the
d/watch file to version 5.  I think your approach to bump the
version has been the correct one.

Have a nice day,  :)
--=20
  .''`.  =C3=89tienne Mollier <[email protected]>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-

--ckkrOr0wN92BLLch
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmnlL4gACgkQeTz2fo8N
EdpHNg//eYd8QcZp/P9yeJFBrkpRUeYvagHJ5OCDiZ7u/+g9wY0ChN3LyCerORwU
e8TOQNWhwGhT9cIswbvtOyC2szQpgPZK6Z6T/H+pr0QY+F/EHeMr3KkwRn7v3CDo
ovQUJsqhaxrQTMVSjHCubK3+TLOFZYpWuvGyo/7nk/7LyzyWOc1WeGok9aLTrIWL
esIdqW2JMHlsGB0Tw34c8cN3rxhGkPUKFJAAhhJtmktK7SjaCBg7C0hT9Nv+/a8b
hIbR/XylXWkQJTDLqzpzkh65FcZZ8Mp1tW/V5MWeYObD5dRQzNk3i5IkA4TejbMU
/jFaOfah+mD+xMS7KXcUIUym+YzI2U5r+gVXtJkGJns9MAcergcPlLM6ThRQYl3e
jXRG3RF0zJhD2DC01ovoiPAGLxBSU7L1G9Ek9hbf6ObdPVe7eKfILh2Wx66EjlLG
/EVpnTGRgfT/11YnJkPX/B4sm9CbIk/zpokYbrY9afNeK7hxxfDj1TbCfT3WLj4s
OtVMDwKClGKj5RVEp2/lYITnHHnjO2UQ9zbPOGK3O2KKzHoiNURhBbmE9Pi05SKH
fvdhgksRLbbn8ZcvzkyCtXM5Op3gapbUMusXPPmb1R2BpQdEhbLe5TQMtUAaP2WS
cUKuiOwZ6W2byhdF4jC0Oj+/Z3PliiIEwQH6fVxTtgT5zBhh3KE=
=8+gT
-----END PGP SIGNATURE-----

--ckkrOr0wN92BLLch--