-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Packaging
-
ALL
-
Build 16 (06/24/16), Build 17 (07/15/16), Build 18 (08/05/16), Build 2016-08-26, Build 2016-09-19, Build 2016-10-10, Build 2016-10-31, Build 2016-11-21, Build 2016-12-12, Build 2017-01-23
I just wanted to apt-install upgrade MongoDB from our repositories, but I found that mongodb-org 3.2.7 doesn't actually depend on the 3.2.7 versions of the packages it is supposed to be a meta package for. Is this intended, or a bug?
I fixed it by manually upgrading the other packages.
- is duplicated by
-
SERVER-28536 Ubuntu mongodb-org metapackage does not have version deps pinned
- Closed
- is related to
-
SERVER-9016 In redhat, installing old version of mongo-10gen-server package installs newer client package
- Closed