doctrine/archived-orm
1
0
Fork 0
mirror of https://github.com/doctrine/orm.git synced 2026-03-23 22:42:18 +01:00
Code Issues 5.3k Packages Projects Releases 100 Wiki Activity

No matching package found -> instantiator ~1.0.1 #5628

New Issue
Closed
opened 2026-01-22 15:13:13 +01:00 by admin · 12 comments
admin commented 2026-01-22 15:13:13 +01:00
Owner
Copy Link

Originally created by @tymon82 on GitHub (Aug 4, 2017).

  • doctrine/orm v2.5.6 requires doctrine/instantiator ~1.0.1 -> no match
    ing package found.
Originally created by @tymon82 on GitHub (Aug 4, 2017). - doctrine/orm v2.5.6 requires doctrine/instantiator ~1.0.1 -> no match ing package found.
admin closed this issue 2026-01-22 15:13:14 +01:00
admin commented 2026-01-22 15:13:14 +01:00
Author
Owner
Copy Link

@alcaeus commented on GitHub (Aug 4, 2017):

You only posted part of the error message. Please post the entire error message from composer as well as your platform information (PHP version)

@alcaeus commented on GitHub (Aug 4, 2017): You only posted part of the error message. Please post the entire error message from composer as well as your platform information (PHP version)
admin commented 2026-01-22 15:13:15 +01:00
Author
Owner
Copy Link

@tymon82 commented on GitHub (Aug 4, 2017):

[Composer\DependencyResolver\SolverProblemsException]
Problem 1
- Installation request for doctrine/orm v2.5.* -> satisfiable by doctri
ne/orm[v2.5.6].
- doctrine/orm v2.5.6 requires doctrine/instantiator ~1.0.1 -> no match
ing package found.
Problem 2
- doctrine/orm v2.5.6 requires doctrine/instantiator ~1.0.1 -> no match
ing package found.
- fess/admin-bundle dev-master requires doctrine/orm v2.5.* -> satisfia
ble by doctrine/orm[v2.5.6].
- Installation request for fess/admin-bundle dev-master -> satisfiable
by fess/admin-bundle[dev-master].
Potential causes:

PHP 7.1.7

All subpackages if they need orm got 2.5.* as require

@tymon82 commented on GitHub (Aug 4, 2017): [Composer\DependencyResolver\SolverProblemsException] Problem 1 - Installation request for doctrine/orm v2.5.* -> satisfiable by doctri ne/orm[v2.5.6]. - doctrine/orm v2.5.6 requires doctrine/instantiator ~1.0.1 -> no match ing package found. Problem 2 - doctrine/orm v2.5.6 requires doctrine/instantiator ~1.0.1 -> no match ing package found. - fess/admin-bundle dev-master requires doctrine/orm v2.5.* -> satisfia ble by doctrine/orm[v2.5.6]. - Installation request for fess/admin-bundle dev-master -> satisfiable by fess/admin-bundle[dev-master]. Potential causes: - A typo in the package name - The package is not available in a stable-enough version according to you r minimum-stability setting see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for mor e details. Read <https://getcomposer.org/doc/articles/troubleshooting.md> for further common problems. PHP 7.1.7 All subpackages if they need orm got 2.5.* as require
admin commented 2026-01-22 15:13:15 +01:00
Author
Owner
Copy Link

@alcaeus commented on GitHub (Aug 4, 2017):

Could you please run composer why-not doctrine/instantiator 1.0.1 and post the output here?

@alcaeus commented on GitHub (Aug 4, 2017): Could you please run `composer why-not doctrine/instantiator 1.0.1` and post the output here?
admin commented 2026-01-22 15:13:15 +01:00
Author
Owner
Copy Link

@tymon82 commented on GitHub (Aug 4, 2017):

$ composer why-not doctrine/instantiator 1.0.1
jms/serializer dev-master requires doctrine/instantiator (^1.0.3)
phpspec/prophecy dev-master requires doctrine/instantiator (^1.0.2)
phpunit/phpunit-mock-objects 3.4.x-dev requires doctrine/instantiator (^1.0.2)
doctrine/instantiator 1.0.1 requires php (~5.3 but 7.1.7 is installed)

@tymon82 commented on GitHub (Aug 4, 2017): $ composer why-not doctrine/instantiator 1.0.1 jms/serializer dev-master requires doctrine/instantiator (^1.0.3) phpspec/prophecy dev-master requires doctrine/instantiator (^1.0.2) phpunit/phpunit-mock-objects 3.4.x-dev requires doctrine/instantiator (^1.0.2) doctrine/instantiator 1.0.1 requires php (~5.3 but 7.1.7 is installed)
admin commented 2026-01-22 15:13:15 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (Aug 4, 2017):

Are you using a composer.lock? 1.0.1 is quite old.

On 4 Aug 2017 1:45 PM, "tymon82" notifications@github.com wrote:

$ composer why-not doctrine/instantiator 1.0.1
jms/serializer dev-master requires doctrine/instantiator (^1.0.3)
phpspec/prophecy dev-master requires doctrine/instantiator (^1.0.2)
phpunit/phpunit-mock-objects 3.4.x-dev requires doctrine/instantiator
(^1.0.2)
doctrine/instantiator 1.0.1 requires php (~5.3 but 7.1.7 is installed)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/issues/6604#issuecomment-320228788,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakFHy_C_m9qjHB35e9PYzs8PUli1lks5sUwRTgaJpZM4OtlD7
.

