http://bugzilla.opensuse.org/show_bug.cgi?id=1122267 http://bugzilla.opensuse.org/show_bug.cgi?id=1122267#c7 --- Comment #7 from Arjen de Korte <suse+build@de-korte.org> --- (In reply to Alberto Planas Dominguez from comment #6)
(In reply to Arjen de Korte from comment #5)
Nine months have passed and MongoDB is still available (and being maintained) in Factory and therefore released in Tumbleweed. Is this intentional?
I can see that the one in factory is still under AGPL-3.0, and this is OK
No, that is not OK. Any MongoDB release after Oct 16 2018 is SSPL-1.0. The latest version in factory is 3.6.13 which was released Jun 10 2019, so this is well after that date. So although the license in the .spec file says 'AGPL-3.0', this is wrong and actually should be 'SSPL-1.0'. The last MongoDB 3.6 release under the AGPL-3.0 would have been 3.6.8, released Sep 19 2018.
Can development continue with for instance MongoDB 4.2 and might this eventually land in Factory, or am I just wasting my time on that?
No, 4.2 will not land in Factory, as is under SSPLv1 license, and we cannot redistribute this software : (
Clear.
Technically the last SR in the devel project, that update the license, is also not OK, but as we do not redistribute it via Tumbleweed nor Leap, maybe is not so wrong.
I beg to differ. MongoDB is *still* being distributed through Tumbleweed.
But now that the license in the devel project changed, a SR to Factory would trigger a review from legal, that I would expect that will decline the SR.
-- You are receiving this mail because: You are on the CC list for the bug.