https://bugzilla.redhat.com/show_bug.cgi?id=2005122
Ben Beasley <code(a)musicinmybrain.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |code(a)musicinmybrain.net
Flags| |needinfo?(sanjay.ankur@gmai
| |l.com)
--- Comment #1 from Ben Beasley <code(a)musicinmybrain.net> ---
I was going to find the commit corresponding to the PyPI tarball, even though
upstream did not tag it, and suggest using that for the tests—but there isn’t
one!
The actual package sources (i.e., lazy_ops/ directory) match
https://github.com/catalystneuro/lazy_ops/commit/407504d1c4b1447e9527e7bd...,
but setup.py is not updated for 0.2.0 in that commit.
In the next commit, the version is 0.2.1, which is newer than any PyPI release,
and there are additional changes in lazy_ops/.
-----
I guess something still has to be done, because there is no license file in the
PyPI tarball, and the BSD license requires the license/copyright text to be
reproduced
(
https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidel...).
The more aggressive option would be to combine the GitHub tarball for commit
407504d1c4b1447e9527e7bddd771b6cc6f4810a with the PyPI 0.2.0 release tarball,
using only the setup.py from the latter. That would give you the license file
*and* let you run the tests.
Or, you could keep the PyPI tarball as you have it, and add
https://github.com/catalystneuro/lazy_ops/raw/407504d1c4b1447e9527e7bddd7...
as an additional source, still forgoing the tests.
What do you think?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2005122