@Ocramius commented on GitHub (Aug 4, 2017): Are you using a composer.lock? 1.0.1 is quite old. On 4 Aug 2017 1:45 PM, "tymon82" <notifications@github.com> wrote: > $ composer why-not doctrine/instantiator 1.0.1 > jms/serializer dev-master requires doctrine/instantiator (^1.0.3) > phpspec/prophecy dev-master requires doctrine/instantiator (^1.0.2) > phpunit/phpunit-mock-objects 3.4.x-dev requires doctrine/instantiator > (^1.0.2) > doctrine/instantiator 1.0.1 requires php (~5.3 but 7.1.7 is installed) > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/doctrine/doctrine2/issues/6604#issuecomment-320228788>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAJakFHy_C_m9qjHB35e9PYzs8PUli1lks5sUwRTgaJpZM4OtlD7> > . >
admin commented 2026-01-22 15:13:16 +01:00
Author
Owner
Copy Link

@tymon82 commented on GitHub (Aug 4, 2017):

In doctrine composer.json i got:

"require": {
    "php": ">=5.4",
    "ext-pdo": "*",
    "doctrine/collections": "~1.2",
    "doctrine/dbal": ">=2.5-dev,<2.6-dev",
    "doctrine/instantiator": "~1.0.1",
    "doctrine/common": ">=2.5-dev,<2.8-dev",
    "doctrine/cache": "~1.4",
    "symfony/console": "~2.5|~3.0"
},
@tymon82 commented on GitHub (Aug 4, 2017): In doctrine composer.json i got: "require": { "php": ">=5.4", "ext-pdo": "*", "doctrine/collections": "~1.2", "doctrine/dbal": ">=2.5-dev,<2.6-dev", "doctrine/instantiator": "~1.0.1", "doctrine/common": ">=2.5-dev,<2.8-dev", "doctrine/cache": "~1.4", "symfony/console": "~2.5|~3.0" },
admin commented 2026-01-22 15:13:16 +01:00
Author
Owner
Copy Link

@alcaeus commented on GitHub (Aug 4, 2017):

@tymon82 You should be able to run composer update and get a fresh batch of dependencies. Looks like you've got a lock file that depends on 1.0.1, which can't be installed on 7.1 (~5.3 is < 6)

@alcaeus commented on GitHub (Aug 4, 2017): @tymon82 You should be able to run `composer update` and get a fresh batch of dependencies. Looks like you've got a lock file that depends on 1.0.1, which can't be installed on 7.1 (`~5.3` is `< 6`)
admin commented 2026-01-22 15:13:17 +01:00
Author
Owner
Copy Link

@tymon82 commented on GitHub (Aug 4, 2017):

@Ocramius this version is in json of doctrine: https://github.com/doctrine/doctrine2/blob/2.5/composer.json

So if its so old does need to be upgraded there?

@tymon82 commented on GitHub (Aug 4, 2017): @Ocramius this version is in json of doctrine: https://github.com/doctrine/doctrine2/blob/2.5/composer.json So if its so old does need to be upgraded there?
admin commented 2026-01-22 15:13:17 +01:00
Author
Owner
Copy Link

@tymon82 commented on GitHub (Aug 4, 2017):

@alcaeus got same error even when deleted .lock file

@tymon82 commented on GitHub (Aug 4, 2017): @alcaeus got same error even when deleted .lock file
admin commented 2026-01-22 15:13:17 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (Aug 4, 2017):

That version is basically >=1.0.1,<1.1 in ORM 2.5.

On 4 Aug 2017 2:06 PM, "tymon82" notifications@github.com wrote:

@alcaeus https://github.com/alcaeus got same error even when deleted
.lock file

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/issues/6604#issuecomment-320232446,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakL1dNc-wJIU7Ws8CgSb0czoV0gfQks5sUwlVgaJpZM4OtlD7
.

@Ocramius commented on GitHub (Aug 4, 2017): That version is basically >=1.0.1,<1.1 in ORM 2.5. On 4 Aug 2017 2:06 PM, "tymon82" <notifications@github.com> wrote: @alcaeus <https://github.com/alcaeus> got same error even when deleted .lock file — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/doctrine/doctrine2/issues/6604#issuecomment-320232446>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJakL1dNc-wJIU7Ws8CgSb0czoV0gfQks5sUwlVgaJpZM4OtlD7> .
admin commented 2026-01-22 15:13:17 +01:00
Author
Owner
Copy Link

@Ocramius commented on GitHub (Aug 4, 2017):

@tymon82 what is the resolution here?

@Ocramius commented on GitHub (Aug 4, 2017): @tymon82 what is the resolution here?
admin commented 2026-01-22 15:13:18 +01:00
Author
Owner
Copy Link

@tymon82 commented on GitHub (Aug 5, 2017):

Cause of lack of time change in composer to dev-master of doctrine.

@tymon82 commented on GitHub (Aug 5, 2017): Cause of lack of time change in composer to dev-master of doctrine.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BC Break
Bug
Can't Fix
Deprecation
Documentation
DQL
Duplicate
Failing Test
Hacktoberfest
Improvement
Improvement
Incomplete
Invalid
Missing Tests
New Feature
PR Created
pull-request
Mirrored from GitHub Pull Request
 Question
Regression
Status: Waiting feedback
Waiting feedback
WIP
Won't Fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#5628
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?