Bug#965031: python3-numpy: please clarify the license for some files in debian/copyright
On Sun, 26 Jul 2020 15:48:47 -0400 Sandro Tosi wrote: [...] > > Could you be so kind to forward my bug report upstream? > > I can, but what if they have questions or they want to follow up with > *you*? am I supposed to be proxying over their questions to you, your > replies and so on? i dont really want to be in that business. > [...] > Once you reached an agreement with upstream, just let us know Dear Sandro, maybe I am misunderstanding something here. You, as the numpy Debian package maintainer, are certainly not a bystander. The health of the package is indeed your business. To be honest, I assumed that you were more than interested in solving possible DFSG-freeness issues in the package. What I reported seems to be either a less-than-clear debian/copyright file (that should be improved, in order to meet Policy 4.5) or some files which lack an explicit DFSG-free license (needing a fix, in order to meet Policy 2.2.1). At worst, some of those files could be All Rights Reserved and thus undistributable. If this turned out to be confirmed, the Debian Project would be distributing files without proper legal permission to do so. I would not describe this scenario as just a matter between me and NumPy upstream developers... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpF6zmEovlAN.pgp Description: PGP signature
Bug#965031: python3-numpy: please clarify the license for some files in debian/copyright
> I do not have a github account. > Could you be so kind to forward my bug report upstream? I can, but what if they have questions or they want to follow up with *you*? am I supposed to be proxying over their questions to you, your replies and so on? i dont really want to be in that business. Please find a way to communicate with upstream directly: email (they have direct addresses and various mailing lists), discord, or any other method that works for you (and tbh, in 2020, working in opensource and not having a gh account limits your interactions and impact dramatically, so you may want to reconsider that at some point). Once you reached an agreement with upstream, just let us know Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#965031: python3-numpy: please clarify the license for some files in debian/copyright
On Tue, 14 Jul 2020 13:46:33 -0400 Sandro Tosi wrote: > > Please let me know, > > feel free to reach out directly to upstream at > https://github.com/numpy/numpy/issues and bring your licence/copyright > concerns there. I do not have a github account. Could you be so kind to forward my bug report upstream? Thanks for your cooperation. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpcEu7xczJr4.pgp Description: PGP signature
Bug#965031: python3-numpy: please clarify the license for some files in debian/copyright
> Please let me know, feel free to reach out directly to upstream at https://github.com/numpy/numpy/issues and bring your licence/copyright concerns there. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#965031: python3-numpy: please clarify the license for some files in debian/copyright
Package: python3-numpy
Version: 1:1.19.0-1
Severity: important
Hello and thanks for maintaining NumPy in Debian!
While reviewing the package debian/copyright file, I noticed
some files for which only the copyright holder seems to be
documented, but not the license.
These files are:
numpy/core/src/umath/{reduction.c, ufunc_type_resolution.c
numpy/core/src/umath/ufunc_object.c
numpy/core/arrayprint.py
numpy/core/src/multiarray/{arrayobject.c, usertypes.c}
numpy/core/src/multiarray/multiarraymodule.c
numpy/core/src/multiarray/{lowlevel_strided_loops.c.src, nditer_api.c,
nditer_constr.c, nditer_pywrap.c,
nditer_templ.c.src}
numpy/core/src/multiarray/{array_assign_array.c, array_assign.c,
array_assign_scalar.c, datetime_busday.c,
datetime_busdaycal.c, datetime.c,
datetime_strings.c}
doc/cython/c_numpy.pxd, doc/pyrex/c_numpy.pxd
Does the NumPy default license apply to the above files?
If so, it should be more explicitly documented in the debian/copyright
file.
If not, has there been any attempt to get in touch with the copyright
holders and obtain a license, so that these files explicitly meet the
DFSG?
Moreover, the following files
numpy/oldnumeric/ma.py
numpy/ma/*
just say "Released for unlimited redistribution.", which is kind
of laconic for a license.
It is it all the permission we are left with?
Has there been any attempt to get in touch with the copyright holders
and obtain a clearer license, so that these files more explicitly
meet the DFSG?
Please let me know, thanks for your time and dedication!
