On Mon, 10 Dec 2018 11:01:11 +0200 Apollon Oikonomopoulos <apoi...@debian.org> wrote: > Source: mongodb > Version: 1:3.4.15-1 > Severity: serious > Justification: Cannot be properly supported > > MongoDB should not be part of (at least) Buster for the following > reasons: > > - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it > to be included in Buster. > > - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch > to SSPLv1 complicates matters. As discussed in #915537, we will not > be distributing any SSPL-licensed software, and keeping the last > AGPL-licensed version (3.6.8 or 4.0.3) without the ability to > cherry-pick upstream fixes is not a viable option. (I am currently > not considering distributing mongodb in non-free.) > > I will not request removal immediately, to allow other packages time to > adjust their dependencies, but eventually auto-removal will kick in. > > That said, MongoDB 3.4 will probably remain in sid for as long as it is > AGPL-licensed and supported upstream.
is there a future for mongodb in Debian? i'm looking it from the python2 removal side of things, and mongodb is the last r-dep of python-mongodb. as this package is already RC buggy, i may just go ahead and remove that package, that will make mongodb unittest to fail. but on a broader spectrum, how long do you want to keep this package in debian, which is practically un-upgradable, with all the issue that means? Thanks, Sandro
