Conflict with acquia_cms profile

I have similar issue after updating this module. Did you find any solution/workaround ? @pobster

Hiya!

I've left it with Acquia (who I don't mind saying, were really useless with it) - but yes, there are three solutions.

1. You can convert your acquia_cms profile to instead be the "minimal" profile.
That way the dependency will come from your own core.extension.yml and not the acquia_cms profile.
2. If you do need/ use purge_processor_lateruntime, edit the acquia_cms_common.install file to:

/**
 * Implements hook_update_N().
 *
 * Uninstall Late runtime processor module.
 */
function acquia_cms_common_update_8007() {
  // Just mark this update as having been "run".  This way it won't be run again.
}

3. If you don't need the purge_processor_lateruntime module installed, edit profiles/contrib/acquia_cms/acquia_cms.info.yml and remove this line:

- purge:purge_processor_lateruntime