Php-ffmpeg: Symfony 4 composer dependency problem

[GitDaimos]

| Q | A
| -------------- | ---
| Bug? | yes
| New Feature? | no
| Version Used | 0.11.0

Actual Behavior

composer require php-ffmpeg/php-ffmpeg
Using version ^0.11.0 for php-ffmpeg/php-ffmpeg
./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
    - Installation request for php-ffmpeg/php-ffmpeg ^0.11.0 -> satisfiable by php-ffmpeg/php-ffmpeg[v0.11.0].
    - Conclusion: remove symfony/filesystem v4.0.3
    - Conclusion: don't install symfony/filesystem v4.0.3
    - php-ffmpeg/php-ffmpeg v0.11.0 requires neutron/temporary-filesystem ^2.1.1 -> satisfiable by neutron/temporary-filesystem[2.1.1, 2.2.0].
    - neutron/temporary-filesystem 2.1.1 requires symfony/filesystem ~2.0 -> satisfiable by symfony/filesystem[v2.1.0, v2.1.1, v2.1.10, v2.1.11, v2.1.12, v2.1.13, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, v2.1.8, v2.1.9, v2.2.0, v2.2.1, v2.2.10, v2.2.11, v2.2.2, v2.2.3, v2.2.4, v2.2.5, v2.2.6, v2.2.7, v2.2.8, v2.2.9, v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.3.38, v2.3.39, v2.3.4, v2.3.40, v2.3.41, v2.3.42, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6, v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9].
    - neutron/temporary-filesystem 2.2.0 requires symfony/filesystem ^2.3 || ^3.0 -> satisfiable by symfony/filesystem[v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.36, v2.3.37, v2.3.38, v2.3.39, v2.3.4, v2.3.40, v2.3.41, v2.3.42, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6, v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.13, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6.9, v2.7.0, v2.7.1, v2.7.10, v2.7.11, v2.7.12, v2.7.13, v2.7.14, v2.7.15, v2.7.16, v2.7.17, v2.7.18, v2.7.19, v2.7.2, v2.7.20, v2.7.21, v2.7.22, v2.7.23, v2.7.24, v2.7.25, v2.7.26, v2.7.27, v2.7.28, v2.7.29, v2.7.3, v2.7.30, v2.7.31, v2.7.32, v2.7.33, v2.7.34, v2.7.35, v2.7.36, v2.7.37, v2.7.38, v2.7.39, v2.7.4, v2.7.40, v2.7.5, v2.7.6, v2.7.7, v2.7.8, v2.7.9, v2.8.0, v2.8.1, v2.8.10, v2.8.11, v2.8.12, v2.8.13, v2.8.14, v2.8.15, v2.8.16, v2.8.17, v2.8.18, v2.8.19, v2.8.2, v2.8.20, v2.8.21, v2.8.22, v2.8.23, v2.8.24, v2.8.25, v2.8.26, v2.8.27, v2.8.28, v2.8.29, v2.8.3, v2.8.30, v2.8.31, v2.8.32, v2.8.33, v2.8.4, v2.8.5, v2.8.6, v2.8.7, v2.8.8, v2.8.9, v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.0.8, v3.0.9, v3.1.0, v3.1.1, v3.1.10, v3.1.2, v3.1.3, v3.1.4, v3.1.5, v3.1.6, v3.1.7, v3.1.8, v3.1.9, v3.2.0, v3.2.1, v3.2.10, v3.2.11, v3.2.12, v3.2.13, v3.2.14, v3.2.2, v3.2.3, v3.2.4, v3.2.5, v3.2.6, v3.2.7, v3.2.8, v3.2.9, v3.3.0, v3.3.1, v3.3.10, v3.3.11, v3.3.12, v3.3.13, v3.3.14, v3.3.15, v3.3.2, v3.3.3, v3.3.4, v3.3.5, v3.3.6, v3.3.7, v3.3.8, v3.3.9, v3.4.0, v3.4.1, v3.4.2, v3.4.3].
    - Can only install one of: symfony/filesystem[v3.4.0, v4.0.3].
    - Can only install one of: symfony/filesystem[v3.4.1, v4.0.3].
   # All versions listed here, to:
    - Can only install one of: symfony/filesystem[v3.3.9, v4.0.3].
    - Installation request for symfony/filesystem (locked at v4.0.3) -> satisfiable by symfony/filesystem[v4.0.3].


Installation failed, reverting ./composer.json to its original content.

Steps to Reproduce

1. Install symfony 4
2. Add composer dependency for PHP-FFMpeg

Any idea to resolve this problem?

[jens1o]

Uh. This is dilemma. Looks like we need to write our own temporary filesystem wrapper since neutron/temporary-filesystem is not maintained anymore.

