View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
399 | WADF | Packaging | public | 23 Dec 2011 10:14 | 3 Jan 2012 21:14 |
Reporter | mrosenquist | Assigned To | |||
Priority | high | Severity | major | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | 0.13.5 | ||||
Summary | 399: When use dep-tags undercirtain cirucmstrances the deptags are not respected | ||||
Description | If there are PEAR reference's which also have SVN checkouts and the PEAR version is not on the channel server the PEAR version which in installed will not be the SVN checkout Example: PEAR:pear.premierithosting.com/Application_Admin-1.2.13a SVN:svn+ssh://svn@svn.premierit.com/applications/Admin/branches/release-1.2/src@52469 checkouts/Admin/ Will end up with Application_Admin-1.4.1 being installed. However if we try the following example: PEAR:pear.premierithosting.com/Application_Admin-1.2.12 SVN:svn+ssh://svn@svn.premierit.com/applications/Admin/branches/release-1.2/src@52469 checkouts/Admin/ Will end up with Application_Admin-1.2.12 being installed. In either case we should end with Application_Admin-1.2.13a installed. Recommend using the -n flag when running a pear upgrade -f on a deptag file, and not installing PEAR channel for a SVN checkout | ||||
Tags | No tags attached. | ||||
|
OK, can you clarify what versions are available on the PEAR channel server and what version is in the local checkout? Is the local checkout 1.2.13a, but you have 1.2.12 and 1.4.1 on the channel server? |
|
These are the versions of Admin available: Release-1.4.3 Release-1.4.2 Release-1.4.1 Release-1.4.0 Release-1.3.8 Release-1.3.7 Release-1.3.6 Release-1.3.5 Release-1.3.4 Release-1.3.3 Release-1.3.2 Release-1.3.1 Release-1.3.0 Release-1.2.12 Release-1.2.11 Release-1.2.10 Release-1.2.9 Release-1.2.8 Release-1.2.7 Release-1.2.6 Release-1.2.5 Release-1.2.4 Release-1.2.3 Release-1.2.2 Release-1.2.1 Release-1.2.0 The local checkout is 1.2.13a |
|
I have to say that as this is an error case, the result is undefined. However, like you I would have also expected that in the first case it is still the SVN checkout that gets installed. It must be something to do with the ordering of the installation. My suspicion is that it is also a special case where the latest version existing in PEAR is newer than the SVN checkout. What do the debug logs say (wadf-deploy -v)? |
Date Modified | Username | Field | Change |
---|---|---|---|
23 Dec 2011 10:14 | mrosenquist | New Issue | |
24 Dec 2011 10:59 | timj | Note Added: 427 | |
3 Jan 2012 14:00 | mrosenquist | Note Added: 428 | |
3 Jan 2012 21:14 | timj | Note Added: 429 |