Source: python-catalogue Version: 2.1.0-6 Severity: normal X-Debbugs-Cc: Andreas Tille <ti...@debian.org>, debian-de...@lists.debian.org
https://pypi.org/project/catalogue/#history shows that 2.1.0 was yanked from PyPI, but it's what we currently have in Debian. Some of the more recent releases (which I think are really in the same version series - it's just that upstream changed their minds about bumping the patch version) contain fixes that we should have in Debian; in particular while trying to fix python-srsly I ran into a problem which I think is fixed by https://github.com/explosion/catalogue/commit/75f5e9c24e93b5fcc2b3e9f324d9328bc871abad. I'm happy to do the work to get us onto a newer version, but I wanted to check what to use for the version scheme. Should we use 2.1.0+really2.0.10-1 or 1:2.0.10-1? I think there'd be some justification for an epoch here since the upstream version numbering scheme changed (cf. https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-version), but I'm copying debian-devel as per policy on epoch proposals. Thanks, -- Colin Watson (he/him) [cjwat...@debian.org]