I can't help you with this, because we may not upgrade any third party dependencies to avoid breaking changes.

We will resolve this with version 1.0.

[GitDaimos]

There is already fix made for this issue on neutron/temporary-filesystem
Maybe author will merge it. If not, we can create new fork based on old filesystem

https://github.com/romainneutron/Temporary-Filesystem/pull/10

[jens1o]

If not, we can create new fork based on old filesystem

That's the plan.

[jens1o]

I created a fork, and added compatibility with that. I referenced composer to use my fork as of now, till the branch has been merged.

[MonsieurLanza]

Hello,

Your fork's branch should not be named "dev-jens1o-update-deps" but just "jens1o-update-deps", "dev-" prefix is removed by composer.

(I need this fix too ^^)

[jens1o]

ah, thanks for the heads up. Fixed.

[cb8]

the problems with neutron/temporary-filesystem have been resolved in version 2.3.0. however, alchemy/binary-driver still requires symfony/process:^2.0|^3.0. i submitted a PR in alchemy-fr/BinaryDriver#18. @jens1o feel free to include it in a fork in case you dont want to way until it gets merged (hopefully).

[jens1o]

I will wait, since 1.x is somewhat scheduled to be released this summer(I plan to release it on my birthday, July 12th).

[uschmann]

HI,

i just started a fresh laravel 5.6 project and would like to use php-ffmpeg in it.
Is there a workaround for this problem until version 1.0 is released?

Any help is really appreciated.

Kind regards

André

[jens1o]

Is there a workaround for this problem until version 1.0 is released?

Rely on the v1.x branch, which is not stable.

[AliN11]

Rely on the v1.x branch, which is not stable

How I install that ?
I still get same error with:
composer require php-ffmpeg/php-ffmpeg:v1.x

[jens1o]

That shouldn't be possible?

[AliN11]

Anyway to use in Laravel ?

[jens1o]

use laravel 5.3 ;)

I'll look into this later today.

[xorik]

To install this package with symfony 4:
1) Add to your composer.json:

    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/PHP-FFMpeg/BinaryDriver.git"
        }
    ],

2) run composer require php-ffmpeg/binary-driver=dev-master
3) run composer require php-ffmpeg/php-ffmpeg

[Youngkingoo6]

I had done as @xorik said.And I succed download the php-ffmpeg ,But I got another problem.
as long as use getenv function ,the application shut down and return 500.And it is not usefull even regist the shut down funciton.

[jens1o]

But I got another problem as long as use getenv functios

Sorry? Could you open a new issue with detailed information?

[jens1o]

see https://github.com/PHP-FFMpeg/PHP-FFMpeg/pull/559#issuecomment-423138352

[jens1o]

New release is out. :)

[nikkii94]

I can't get it to work, I got this error everytime I try to install this package with Symfony 4

Problem 1
    - Installation request for php-ffmpeg/php-ffmpeg ^0.13.0 -> satisfiable by php-ffmpeg/php-ffmpeg[v0.13].
    - php-ffmpeg/php-ffmpeg v0.13 requires evenement/evenement ^2.0 || ^1.0 -> satisfiable by evenement/evenement[1.0.x-dev, 2.0.x-dev, v1.0.0, v1.1.0, v2.0.0, v2.1.0] b
ut these conflict with your requirements or minimum-stability.

I tried everything mentioned above, but with no luck :/
Can you please help? :)

[jens1o]

Please open a new issue, because it is (probably) unrelated to this. Please include your full composer.json there.

[BenasPaulikas]

No matter what I'm doing I'm getting

  Problem 1
    - Installation request for php-ffmpeg/php-ffmpeg ^0.13.0 -> satisfiable by php-ffmpeg/php-ffmpeg[v0.13].
    - Conclusion: remove evenement/evenement v3.0.1
    - Conclusion: don't install evenement/evenement v3.0.1
    - php-ffmpeg/php-ffmpeg v0.13 requires evenement/evenement ^2.0 || ^1.0 -> satisfiable by evenement/evenement[v1
.0.0, v1.1.0, v2.0.0, v2.1.0].
    - Can only install one of: evenement/evenement[v1.0.0, v3.0.1].
    - Can only install one of: evenement/evenement[v1.1.0, v3.0.1].
    - Can only install one of: evenement/evenement[v2.0.0, v3.0.1].
    - Can only install one of: evenement/evenement[v2.1.0, v3.0.1].
    - Installation request for evenement/evenement (locked at v3.0.1) -> satisfiable by evenement/evenement[v3.0.1].

Any ideas for this ?

[BenasPaulikas]

composer show --tree Shows that evenement is being used by other composer plugin. Ignore my question.