1,574
edits
Changes
Jump to navigation
Jump to search
Line 210:
Line 210: − + + + + +
→DEALING WITH PACKAGE DEPENDENCIES.
*e-smith-base 5.0.0-16 cannot be released as it has a change that has not been verified.
*e-smith-base 5.0.0-16 cannot be released as it has a change that has not been verified.
*It would be possible to release e-smith-base 5.0.0-14
**It would be possible to release e-smith-base 5.0.0-14
*e-smith-pop3 2.0.0-2 cannot be released as e-smith-base 5.0.0-16 which contains part of the fix for bug 6262 is not being released.
*e-smith-pop3 2.0.0-2 cannot be released as e-smith-base 5.0.0-16 which contains part of the fix for bug 6262 is not being released.
*e-smith-apache 2.0.0-7 cannot be released as part of the fix for Bug 4633 is in e-smith-pop3 2.0.0-1 which is not being released.
*e-smith-apache 2.0.0-7 cannot be released as part of the fix for Bug 4633 is in e-smith-pop3 2.0.0-1 which is not being released.
If you carefully check the code changes it may be possible to release e-smith-pop3 & e-smith-apache in the example above, but safest not to.
If you carefully check the code changes it may be possible to release e-smith-pop3 & e-smith-apache in the example above, but safest not to.
To be clarified:
- If deps are not resolved, will Shad's script block cp for unresolved packages dependencies?
[Answer from Ian: not sure for updates. But normally it is not hard dependencies being an issue. ]