When comparing packages on a platform to assess compatibility for upgrade, Aegir appears to believe that the dev version will always be older than a numbered version in the same major version number.

Yet many packages under heavy development specifically ask users to move onto a dev version (eg Skinr module, required by Acquia Prosper theme) which is actually more advanced than the release.

This was running on a HEAD installation (as of time of ticket submission)

Comments

steveparks’s picture

steveparks commented

An added idea - would it be a good idea to have a checkbox next to packages that are coded red for the admin to manually choose to override Aegir's decision about incompatibility?

anarcat’s picture

anarcat commented

I would love being to force upgrades, it would also work around #604800: platform comparison doesn't handle properly non-global modules.

adrian’s picture

adrian commented

I am considering changing the validation so that it only the schema version is taken into account.

at the moment the back end allows you the migration, but the front end has stricter validation, so i'm going to make the lower version simply be a warning and not an error.

I am also running into this issue with d7 migrations at the moment because the tag for the modules upstream is HEAD.

adrian’s picture

adrian commented
Status: Active » Fixed

i think we fixed this so that version mismatches are just warnings, but schema mismatches are errors.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.