This is what I've found:
Our code does not explicitly install or use chardet; however, some of the
dependencies our code does install/use have chardet as a dependency and may be
using it.
I believe I've identified all the dependencies resulting in chardet being
installed and am working to upd
Hi Justin,
I checked more thoroughly and that requirements file doesn't appear to be used
anywhere so I've deleted it. However, I did also check the docker images built
from this release candidate and found chardet installed in a number of them
(not explicitly, but in the installation process o
Hi,
I just looked in the requirements file and remembered that chardet was
LGPL-licensed, but I assume there’s an automated way to do it.
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional c
I had voted +1 on dev@ but I'm changing my vote until we clarify the
use of chardet:
0 (binding)
Is there an automated way to check the licenses of Python dependencies
(analogous to how Java-based projects use RAT)? It would be useful for
me (not a Python expert but voting on releases) and the pr
Hi,
-1 (binding), as I think you may have an issue here as
apache-sdap-nexus-1.2.0-incubating-src depends on LGPL licensed chardet. [1]
ASF project can not depend on LGPL software unless it is optional. Is this the
case here?
I checked:
- incubating in names
- signatures and hashes are fine
-
Hello everyone,
This is a call for a vote to release Apache SDAP (incubating) release candidate
rc2 for version 1.2.0.
The Apache SDAP community has voted to approve release of Apache SDAP
(incubating) version 1.2.0-rc2.
We now request the Incubator PMC review and vote on this release.
SDAP c
