Hi.

Thanks for the report.

I discussed this request within the development part of our team and the we are open to updating python3-jsonschema to newer version, since there is only `osbuild` package depending on it in el9 and we maintain it as well.

I wanted to ask whether you would be willing to make a MR in c9s once this bug gets approved for inclusion in the upcoming minor release of RHEL-9? Specifically in https://gitlab.com/redhat/centos-stream/rpms/python-jsonschema

In addition to that, I wanted to ask whether you have any particular 4.x version on your mind? I would propose to take some version from Fedora 37, e.g. https://koji.fedoraproject.org/koji/packageinfo?packageID=13973...

Hi Tomáš,

I'll be happy to make the MR when the time comes, as for the version, my particular requirement is for 
jsonschema >= 4.6.0 so any of the latest build from f37 will do.

I would like to request to update to jsonschema-4.10.0 release that is this build https://koji.fedoraproject.org/koji/buildinfo?buildID=2047311 in RHEL-9

Reason: I keep getting requests to keep updated ansible-lint package in EPEL also and it is the upstream who always quick in adapting all new upstream dependencies.

Please consider update jsonschema to 4.10.0 version.

So I gave it a try and tried to update the python-jsonschema in c9s to 4.10.0.

The result is that since version 4.6.0 (specifically https://github.com/python-jsonschema/jsonschema/pull/957) it added requires on "hatchling" and "hatch-vcs". None of them is available in RHEL-9.

I'm not going to request that these packages are added to RHEL-9 and I'm not going to maintain them, nor is our team. The reason is that this would mean additional work and we don't really need newer python-jsonschema in RHEL-9.

So the end result is that even updating to 4.6.0 won't work because of this. And version lower than 4.6.0 won't help much based on comment #3.

I'm sorry, but I don't see may options how to solve this (other than some team within Red Hat that needs this to step up and package these new dependencies and maintain them going forward, ideally also taking on the maintenance of python-jsonschema if there would be need to update it more regularly).

I'll let everyone comment before I close this as WONTFIX.

Hi @thozza 

First, thanks for the attempt, it's understandable that you can't maintain those extra dependencies. 

Second, since you are stuck in using version 3, could we, as in EPEL9 maintainers, add a new package named python-jsonschema4 more in synch with upstream. 

Either way, feel free to close this bug, unless @pnemade has something to add.

Thanks Tomáš and Chedi for your update here.

I don't think I have any capacity to maintain it within RHEL currently. But I am happy to help for any Fedora or EPEL work as its voluntary work :)

(In reply to chedi toueiti from comment #6)
> Hi @thozza 
> 
> First, thanks for the attempt, it's understandable that you can't maintain
> those extra dependencies. 

No problem. I naively hoped for this bug to be trivial to resolve, but it as it turned out it's not.

> Second, since you are stuck in using version 3, could we, as in EPEL9
> maintainers, add a new package named python-jsonschema4 more in synch with
> upstream. 

We are in fact stuck with any version prior to 4.6.0 AFAICT. I don't see it happening, but we may end up updating python-jsonschema to a 4.x version, but lower than 4.6.0 in the future.

Personally, I don't see any issue with the newer package being added to EPEL-9 under a different name. However it may be against the policy (it may have to conflict with the RHEL-9 package?). Given the situation in el9 and the discussion in this bug, I think that you could at least try asking FESCo for an exception if your request gets denied.

Good luck!

Closing as WONTFIX