Unable to use latest version from composer

Issue #65 closed
Robert Koszewski created an issue

Seems that the latest tags are missing from composer.

This are the tags that are supported right now:

The requested package boressoft/ident_switch ~4.2 exists as boressoft/ident_switch[0.5, 0.6, 0.7, 0.8, 1.0, 1.1, 1.2, 2.0, 3.0, 3.1, 3.2, 3.3, 3.3.1, 3.4, 4.0, 4.0.1, dev-master]

Where dev-master seems to be outdated as well..

Any way to fix this?

Comments (3)

  1. Boris Gulay repo owner

    Hi

    Hi guys.

    Short answer: you just have to update your composer. Just run ./composer selfupdate before updating ident_switch.

    Detailed answer:

    Some time ago bitbucked has turned off their old API that composer was using to get repository data. That’s why I had issue #52: plugins.roundcube.net is using composer too. After updating to latest version everything will work fine.

    Issue with port in CHECK was fixed in version 4.1 of my plugin. Your composer can see versions up to 4.0.1 only. Thet`s why you still have the problem.

    And message from composer “The requested package … exists as…” is also related to old composer version.

    The solution is simple: just run ./composer selfupdate.

    you just have to update your composer. Just run ./composer selfupdate before updating ident_switch.

    Detailed answer:

    Some time ago bitbucked has turned off their old API that composer was using to get repository data. That’s why I had issue #52: plugins.roundcube.net is using composer too. After updating to latest version everything will work fine.

    Issue with port in CHECK was fixed in version 4.1 of my plugin. Your composer can see versions up to 4.0.1 only. Thet`s why you still have the problem.

    And message from composer “The requested package … exists as…” is also related to old composer version.

    The solution is simple: just run ./composer selfupdate.

  2. Boris Gulay repo owner

    You just have to update your composer. Just run ./composer selfupdate before updating ident_switch.

  3. Log in to comment