After udating manually to 8.1.8, initiating composer manager, calling drupal-update, I get following error message. This problems remain after i reinstalled manually the old code of 8.1.7 ...

"Your requirements could not be resolved to an installable set of packages.

Problem 1
- Installation request for drupal/drupal No version set (parsed as 1.0.0) -> satisfiable by drupal/drupal[No version set (parsed as 1.0.0)].
- roave/security-advisories dev-master conflicts with drupal/drupal[No version set (parsed as 1.0.0)].
- Installation request for roave/security-advisories dev-master -> satisfiable by roave/security-advisories[dev-master]."

If I try to remove roave/security-advisories I get following message

roave/security-advisories is not required in your composer.json and has not been removed
Problem 1
- The requested package psr/log (locked at 1.0.0, required as dev-master) is satisfiable by psr/log[1.0.0] but these conflict with your requirements or minimum-stability.
Problem 2 [same as Problem 1 above]

Comments

MartinMa created an issue. See original summary.

bojanz’s picture

bojanz CreditAttribution: bojanz at Centarro commented

No clue. Share your composer.json, might help

MartinMa’s picture

MartinMa CreditAttribution: MartinMa as a volunteer commented

Thank you for your answer.

Just found the source oft the problem: it was the "composer security checker" whose composer.json file was not listed in the composer.json of the root folder (destipe composer manager was working).

It seemed to work well for a while.

Just found the module via grep "roave/security-advisories" in the modules folder.

It seems to be impossible to check dependencies on the root with "compose prohibits". So it would be usefull if composer manger - or an extra module - would check this.

By the way: commerguys libraries are not linked to the github directory on composer managers report page (like some other libraries). may be usefull for some people ...

Just another idea to improve information: many modules dont have a proper package-value in info.yml. Were can I start a project that every module is assigned to a propper "package" so that the modules overview page in the admin interface is more helpfull? (i am not a programmer, more a communication worker)

Londova’s picture

Londova CreditAttribution: Londova commented

I met a similar problem, without being able to solve it. While running "composer drupal-update", I got the error:
--------
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package drupal/calendar_datetime could not be found in any version, there may be a typo in the package name.
Problem 2
- Installation request for drupal/currency ^3.1 -> satisfiable by drupal/currency[3.1.0].
- Can only install one of: drupal/currency[8.3.x-dev, 3.1.0].
- Installation request for drupal/currency 8.3.* -> satisfiable by drupal/currency[8.3.x-dev].

Potential causes:
- A typo in the package name
- The package is not available in a stable-enough version according to your minimum-stability setting, see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.
--------

Any idea how to solve this issue?

skessler’s picture

skessler
He/Him
Location Denver
CreditAttribution: skessler commented

I am new to Composer and trying to figure out where the command for the minimum-stability goes. If someone has an example of where the composer.json needs to be in the file system and what needs to be in it I would be very appreciative .

Thanks,
Steve

etdouglas’s picture

etdouglas CreditAttribution: etdouglas commented

I'm having the same issue as Londvoa.

queenielow’s picture

queenielow CreditAttribution: queenielow commented

Hi Guys,

I'm having the similar issue too.. Any solutions? It's my 1st time using composer to install a module.

This is what I get. Any tips would be great.

composer require drupal/mailsystem:4.1
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package drupal/admin_toolbar could not be found in any version, there may be a typo in the package name.
  Problem 2
    - The requested package drupal/config_update could not be found in any version, there may be a typo in the package name.
  Problem 3
    - The requested package drupal/ctools could not be found in any version, there may be a typo in the package name.
  Problem 4
    - The requested package drupal/devel could not be found in any version, there may be a typo in the package name.
  Problem 5
    - The requested package drupal/diff could not be found in any version, there may be a typo in the package name.
  Problem 6
    - The requested package drupal/entity_reference_revisions could not be found in any version, there may be a typo in the package name.
  Problem 7
    - The requested package drupal/field_group could not be found in any version, there may be a typo in the package name.
  Problem 8
    - The requested package drupal/metatag could not be found in any version, there may be a typo in the package name.
  Problem 9
    - The requested package drupal/paragraphs could not be found in any version, there may be a typo in the package name.
  Problem 10
    - The requested package drupal/pathauto could not be found in any version, there may be a typo in the package name.
  Problem 11
    - The requested package drupal/token could not be found in any version, there may be a typo in the package name.
  Problem 12
    - The requested package drupal/twig_field_value could not be found in any version, there may be a typo in the package name.
  Problem 13
    - The requested package drupal/mailsystem could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.

Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems.

Installation failed, reverting ./composer.json to its original content.
markhalliwell’s picture

markhalliwell
Primary language English
CreditAttribution: markhalliwell at Tag1 Consulting commented
Status: Active » Closed (outdated)

Since this module no longer officially supports Drupal 8 (because it has native composer support since 8.1.x+), marking this issue as outdated.

mark_fullmer’s picture

mark_fullmer
he/him
Primary language English
Location Tucson
CreditAttribution: mark_fullmer as a volunteer and at University of Texas at Austin commented

Reading around on similar issues, it seems like running `composer config repositories.drupal composer https://packages.drupal.org/8`, which will add the following configuration to your composer.json file, works:

    "repositories": {
        "drupal": {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
    }

This kind of makes sense, since the error message suggests it is unable to find the Drupal packages. See https://www.drupal.org/project/media/issues/2820691#comment-12454174