Acquia 6.20 didn't get installed during upgrade (barracuda then Octopus) [#1151028]

I just did an upgrade(barracuda then Octopus) from approx a 20 week old install (2010-12-06 ). It seems to have given me all the distributions except Acquia 6.20

It wan't on the list of platforms and therefore wasn't available when I tried to migrate an Acquia 6.19 based site. It only showed me the current 6.19 version and the 7.0 version.
I then went back and checked my SSH session from the upgrade process and didn't see a prompt asking about Acquia 6.20

Comments

Comment #1

omega8cc CreditAttribution: omega8cc commented 9 May 2011 at 15:16

Status:

Active

» Needs work

This is because the Acquia 6.x directory has no version number in the path, so newer upgrade logic skips the older platform to not overwrite it.

We need to add versions numbers in the path to fix this, as we did for other platforms, because currently we use _USE_CURRENT=YES option by default, see: http://drupalcode.org/project/octopus.git/commit/9fc67eefa9d2e65cfb125ec...

Comment #2

omega8cc CreditAttribution: omega8cc commented 9 May 2011 at 15:30

Component:

Code

» Documentation

No, I was wrong, in fact, for this kind of upgrade (new core version), you should use the previously used _USE_CURRENT=NO option, so it is rather documentation issue.

I will see if we can force it for upgrades from older core versions, automatically.

Comment #3

omega8cc CreditAttribution: omega8cc commented 9 May 2011 at 16:22

This should be fixed in this commit: http://drupalcode.org/project/octopus.git/commit/94fad681e88b9110cd594cd...

It needs testing, so please mark the issue as RTBC when tested and working as expected - it should force creation of all platforms with newer core on upgrade from pre-6.20 installs.