#1005757 python-jsonschema: Please provide latest upstream release 4.4.0

#1005757#5
Date:
2022-02-14 13:50:18 UTC
From:
To:
Dear Maintainer,

I am currently packaging dtschema (see ITP #1005301 [0]). This package
seems to use a validator introduced in 2019 but not available in the
current 3.2 release.

Here is the test failing during package build:


It seems to be that providing the latest 4.4.0 release should solve this
issue, and allow me to finish the packaging of the dtschema package. The
`Draft201909Validator` was introduced a commit 6 months ago in upstream
[1].

Bests regards,

Agathe.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005301
[1] https://github.com/Julian/jsonschema/commit/d104bdbe2ce3f283e4e2bbf2a5fe7f6f7d6f7280

#1005757#12
Date:
2022-05-03 07:27:30 UTC
From:
To:
Hi,

Any news concerning this request? If the versions are not compatible or
this cannot be updated, I may create ITP "python-jsonschema4" and
maintain it under Debian Python Team.

Bests,

Agata.

#1005757#17
Date:
2022-05-05 13:21:03 UTC
From:
To:
Hi,

python-jsonschema is packaged as part of the OpenStack components. Until
OpenStack upgrades to that version, I wont be upgrading the package.
Thanks for your understanding.

Cheers,

Thomas Goirand (zigo)

#1005757#22
Date:
2022-05-29 13:08:15 UTC
From:
To:
Hello all,

The recent releases of ansible-lint (>= 6.1.0) requires python-jsonschema
other changes required from that release):
https://github.com/python-jsonschema/jsonschema/pull/940

Thomas, are you aware of anything specific which will break openstack
or is it because it hasn't been tested yet?

Thank you,

#1005757#31
Date:
2022-06-12 10:13:59 UTC
From:
To:
Hi,

I would also like to stress that I would like to see dt-schema moving to a version that one can actually use for current
Linux kernel's device tree checking. As of now I have to pip install jsonschema and dt-schema for this use case.

Lots of kernel developers on Debian will be thankful for this to be resolved.

Thanks,
Bastian

#1005757#36
Date:
2022-06-12 22:26:29 UTC
From:
To:
It's because it hasn't been tested yet. I've seen many cases were
uploading a single package breaks everything...

Since I added so many autopkgtest, what I can do is upload the latest
version to Experimental, and let the Debian CI run its tests against
what's currently in Unstable. Then the pseudo excuse page will show how
it goes.

Maybe you can also deal with the latest version of python-jsonschema in
Experimental for a short time too?

Note I wrote to the OpenStack list and ask if we can upgrade jsonschema.
Please allow a few days until I get some replies.

Cheers,

Thomas Goirand (zigo)

#1005757#39
Date:
2022-06-13 13:02:22 UTC
From:
To:
Hello,

Bug #1005757 in python-jsonschema reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/third-party/python-jsonschema/-/commit/546fd5dbfbfdff7ff6254c517a6fd0a9b20070fe
------------------------------------------------------------------------
d/changelog Closes: #1005757
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005757

#1005757#44
Date:
2022-06-13 13:02:21 UTC
From:
To:
Hello,

Bug #1005757 in python-jsonschema reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/third-party/python-jsonschema/-/commit/546fd5dbfbfdff7ff6254c517a6fd0a9b20070fe
------------------------------------------------------------------------
d/changelog Closes: #1005757
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005757

