Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Won't Do
-
None
Description
currently, there is no code that compares the version passed the curator and the version in the file name of the packages themselves, which makes it easy to accidentally put packages of the wrong version into a repository.
This is particularly a problem during manual and rebuilds, which are uncommon.
The versions in the package names and the version that would likely be passed into curator have different formats, which makes this not super stressful.
Attachments
Issue Links
- related to
-
SERVER-26583 MongoDB 3.4 packages appearing in 3.2 repo when running yum update
-
- Closed
-