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
mongodb: 4.0.12 -> 4.2.8 #92719
mongodb: 4.0.12 -> 4.2.8 #92719
Conversation
/marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The diff looks fine (didn't look at the .patch
es). Some style suggestions.
73d9c84
to
341ae3f
Compare
addressed comments, squashed out the errors i'd made, noticed that github doesn't preserve that history- apologies for that. regardless, PTAL. thanks! |
The PR author cannot set the status to If you are not the PR author and you are reading this, please review the usage of this bot. You may be able to help. Please make an honest attempt to resolve all outstanding issues before setting to |
@GrahamcOfBorg build mongodb-4_2 |
Oh, right. It's unfree now. |
actually just caught an issue with tests- current test is using cross-version clients, and 3.4 to 4.2 doesn't work. quick update inbound. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pinged a few more people that were in the maintainer list. If no one replies in a couple days I'll just set this to needs_merge
In the meantime please prefix the commit messages with their scope, like you did on the first one |
sure. mind if i just squash them out now that you've reviewed? |
That's also fine, yes |
Not strictly an upgrade, but adds a new mongodb-4_2 target with the current mongodb from that branch. Use matching client and server versions in mongodb tests- tests were using the mongo 3.4 client to connect, and this finally doesn't work with server 4.2. Per reviewer suggestion, adding myself as cheetah3 maintainer. Additionally, reestore comments describing the purpose of the build-dependencies patch
/status needs_merger |
Not strictly an upgrade, but adds a new mongodb-4_2 target with the
current mongodb from that branch.
Motivation for this change
Current mongodb isn't packaged, would like it to be.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)