I observe that the source package name on PyPI has changed from "configshell-fb" (with hyphen) to "configshell_fb" (with underscore).
Context
I am working on updating the configshell-fb package on Debian and I will change the origin of the source package from GitHub to PyPI because the source tarball on GitHub does not contain the PKG-INFO file that Pybuild uses to determine the version.
So I will update the debian/watch file as well to query PyPI (in reality, a Debian redirector) instead of GitHub as suggested here.
The problem is that the auto-generated watch file (i.e. https://pypi.debian.net/configshell-fb/watch) reports that the latest published version is still 1.3.0. It does not detect version 2.0.0 because of the package name change.
$ uscan --no-download --verbose
uscan info: Looking at $base = https://pypi.debian.net/configshell-fb/ with
$filepattern = configshell-fb-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz))) found
$newfile = https://pypi.debian.net/configshell-fb/configshell-fb-1.1.30.tar.gz
$newversion = 1.1.30
Would you consider publishing a new package on PyPI with the correct package name (i.e. configshell-fb)?
I observe that the source package name on PyPI has changed from "configshell-fb" (with hyphen) to "configshell_fb" (with underscore).
Context
I am working on updating the configshell-fb package on Debian and I will change the origin of the source package from GitHub to PyPI because the source tarball on GitHub does not contain the
PKG-INFOfile that Pybuild uses to determine the version.So I will update the
debian/watchfile as well to query PyPI (in reality, a Debian redirector) instead of GitHub as suggested here.The problem is that the auto-generated watch file (i.e. https://pypi.debian.net/configshell-fb/watch) reports that the latest published version is still 1.3.0. It does not detect version 2.0.0 because of the package name change.
Would you consider publishing a new package on PyPI with the correct package name (i.e. configshell-fb)?