Issue 118 in metacello: dirty package after merge skews currentVersion calculation

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium Product-Core Version-1.0-beta.28  
Milestone-1.0

New issue 118 by [hidden email]: dirty package after merge skews  
currentVersion calculation
http://code.google.com/p/metacello/issues/detail?id=118

It looks as though the current version calculation does not take merged  
packages into account .. if a package is dirty then the list of ancestors  
should be scanned in case a later version (that affects currentVersion  
calculation) is present

Updates:
        Labels: -Milestone-1.0 Milestone-1.0-beta.28.4

Comment #1 on issue 118 by [hidden email]: dirty package after merge  
skews currentVersion calculation
http://code.google.com/p/metacello/issues/detail?id=118

(No comment was entered for this change.)

Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.28.3.2

Comment #2 on issue 118 by [hidden email]: dirty package after merge  
skews currentVersion calculation
http://code.google.com/p/metacello/issues/detail?id=118

scanning list of ancestors for package match (whether or not the  
workingCopy is modified)

Name: ConfigurationOfMetacello-dkh.577
Author: dkh
Time: 20 March 2011, 7:52:26 pm
UUID: 911c384d-e54d-409b-8edd-e879bda1e5b7
Ancestors: ConfigurationOfMetacello-dkh.576

available in 1.0-beta.28.3.2 ... or later

Comment #4 on issue 118 by [hidden email]: dirty package after merge  
skews currentVersion calculation
http://code.google.com/p/metacello/issues/detail?id=118

Issue 141 has been merged into this issue.