It seems there is a bug lurking; you should have gotten a failure for
whichever package you didn't stick the license in ACCEPTABLE_LICENSES,
not a scan failure.
The new problem is that everything is building with python 38, but it
seems mongodb3 requires python 27 :(
Is there any way to get this to play nicely?
Other than having to hav py3X-scons not installed when you build
mongodb3, and perhaps a desire to get rid of python 27 from yuor system,
is there any real problem?
While I appreciate the efforts to keep the more better licensed
mongodb3 around for unifi controller 5 (Hi Greg!), maybe it's time to
add controller 6 to work with mongodb4?
I didn't realize that 6 uses mongodb4 -- I was only holding off because
of 1) lack or roun tuits 2) no urgent problem using 5 still and 3) still
a bit scared after seeing reports that the first release or two of 6
worked badly enough that people lost the ability to admin their
networks. Now I am down to 1, but such a change is too disruptive just
before the branch.
I am unclear on the mongo 4 license and how problematic it is -- whether
it is merely not open source or truly problematic. I remember a fairly
big kerfluffle when it came out. Of course, the net/unifi license is
not open source, but that's not from a company whose home page seems to
try to sell proprietary licenses to an open-core product but does not
contain the words "open source" or "free software".
Debian has declined to accept it as DFSG-free:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915537
But, we are only talking about adding unifi6 and maybe dropping 5,
nothing more. So there is probably not a reason to do anything other
than update (with adequate functional testing).