4.1.2
op-ct
tagged this
10 Oct 21:23
Before this patch, dependencies in `metadata.json` and `build/rpm_metadata/requires` were missing upper boundaries and often listed inaccurate lower boundaries. This created an extremely fragile 5.2.X/4.3.X module ecosystem on the Forge, as a major release in any dependency would be certain to break the module. This commit resolves the issue by introducing upper and lower boundaries for each dependency in `metadata.json` and propagates those dependencies to the RPM dependencies listed in `build/rpm_metadata/requires`. The minimum version boundaries were determined from the modules as they were checked out in `simp-core` for the latest SIMP 5.2.X/4.3.X release (with the addition recent z-version bumps from Forge-readiness patches). SIMP-1595 #comment Fixed `pupmod-simp-dhcp` SIMP-1634 #close Change-Id: Idf3657a6bf17c89a3a00d29eb537f8cd0573690e
Assets 2
-
2016-10-10T21:23:38Z -
2016-10-10T21:23:38Z -