View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 328 | WADF | Core | public | 22 Jan 2010 12:00 | 24 Nov 2011 21:46 |
| Reporter | samadams83 | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Product Version | 0.13.2 | ||||
| Summary | 328: Package dependency version: Higher-version files persisting after downgrade | ||||
| Description | When a package file specifies a specific max version of a dependancy (e.g. 0.9.0) but other dependencies have no max, wadf will download and install the latest version (e.g. 1.2.0), and then install the older version over it afterwards. The problem is that the files from the 1.2.0 version that haven't been overwritten by the downgrade (i.e. files that don't exist in the later version) will not be removed. This can cause the application to behave incorrectly as it has files from mixed versions. | ||||
| Tags | No tags attached. | ||||
|
|
I think you mean "files from the 1.2.0 version that haven't been overwritten by the downgrade (i.e. files that don't exist in the *earlier* version)". If this is the case, it's a fair point but it will be a bug in PEAR. |
|
|
This *might* be fixed with the upstream PEAR bug fix http://pear.php.net/bugs/bug.php?id=17350 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 22 Jan 2010 12:00 | samadams83 | New Issue | |
| 22 Jan 2010 12:10 | timj | Note Added: 334 | |
| 22 Jan 2010 12:11 | timj | Note Edited: 334 | |
| 24 Nov 2011 21:46 | timj | Note Added: 424 |
