On 26-Aug-2017, Hugo Lefeuvre wrote:
> I'm currently facing issues with my GnuPG key which prevent me from
> uploading this package to unstable (I'm waiting for the next keyring
> update to replace my key).
Sorry to learn of the roadblock.
> If you want to co-maintain this package, feel free to add your name
> to the Uploaders field and upload it to unstable.
My motivation is to have the package as a dependency for ‘pyethapp’
which I am working on.
> Some things you should notice, however:
> * This is a Python 2 package only
> * Upstream is planning to make a Python 3.{0,2}, but I think it's
> not going to happen soon unless you ping him/open a bug report.
Some more issues (some of these are issues I've reported upstream):
* The GitHub repository has only one release made available
<URL:https://github.com/digitalemagine/py-statistics/releases>, and
has none of the versions from the PyPI page
<URL:https://github.com/digitalemagine/py-statistics/issues/4>.
* The version at GitHub, version “3.4.0b3”, is not available
at PyPI <URL:https://pypi.org/project/statistics/>
<URL:https://github.com/digitalemagine/py-statistics/issues/5>.
So for distributions depending on the version at PyPI, currently
“1.0.3.5”, it's not clear that they will work correctly with this
later version.
* The Debian package version does not mangle the version to place
“3.4.0b3” earlier than (what will presumably be released later as)
“3.4.0”. When upstream makes a “3.4.0” release, it will sort
*earlier* in Debian than the existing upstream version “3.4.0b3”.
This can be corrected with an appropriate change to the version
string for future Debian releases, but that doesn't solve the issue
for the already-released “3.4.0b3-1”.
What are your thoughts on addressing these?
--
\ “Every decent man is ashamed of the government he lives under.” |
`\ —Henry L. Mencken |
_o__) |
Ben Finney <bignose@debian.org>
Attachment:
signature.asc
Description: PGP signature