Re: Bug#1139559: ITP: python-hypothesis-jsonschema -- hypothesis JSON schema data generator
Simon Josefsson <[email protected]> Sat, 13 Jun 2026 06:52:06 +0200
| Newsgroups | gmane.linux.debian.devel.python |
|---|---|
| Message-ID | <[email protected]> |
--=-=-= Content-Type: text/plain Jeroen Ploemen <[email protected]> writes: > On Tue, 09 Jun 2026 19:02:53 +0200 > Simon Josefsson <[email protected]> wrote: > >> Review of this packaging would be appreciated. > > Most of the upstream testsuite makes use of gen_schemas, which does > not appear to have been packaged in Debian. As a result, no tests are > run on build and 'Testsuite: autopkgtest-pkg-pybuild' should not be > used: all that does under these circumstances is pretend the package > comes with an autopkgtest. Try autopkgtest-pkg--python instead. Thank you for looking at the package! I didn't know about the various python testsuite options. I changed to use autopkgtest-pkg-python now. For future reference, I found explanation of autopkgtest-pkg-pybuild vs autopkgtest-pkg-python here: https://manpages.debian.org/testing/autodep8/autodep8.1.en.html#EXAMPLES_OF_PRODUCED_TEST_CONTROL_FILES I have uploaded this to NEW queue. >> I considered using github instead of pypi tarballs, but it seems >> upstream doesn't push tags to github so figuring which commits to >> pin to and writing the watch file seems complicated... reported as >> https://github.com/python-jsonschema/hypothesis-jsonschema/issues/113 > > You are free to use whichever best suits your needs, there's no team > policy that requires or even prefers one over the other. Usually, it > boils down to the one that includes tests and documentation. Okay. My own preference is now to to use git sources directly. But for this package, understanding which git commit they used for each release seems complicated since they don't publish git tags. And writing a debian/watch for this situation seems impossible. I suspect this isn't intentional by upstream, just some artifact of their workflow (the homepage URL on pypi.org also seems odd... [1]), so this could all be clarified whenever upstream responds. /Simon [1] https://github.com/python-jsonschema/hypothesis-jsonschema/issues/114 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQNoBAEWCgMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmos4fcUHHNpbW9uQGpv c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh BLHSvRN1vst4TPT4xNc89jjFPAa+BQJp4fWRBQkOa+rdAAoJENc89jjFPAa+hWIA /1lQvrJeGlQq50lP6tm99D1zDy7J1tQ3ha4x0Jx7rkFTAP9hpUKuTvm6m1fXyiZV YZlu2+Id/Dq3CIAZvNF+XEr2BLgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0 +MTXPPY4xTwGvgUCaeCW1wUJDmqLVgCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE 8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J ENc89jjFPAa+s7AA+gIIHpBApDpcDj1sKhzDngmpvwQf0VkHme6s+EG7qSgpAQDe /XMrU0c0Pa3ji85cMqZhvzJOFI/soe662lzL0QY3Bbg4BFySz2oSCisGAQQBl1UB BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJp4JbXBQkOaottAAoJENc89jjF PAa+RNUA/2faQO/nFT06E+MlhlQdo/0chlQXC5TZMPTVvVBFwoLOAP9xLJK0ow5E jTzYJB4K810AL/Iv6PEOAEgA4cPTHVlbCQAKCRBRcisI/kdFoqpRAQDBihVgE8al Fy1aL8fPoUsFTKUZjMCmsobngAMAZTkeTQD/WfPfqUmQt+ffMc/LDaKFodwJnmdo bjUMlHrH7o3vnw4= =u8nY -----END PGP SIGNATURE----- --=-=-=--