dirty package after merge skews currentVersion calculation

krfkeith / metacello

Automatically exported from code.google.com/p/metacello

0 stars 0 forks source link

dirty package after merge skews currentVersion calculation #118

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

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

Original issue reported on code.google.com by henrichs...@gmail.com on 5 Mar 2011 at 8:29

GoogleCodeExporter commented 9 years ago

Original comment by henrichs...@gmail.com on 18 Mar 2011 at 6:11

Added labels: Milestone-1.0-beta.28.4
Removed labels: Milestone-1.0

GoogleCodeExporter commented 9 years ago

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

Original comment by henrichs...@gmail.com on 21 Mar 2011 at 2:57

Changed state: Fixed
Added labels: Fixed-1.0-beta.28.3.2

GoogleCodeExporter commented 9 years ago

bulk verify

Original comment by henrichs...@gmail.com on 18 Apr 2011 at 5:32

Changed state: Verified

GoogleCodeExporter commented 9 years ago

Issue 141 has been merged into this issue.

Original comment by henrichs...@gmail.com on 3 Jun 2011 at 9:00