Actions
Bug #10462
closed
package verify version (sometimes?) does not check version of packages
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
The package_check_version generic methods does not always checks the precise version of the package, but sometimes only its presence.
This may possibly be fixed by using specific package bodies with a specified version in the package name.
Updated by Alexis Mousset about 7 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
Updated by François ARMAND about 7 years ago
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Updated by Alexis Mousset almost 7 years ago
- Priority set to 36
Only happens with old package technique/method.
Updated by Alexis Mousset almost 7 years ago
- Category changed from Generic methods - Package Management to 83
- Priority changed from 36 to 35
Updated by Alexis Mousset almost 7 years ago
- Is duplicate of Bug #9547: package_install should use another package body when using a specific package version added
Updated by Alexis Mousset almost 7 years ago
- Status changed from New to Rejected
- Priority changed from 35 to 50
Fixed by #9547.
Updated by Alexis Mousset almost 6 years ago
- Category changed from 83 to Generic methods - Package Management
- Priority changed from 50 to 43
Updated by Alexis Mousset almost 2 years ago
- Target version changed from 0.x to ncf-0.x
- Priority changed from 43 to 0
Updated by Alexis Mousset almost 2 years ago
- Project changed from 41 to Rudder
- Category changed from Generic methods - Package Management to Generic methods
Actions