The composer.json includes some dependencies, but the versions specified don't match the versions available in the repos that are included in the composer.json file.

The dev-branchname convention only works with repos of type vcs, where this should work with packagist.drupal-composer.org.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikey_p created an issue. See original summary.

Berdir’s picture

Status: Needs review » Needs work

Thanks. I've just released token alpha2, ctools already had a new release, which means we no longer require their dev versions, while changing this can you update the patch to remove that?

mikey_p’s picture

I think this is what you're looking for, although token token 8.x-1.0-alpha2 doesn't seem to be on Drupal Packagist yet.

Berdir’s picture

doesn't that mean *only* exactly those releases? Can't we say at least that or anything that's newer?

Berdir’s picture

webflo: berdir: i think ~8.1.0-alpha2 should work. it means =>8.1.0-alpha2, <8.2.0

mikey_p’s picture

I think in composer lingo that would be anything up to 9.0.0 wouldn't it?

mikey_p’s picture

Berdir’s picture

Status: Needs review » Fixed

Thanks.

  • Berdir committed 92f0607 on 8.x-1.x authored by mikey_p
    Issue #2653880 by mikey_p: Fix composer dependencies
    

The last submitted patch, 3: 2653880-pathauto_fix_composer_dependencies-3.patch, failed testing.

Status: Fixed » Needs work

The last submitted patch, 7: 2653880-pathauto_fix_composer_dependencies-7.patch, failed testing.

The last submitted patch, pathauto-fix-composer-dependencies.patch, failed testing.

Berdir’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

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