#1005757#49
Date:
2022-06-13 13:19:15 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
python-jsonschema, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1005757@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand <zigo@debian.org> (supplier of updated python-jsonschema package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 13 Jun 2022 10:51:08 +0200
Source: python-jsonschema
Architecture: source
Version: 4.6.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack <team+openstack@tracker.debian.org>
Changed-By: Thomas Goirand <zigo@debian.org>
Closes: 1005757
Changes:
 python-jsonschema (4.6.0-1) experimental; urgency=medium
 .
   * New upstream release (Closes: #1005757).
   * Switch to pybuild and poetry, as upstream switch to shipping a
     pyproject.toml instead of setup.cfg.
   * Added optional dependencies as Recommends:.
   * Refreshed remove-sphinxcontrib.spelling-from-doc-conf.py.patch.
   * Rebased fix-lintian-privacy-breach.patch.
   * Add python3-hatch-vcs and python3-hatchling as build-depends.
   * Fix PYTHONPATH when building sphinx doc.
   * Add do-not-use-furo-theme.patch.
Checksums-Sha1:
 2b749e412e2d12224f02f9eccce4d9efa5175b93 2741 python-jsonschema_4.6.0-1.dsc
 1bba1175e8f2c4134c0cc08fee3075407fb5b415 122608 python-jsonschema_4.6.0.orig.tar.xz
 9672d516506ae9e23c8acc86640d124462b858cf 6372 python-jsonschema_4.6.0-1.debian.tar.xz
 92256af2c190aec0fe2a92ef54d2ff609c204267 10189 python-jsonschema_4.6.0-1_amd64.buildinfo
Checksums-Sha256:
 1a3d651dec26abfdffb88af07153bddaa0771dfb40ab255991f2d5c26bc8d146 2741 python-jsonschema_4.6.0-1.dsc
 046773d038f5d7d2807afb2c73da5a943fd7a7dd9bdacc17d5b7b12420d539b2 122608 python-jsonschema_4.6.0.orig.tar.xz
 52ae2254a068ac8d1bb22dae0b0858e98389a0c9510502b475f0c281548a8b0e 6372 python-jsonschema_4.6.0-1.debian.tar.xz
 96327b74ff512f36550608de9ff4f09263b76d398ff3a09e1771d6c8d7bb1925 10189 python-jsonschema_4.6.0-1_amd64.buildinfo
Files:
 1ce5aa34d380fc4d5d247877ed5ffc6f 2741 python optional python-jsonschema_4.6.0-1.dsc
 a0b804f127181384c357a92cae0be9f0 122608 python optional python-jsonschema_4.6.0.orig.tar.xz
 19a9110220db79aaf3dbe96a199845e9 6372 python optional python-jsonschema_4.6.0-1.debian.tar.xz
 6ea7591e18710395a125feb2c4ec55a5 10189 python optional python-jsonschema_4.6.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmKnNfAACgkQ1BatFaxr
Q/6HTxAAhPsANqgiZ5C34W8typ+RiKKONvfLBXBfXdLwP/3m2KUY2bEKLyNogKq+
jESECLwx2mGGY/OnUOyN2F96Y5vuWNXHa9UXXos0OSK2hrUI1mJUVhmybMZLszeY
AEBS1VsKqjb9n8reFHaxehgikSukYL133xSYQEApG3oxAtkJe1RxfNnHa1QQ2Zxg
fMIqhm277FI4U5bappGDAkw2x7Z7H/r5iVXRMdE4xt57x0EKVnmQlUiBL/ppBgcx
cif+zp8PWXIJ9xHxr83dKv4EiUzMJpLg0b6UyGLrr3hvNDK+SFhtKg7mAiPxkryH
SYMXjqYMf/pJ+H2t5TH4S7D4x7DS0UmAkBMkFtJxCYamSTUSJG64bYYN5zWDfFTf
kFQjgTLdhHMeJhaC+hfqEawZ4ouxiZPM0HlGyaaMxaIsavNrsT18m2fz4G29lFGg
0ESSBA/fdoOKfl3qozihCVEVWeXdvKYxcFr+EHNtnYm6aGvJhmT8bh07QktcPf7m
UXFqsl4XdcMRzz+lpyJNedkFsBD5v3b649DPNkbklQqYlH0Q1CRdlPnjxA5pgwdi
OHZ9BmdS8xOMW8Fw/kQqrfyLZRRtw5zbGUv7LJSjYRWF999zgPdnAURSOvQCKfrF
LNu5Bc61wVk/z3jQ6YlWUqkZxhzw9f3FwN2WnGmSzUe1mbOBEK4=
=surj
-----END PGP SIGNATURE-----

#1005757#54
Date:
2022-06-14 20:44:18 UTC
From:
To:
Hello Thomas,

That would certainly be helpful, the diff on ansible-lint is slowly
growing so it would be good to at least have it in experimental.

Awesome, thank you!

#1005757#59
Date:
2022-06-14 22:43:19 UTC
From:
To:
You probably saw I uploaded 4.6.0 to Experimental already. Let me know
if it works well enough for you. I had to redesign a bit the package as
upstream switched to Poetry (from setuptools).

As you can see from here:
https://release.debian.org/britney/pseudo-excuses-experimental.html#python-jsonschema

there are many regressions in OpenStack, as I expected. The most
worrisome is the Nova one (Nova is the core of OpenStack, the one that
spawns VMs...).

I'd very much prefer to have enough time to fix them before uploading
jsonschema 4.6.0 to Unstable.

Cheers,

Thomas Goirand (zigo)