Composer dependency mismatch on 0.6.2

[drzax]

0.6.2 can't be installed on SS 3.0.x using Composer as it requires silverstripe/widgets dev-master which in turn requires silverstripe/cms >= 3.1

[cbarberis]

hey @kmayo-ss should we close this one too?

cheers
Carlos

[kmayo-ss]

Still seems to be a problem tried a composer install on the following composer file

{
        "name": "silverstripe/installer",
        "description": "The SilverStripe Framework Installer",
        "require": {
                "php": ">=5.3.2",
                "silverstripe/cms": "3.0.*",
                "silverstripe/framework": "3.0.*",
                "silverstripe-themes/simple": "*",
                "silverstripe/blog": "0.6.2"
        },
        "config": {
                "process-timeout": 600
        },
        "minimum-stability": "dev"
}

and received the following error

Kirks-MacBook-Pro:issue84 kmayo$ composer install
Loading composer repositories with package information
Installing dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- silverstripe/blog 0.6.2 requires silverstripe/widgets dev-master -> satisfiable by silverstripe/widgets[dev-master].
- silverstripe/cms 3.2.x-dev requires silverstripe/framework 3.2.x-dev -> satisfiable by silverstripe/framework[3.2.x-dev].
- don't install silverstripe/framework 3.2.x-dev|install silverstripe/framework dev-master
- Conclusion: don't install silverstripe/framework dev-master
- Conclusion: don't install silverstripe/cms 3.0.x-dev
- Conclusion: don't install silverstripe/cms 3.1.x-dev
- silverstripe/cms 3.1.0-beta1 requires silverstripe/framework 3.1.x-dev -> satisfiable by silverstripe/framework[3.1.x-dev].
- Conclusion: don't install silverstripe/framework 3.1.x-dev
- Conclusion: don't install silverstripe/cms 3.1.2
- Conclusion: don't install silverstripe/cms 3.0.8
- Conclusion: don't install silverstripe/cms 3.1.2-rc1
- Conclusion: don't install silverstripe/cms 3.1.1
- Conclusion: don't install silverstripe/cms 3.0.7
- Conclusion: don't install silverstripe/cms 3.1.0
- Conclusion: don't install silverstripe/cms 3.1.0-rc3
- Conclusion: don't install silverstripe/cms 3.0.7-rc1
- Conclusion: don't install silverstripe/cms 3.1.0-rc2
- Conclusion: don't install silverstripe/cms 3.1.0-rc1
- Conclusion: don't install silverstripe/cms 3.0.6
- Installation request for silverstripe/blog 0.6.2 -> satisfiable by silverstripe/blog[0.6.2].
- Installation request for silverstripe/framework 3.0.* -> satisfiable by silverstripe/framework[3.0.2.1, 3.0.3, 3.0.3-rc1, 3.0.3-rc2, 3.0.4, 3.0.5, 3.0.6, 3.0.6-rc1, 3.0.6-rc2, 3.0.7, 3.0.7-rc1, 3.0.8, 3.0.x-dev].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.2.1].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.3].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.3-rc1].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.3-rc2].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.4].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.5].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.6-rc1].
- Can only install one of: silverstripe/cms[3.1.0-beta2, 3.0.6-rc2].
- silverstripe/widgets dev-master requires silverstripe/cms ~3.1 -> satisfiable by silverstripe/cms[3.1.0, 3.1.0-beta1, 3.1.0-beta2, 3.1.0-beta3, 3.1.0-rc1, 3.1.0-rc2, 3.1.0-rc3, 3.1.1, 3.1.2, 3.1.2-rc1, 3.1.x-dev, 3.2.x-dev].
- Conclusion: don't install silverstripe/cms 3.1.0-beta3
- Installation request for silverstripe/cms 3.0.* -> satisfiable by silverstripe/cms[3.0.2.1, 3.0.3, 3.0.3-rc1, 3.0.3-rc2, 3.0.4, 3.0.5, 3.0.6, 3.0.6-rc1, 3.0.6-rc2, 3.0.7, 3.0.7-rc1, 3.0.8, 3.0.x-dev].

[cbarberis]

Bit late to change the tag.
What are the options here? create a new tag with the right requirements in the composer file?

[kmayo-ss]

On the original pull request made the following comment for it to be tagged as 0.6.3
The original pull request may be quite stale now but if it can still be merged in creating a new tag would be good

#99
I would like this pull request to be created as a new tag 0.6.3 this is to resolve the following issues

[tractorcow]

I've commented on #99 - Simple solution should be to just tag the 0.6-dev branch as 0.6.3 since it has the correct dependencies (3.0.* not 3.*). Widgets is a suggestion, not a requirement, and the correct version (0.1) is listed instead of dev-master.

[assertchris]

Widgets is no longer a dependency.