ProfessionalWiki / ProfessionalWiki/Maps

Issue updating to v10 with composer

Open
#745 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
JavaScript
Stars
78
Forks
65
Avg merge
9h 17m
Merged PRs (30d)
6

Description

I ran into the same issue described here by a reddit user: https://old.reddit.com/r/mediawiki/comments/1170jrz/maps_100_will_not_install_what_to_do/

With the following composer.local.json:

{
    "require": {
        "mediawiki/maps": "^10.0",
        "mediawiki/semantic-media-wiki": "^4.0"
    },

    "extra": {
        "merge-plugin": {
                        "include": [
                                "extensions/*/composer.json",
                                "skins/*/composer.json"
                        ]
        }
    }
}

I got the following error after running composer update --no-dev:

  Problem 1
    - mediawiki/core is present at version 1.0.0+no-version-set and cannot be modified by Composer
    - mediawiki/maps[10.0.0] cannot be installed as that would require removing mediawiki/core[1.0.0+no-version-set]. They both replace mediawiki/semantic-maps and thus cannot coexist.
    - Root composer.json requires mediawiki/maps ^10.0 -> satisfiable by mediawiki/maps[10.0.0].

I was able to resolve the issue by temporarily removing composer.local.json, running composer update --no-dev and then restoring composer.local.json and updating a second time, but I don't understand what caused the problem in the first place.

The mediawiki/core package doesn't seem to make any mention of mediawiki/semantic-maps, so I'm not sure where the conflict comes from.

I would appreciate any help understanding the what causes the problem so I don't have it in the future.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with composer.local.json and the root composer.json, then reproduce the failure with composer update --no-dev using the shown requirements. Trace why mediawiki/maps, mediawiki/semantic-maps, and mediawiki/core are considered conflicting; done means documenting the cause and a reliable update procedure.

Written by the indexing model from the issue text.

Assessment

Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.