Re: Setup in debian 13 (trixie): bugs + fixes

Hola Mar=EDa,

thanks for sharing your findings on Trixie.

Incidentally, I have just upgraded a Bookworm to Trixie and
have not run into any trouble (well, not _on_ Trixie, that
is). I didn't need to bootstrap, though, and an
pg-upgrade_cluster 15->17 ran just fine (does not use
gm-bootstrap).

> */CLIENT/*
>=20
> Two dependencies are not automatically installed with gnumed-client, and=
 thus are missing
> when trying to run the client.
>=20
> =A0=A0=A0 - python3-standard-mailcap

A-ha, good to know. GNUmed did protect itself from loss of
mailcap from the std lib by way of including a copy thereof
within its own codebase and loading that if "import mailcap"
fails.

Did you encounter a downright error when _not_ installing
python3-standard-mailcap or how else did you chance upon
this ?

Added for next release.

> =A0=A0=A0 - python3-packaging

Added for next release.

This is used for parsing the Orthanc (DICOM PACS) server
version.

> Just a simple...
>=20
> =A0=A0=A0 sudo apt install python3-packaging python3-standard-mailcap
>=20
> ... and the client runs, no problem!

Did it not run without the above ?  That would be quite
interesting to know for hardening the startup.

> Explanation that I could gather: Mailcap was part of the Standard Python=
 Lib, but now it was
> removed, so it needs "manual" installation.

Exactly. Except that there is a workaround in place which
really should have kicked in. Would you be able to reproduce
the failure case and any debugging information thereof ?

> Now as for the packaging lib, I don't know why
> it was not automatically installed by apt.

Same here, removed from stdlib...

> I know this is probably something that should be fixed by the debian tea=
m maybe?

Yep, I have added notes for the next release to add these to "Depends:"

> But just
> out of curiosity, how does one go about adding these packages to the dep=
endencies list so
> that apt installs them automatically?

We tell the Debian people that we need that and kindly ask
them to consider the need for the next packaging :)

> Do we get a say in it, so that if for example we add
> these to the prerequisites in gituhub and then the debian team pulls the=
 changes from there?
> Always wanted to know the workings behind package management...

ATM it is manual. There's a multitude of ways of
pre-definining Python dependancies and none so far has
piqued my interest sufficiently. Ne'erthelesse would I be
willing to include contributed (heh :) infrastructure code
to that end, especially if it works towards enabling users
to setup a systemwide venv for the gnumed client.

Best,
Karsten
=2D-=20
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B