Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mongo support for Bookworm & avoid reinstall #1875

Open
wants to merge 9 commits into
base: dev
Choose a base branch
from

Conversation

gcollin
Copy link

@gcollin gcollin commented Jun 21, 2024

The problem

Only Mongo v7.0 is available for Bookworm. So all applications installing Mongo fails the Bookworm install.
As well can install an older version over a newer one if requested by an application.

Solution

Forced installation of v7 of Mongo if bookworm is detected.
Detects the version of Mongo installed and ensure no regression in installation.
...

PR Status

...

How to test

...

@alexAubin
Copy link
Member

Related notes from @orhtej2 : YunoHost-Apps/wekan_ynh#284 (comment)

but it's not clear to me in the end if an explicit migration is need to go from 4.x to 5 / 6 / 7.x or not ? Possibly we could somewhat magically upgrade mongo and run the appropriate migration stuff similar to what we already do for postgresql

@gcollin
Copy link
Author

gcollin commented Jun 22, 2024

As per the official upgrade documentation, when upgrading Mongo, you just need to ensure step by step upgrade.
https://www.mongodb.com/docs/manual/release-notes/7.0-upgrade-standalone/

And then set the features compatibility to the latest version only if you want by running
db.adminCommand( { setFeatureCompatibilityVersion: "7.0" } )

So for me it's quite safe to upgrade the mongo version whenever it's not available in the target debian release.

What I can do in the script is check that we're not trying to upgrade more than 2 versions deep, and fail the install if so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants