Your message dated Sun, 23 Feb 2020 22:22:57 +0000 with message-id <[email protected]> and subject line Bug#947743: Removed package(s) from unstable has caused the Debian Bug report #851220, regarding mongodb-server: broken upgrade from 2.6 to 3.2 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 851220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851220 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mongodb-server Version: 1:3.2.11-2 Severity: normal My mongo database stopped working after upgrading to the latest version in stretch, which changed from mongo 2.6 to 3.2. mongod would not start, complaining that authSchemaUpgrade needed to be run first (and only on a 2.6 server, which was no longer available). I ended up downloading the 2.6 tarball from the mongo website and running that version of mongod against my database in /var/lib so I could do the authSchemaUpgrade. After that the new 3.2 version seemed to work OK. In case anyone else gets stuck like this, I basically did this: $ sudo mongod2.6 --noauth --dbpath /var/lib/mongodb & $ mongo > use admin > db.runCommand({authSchemaUpgrade:1}) ^D I'm not sure if this could be detected or automated, but I wasted a lot of time. I don't think there should be a "silent" upgrade across major versions like this when there are such incompatible changes. Perhaps have mongodb-2.6, mongodb-3.2, etc. packages available concurrently in the archive, with mongodb pulling in the "current" one.
--- End Message ---
--- Begin Message ---Version: 1:3.4.18-2+rm Dear submitter, as the package mongodb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/947743 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
