Project

General

Profile

Bug #5147

Resolve issue with modules.txt

Added by David Welker about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
general
Target version:
Start date:
08/12/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5147

Description

Automatic suite resolution has some issues with regard to patching. For example, if reporting-2.1.0 contains a self-reference to reporting-2.1.^, then when reporting-2.1 is patched, this will resolve to:

reporting-2.1.0
reporting-2.1.1

This is clearly incorrect, especially as the patch will be overridden by the older version and both modules are clearly unnecessary.

This is a particularly tricky issue, as fixing this bug will affect how modules.txt is interpreted and may cause some backwards compatibility issues. I will be investigating solutions to this that are maximally backwards compatible.


Related issues

Blocked by Kepler - Bug #5143: not getting prompted to upgrade to available patched version in test areaResolved08/11/2010

Blocked by Kepler - Bug #5099: Import Dependent Modules for KAR doesn't workResolved07/21/2010

History

#1 Updated by David Welker about 9 years ago

I found a way to solve this problem without affecting backwards compatibility. There is new file, called current-suite.txt which will store the current suite. In this way, a ^ symbol can be included for the suite itself if it is patched.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5147

Also available in: Atom PDF