Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.After the latest 2.1.0 full upgrade of barracuda and octopus, with o_contrib_up=yes, some of the o_contrib_seven modules do update, but my static platform still symlinks to the version of o_contrib_seven that is 3 months old, and 2 "upgrades" ago. This is after 2 full 24 hour cycles of nightly cron and a few manual verifications of the platform. Is this intended behavior? And if so, do you suggest modifying the symlink so that it links to /data/all/004/o_contrib_seven rather than /data/all/002... for example. Would this best be done from the command line, or will you be putting a fix in stable?
OR, are we supposed to create a new static platform with each octopus upgrade, and the new static platform will automatically symlink to the newest o_contrib_seven, and then using best practices migrate sites from the old static platform to the new static platform? Is this the intended behavior/usage?
| Comment | File | Size | Author |
|---|---|---|---|
| octopus_log.txt | 442 bytes | Anonymous (not verified) | |
| barracuda_log.txt | 840 bytes | Anonymous (not verified) | |
| fast1.octopus.txt | 987 bytes | Anonymous (not verified) | |
| barracuda.txt | 1.74 KB | Anonymous (not verified) |
Comments
Comment #1
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #2
omega8cc CreditAttribution: omega8cc commentedThis is by design. We update only some essential modules there, not all, because it would be against Aegir best practices, since they are part of existing platforms and sites. Only newly created platforms, both built-in and custom will receive complete, latest o_contrib set.