Hi
I'm working on packaging pgadmin4-7.0, which bumped several python dependencies, requiring multiple updates of existing fedora packages. I started by building newer version of all direct dependencies in copr [1], and then investigating the dependencies trees of the direct dependencies. So here come the questions:
- It is kinda hard to know which python dependencies are really affected. What is the best practice? Just limiting to checking those which have a version-constrained dependency which would not be satisfied by the update?
- So far I've filed multiple PRs for the various dependencies, but it is fairly unrealistic to have these all processed in a timely manner. I'm assuming the best way forward is a self-contained change?
Thanks Sandro
[1] https://copr.fedorainfracloud.org/coprs/smani/pgadmin4-7.0/builds/
On ti, 02 touko 2023, Sandro Mani wrote:
Hi
I'm working on packaging pgadmin4-7.0, which bumped several python dependencies, requiring multiple updates of existing fedora packages. I started by building newer version of all direct dependencies in copr [1], and then investigating the dependencies trees of the direct dependencies. So here come the questions:
- It is kinda hard to know which python dependencies are really
affected. What is the best practice? Just limiting to checking those which have a version-constrained dependency which would not be satisfied by the update?
- So far I've filed multiple PRs for the various dependencies, but it
is fairly unrealistic to have these all processed in a timely manner. I'm assuming the best way forward is a self-contained change?
This is not a self-contained change if for PostgreSQL admininstration it bumps bunch of packages like python-cryptography and python-gssapi. ;)
Is there a real need to bump them? Specifically, python-cryptography does break a lot with its changes -- we got broken twice in FreeIPA in this year.
Thanks Sandro
[1] https://copr.fedorainfracloud.org/coprs/smani/pgadmin4-7.0/builds/
-
Alexander Bokovoy -
Sandro Mani