[MacPorts] #67148: mongodb: Database cleared with upgrade from v5 to v6 (was: Database cleared with upgrade from v5 to v6)

MacPorts noreply at macports.org
Sat Mar 25 21:57:53 UTC 2023

#67148: mongodb: Database cleared with upgrade from v5 to v6
  Reporter:  TheDigitalOrchard  |      Owner:  ryandesign
      Type:  defect             |     Status:  assigned
  Priority:  Normal             |  Milestone:
 Component:  ports              |    Version:
Resolution:                     |   Keywords:
      Port:  mongodb            |
Changes (by ryandesign):

 * status:  new => assigned
 * owner:  (none) => ryandesign


 There's nothing in the mongodb Portfile that should result in databases
 being wiped upon upgrade.

 It is true that there was not any explicit warning that `sudo port upgrade
 mongodb` would increase the major version of mongodb, beyond, of course,
 the output of `port outdated` prior to doing the update. This is no
 different than how all prior upgrades of mongodb were handled in MacPorts,
 though it is different from how most of the other database ports are
 handled in MacPorts. MySQL, PostgreSQL, and BerkeleyDB ports do offer
 separate versioned ports so that the user can decide when to do a major
 version update. Especially considering upstream's lack of support for
 older versions of macOS, it is possible that we might want to switch to
 versioned mongodb ports; it hasn't been done thus far because nobody has
 requested it yet.

 `sudo port unload mongodb` should stop the `mongod` process. Certainly
 restarting the computer will stop all processes.

Ticket URL: <https://trac.macports.org/ticket/67148#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS

More information about the macports-tickets mailing list