The lock file is not up to date with the latest changes in composer.json










1















I'm trying to clone a github repository and issue a composer install on it. But I am getting this:




Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.




Your requirements could not be resolved to an installable set of packages. 
Problem 1
- Conclusion: remove symfony/polyfill-intl-icu v1.9.0
- Installation request for symfony/polyfill-intl-icu v1.9.0 -> satisfiable by symfony/polyfill-intl-icu[v1.9.0].
- Conclusion: remove symfony/process v3.4.15
- symfony/polyfill-intl-icu v1.9.0 requires symfony/intl ~2.3|~3.0|~4.0 -> satisfiable by symfony/symfony[v4.0.0].
- don't install symfony/process v3.4.15|remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|don't install symfony/process v3.4.15
- Installation request for symfony/process v3.4.15 -> satisfiable by symfony/process[v3.4.15].


When running composer update



Problem 1
- Conclusion: don't install symfony/symfony v4.1.7
- Conclusion: don't install symfony/symfony v4.1.6
- Conclusion: don't install symfony/symfony v4.1.5
- Conclusion: don't install symfony/symfony v4.1.4
- Conclusion: don't install symfony/symfony v4.1.3
- Conclusion: don't install symfony/symfony v4.1.2
- Conclusion: don't install symfony/symfony v4.1.1
- Conclusion: don't install symfony/symfony v4.1.0
- Conclusion: don't install symfony/symfony v4.0.14
- Conclusion: don't install symfony/symfony v4.0.13
- Conclusion: don't install symfony/symfony v4.0.12
- Conclusion: don't install symfony/symfony v4.0.11
- Conclusion: don't install symfony/symfony v4.0.10
- Conclusion: don't install symfony/symfony v4.0.9
- Conclusion: don't install symfony/symfony v4.0.8
- Conclusion: don't install symfony/symfony v4.0.7
- Conclusion: don't install symfony/symfony v4.0.6
- Conclusion: don't install symfony/symfony v4.0.5
- Conclusion: don't install symfony/symfony v4.0.4
- Conclusion: don't install symfony/symfony v4.0.3
- Conclusion: don't install symfony/symfony v4.0.2
- Conclusion: don't install symfony/symfony v4.0.1
- Conclusion: remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|remove symfony/process v3.4.15
- don't install symfony/process v3.3.0|don't install symfony/symfony v4.0.0


composer.json (require section)



"require": 
"php": ">=7.1",
"symfony/symfony": "~4.0",
"symfony/process": "^3.3",
"doctrine/orm": "dev-fork as 2.5.6",
"doctrine/doctrine-bundle": "1.*",
"symfony/swiftmailer-bundle": "~3.1",
"symfony/monolog-bundle": "~3.1",
"sensio/framework-extra-bundle": "^5.1",
"graylog2/gelf-php": "^1.4",
"doctrine/doctrine-migrations-bundle": "^1.1",
"awt/webauth-bundle": "3.0.*",
"awt/canvas-client-bundle": "6.2.*"










share|improve this question



















  • 1





    try composer update

    – Imanali Mamadiev
    Nov 14 '18 at 6:27











  • share the require sections of your composer.json

    – Trix
    Nov 14 '18 at 8:11











  • symfony/symfony includes symfony/process too. This leads to a conflict as a package cannot be installed in two versions. There was a bug in Composer that allowed this mistakenly in previous versions, but this bug was fixed in Composer 1.7.3. You now need to either remove the symfony/process dependency and stick with the Process component in version 3.4 or require all Symfony components explicitly if you need a newer version of the Process component (or update symfony/symfony to 4.1).

    – xabbuh
    Nov 14 '18 at 11:12











  • @Trix edited to include the require section

    – user6313136
    Nov 14 '18 at 17:14











  • @ImanaliMamadiev I did run composer update and get similar errors

    – user6313136
    Nov 14 '18 at 17:14















1















I'm trying to clone a github repository and issue a composer install on it. But I am getting this:




Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.




Your requirements could not be resolved to an installable set of packages. 
Problem 1
- Conclusion: remove symfony/polyfill-intl-icu v1.9.0
- Installation request for symfony/polyfill-intl-icu v1.9.0 -> satisfiable by symfony/polyfill-intl-icu[v1.9.0].
- Conclusion: remove symfony/process v3.4.15
- symfony/polyfill-intl-icu v1.9.0 requires symfony/intl ~2.3|~3.0|~4.0 -> satisfiable by symfony/symfony[v4.0.0].
- don't install symfony/process v3.4.15|remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|don't install symfony/process v3.4.15
- Installation request for symfony/process v3.4.15 -> satisfiable by symfony/process[v3.4.15].


When running composer update



Problem 1
- Conclusion: don't install symfony/symfony v4.1.7
- Conclusion: don't install symfony/symfony v4.1.6
- Conclusion: don't install symfony/symfony v4.1.5
- Conclusion: don't install symfony/symfony v4.1.4
- Conclusion: don't install symfony/symfony v4.1.3
- Conclusion: don't install symfony/symfony v4.1.2
- Conclusion: don't install symfony/symfony v4.1.1
- Conclusion: don't install symfony/symfony v4.1.0
- Conclusion: don't install symfony/symfony v4.0.14
- Conclusion: don't install symfony/symfony v4.0.13
- Conclusion: don't install symfony/symfony v4.0.12
- Conclusion: don't install symfony/symfony v4.0.11
- Conclusion: don't install symfony/symfony v4.0.10
- Conclusion: don't install symfony/symfony v4.0.9
- Conclusion: don't install symfony/symfony v4.0.8
- Conclusion: don't install symfony/symfony v4.0.7
- Conclusion: don't install symfony/symfony v4.0.6
- Conclusion: don't install symfony/symfony v4.0.5
- Conclusion: don't install symfony/symfony v4.0.4
- Conclusion: don't install symfony/symfony v4.0.3
- Conclusion: don't install symfony/symfony v4.0.2
- Conclusion: don't install symfony/symfony v4.0.1
- Conclusion: remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|remove symfony/process v3.4.15
- don't install symfony/process v3.3.0|don't install symfony/symfony v4.0.0


composer.json (require section)



"require": 
"php": ">=7.1",
"symfony/symfony": "~4.0",
"symfony/process": "^3.3",
"doctrine/orm": "dev-fork as 2.5.6",
"doctrine/doctrine-bundle": "1.*",
"symfony/swiftmailer-bundle": "~3.1",
"symfony/monolog-bundle": "~3.1",
"sensio/framework-extra-bundle": "^5.1",
"graylog2/gelf-php": "^1.4",
"doctrine/doctrine-migrations-bundle": "^1.1",
"awt/webauth-bundle": "3.0.*",
"awt/canvas-client-bundle": "6.2.*"










share|improve this question



















  • 1





    try composer update

    – Imanali Mamadiev
    Nov 14 '18 at 6:27











  • share the require sections of your composer.json

    – Trix
    Nov 14 '18 at 8:11











  • symfony/symfony includes symfony/process too. This leads to a conflict as a package cannot be installed in two versions. There was a bug in Composer that allowed this mistakenly in previous versions, but this bug was fixed in Composer 1.7.3. You now need to either remove the symfony/process dependency and stick with the Process component in version 3.4 or require all Symfony components explicitly if you need a newer version of the Process component (or update symfony/symfony to 4.1).

    – xabbuh
    Nov 14 '18 at 11:12











  • @Trix edited to include the require section

    – user6313136
    Nov 14 '18 at 17:14











  • @ImanaliMamadiev I did run composer update and get similar errors

    – user6313136
    Nov 14 '18 at 17:14













1












1








1


1






I'm trying to clone a github repository and issue a composer install on it. But I am getting this:




Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.




Your requirements could not be resolved to an installable set of packages. 
Problem 1
- Conclusion: remove symfony/polyfill-intl-icu v1.9.0
- Installation request for symfony/polyfill-intl-icu v1.9.0 -> satisfiable by symfony/polyfill-intl-icu[v1.9.0].
- Conclusion: remove symfony/process v3.4.15
- symfony/polyfill-intl-icu v1.9.0 requires symfony/intl ~2.3|~3.0|~4.0 -> satisfiable by symfony/symfony[v4.0.0].
- don't install symfony/process v3.4.15|remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|don't install symfony/process v3.4.15
- Installation request for symfony/process v3.4.15 -> satisfiable by symfony/process[v3.4.15].


When running composer update



Problem 1
- Conclusion: don't install symfony/symfony v4.1.7
- Conclusion: don't install symfony/symfony v4.1.6
- Conclusion: don't install symfony/symfony v4.1.5
- Conclusion: don't install symfony/symfony v4.1.4
- Conclusion: don't install symfony/symfony v4.1.3
- Conclusion: don't install symfony/symfony v4.1.2
- Conclusion: don't install symfony/symfony v4.1.1
- Conclusion: don't install symfony/symfony v4.1.0
- Conclusion: don't install symfony/symfony v4.0.14
- Conclusion: don't install symfony/symfony v4.0.13
- Conclusion: don't install symfony/symfony v4.0.12
- Conclusion: don't install symfony/symfony v4.0.11
- Conclusion: don't install symfony/symfony v4.0.10
- Conclusion: don't install symfony/symfony v4.0.9
- Conclusion: don't install symfony/symfony v4.0.8
- Conclusion: don't install symfony/symfony v4.0.7
- Conclusion: don't install symfony/symfony v4.0.6
- Conclusion: don't install symfony/symfony v4.0.5
- Conclusion: don't install symfony/symfony v4.0.4
- Conclusion: don't install symfony/symfony v4.0.3
- Conclusion: don't install symfony/symfony v4.0.2
- Conclusion: don't install symfony/symfony v4.0.1
- Conclusion: remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|remove symfony/process v3.4.15
- don't install symfony/process v3.3.0|don't install symfony/symfony v4.0.0


composer.json (require section)



"require": 
"php": ">=7.1",
"symfony/symfony": "~4.0",
"symfony/process": "^3.3",
"doctrine/orm": "dev-fork as 2.5.6",
"doctrine/doctrine-bundle": "1.*",
"symfony/swiftmailer-bundle": "~3.1",
"symfony/monolog-bundle": "~3.1",
"sensio/framework-extra-bundle": "^5.1",
"graylog2/gelf-php": "^1.4",
"doctrine/doctrine-migrations-bundle": "^1.1",
"awt/webauth-bundle": "3.0.*",
"awt/canvas-client-bundle": "6.2.*"










share|improve this question
















I'm trying to clone a github repository and issue a composer install on it. But I am getting this:




Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them.




Your requirements could not be resolved to an installable set of packages. 
Problem 1
- Conclusion: remove symfony/polyfill-intl-icu v1.9.0
- Installation request for symfony/polyfill-intl-icu v1.9.0 -> satisfiable by symfony/polyfill-intl-icu[v1.9.0].
- Conclusion: remove symfony/process v3.4.15
- symfony/polyfill-intl-icu v1.9.0 requires symfony/intl ~2.3|~3.0|~4.0 -> satisfiable by symfony/symfony[v4.0.0].
- don't install symfony/process v3.4.15|remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|don't install symfony/process v3.4.15
- Installation request for symfony/process v3.4.15 -> satisfiable by symfony/process[v3.4.15].


When running composer update



Problem 1
- Conclusion: don't install symfony/symfony v4.1.7
- Conclusion: don't install symfony/symfony v4.1.6
- Conclusion: don't install symfony/symfony v4.1.5
- Conclusion: don't install symfony/symfony v4.1.4
- Conclusion: don't install symfony/symfony v4.1.3
- Conclusion: don't install symfony/symfony v4.1.2
- Conclusion: don't install symfony/symfony v4.1.1
- Conclusion: don't install symfony/symfony v4.1.0
- Conclusion: don't install symfony/symfony v4.0.14
- Conclusion: don't install symfony/symfony v4.0.13
- Conclusion: don't install symfony/symfony v4.0.12
- Conclusion: don't install symfony/symfony v4.0.11
- Conclusion: don't install symfony/symfony v4.0.10
- Conclusion: don't install symfony/symfony v4.0.9
- Conclusion: don't install symfony/symfony v4.0.8
- Conclusion: don't install symfony/symfony v4.0.7
- Conclusion: don't install symfony/symfony v4.0.6
- Conclusion: don't install symfony/symfony v4.0.5
- Conclusion: don't install symfony/symfony v4.0.4
- Conclusion: don't install symfony/symfony v4.0.3
- Conclusion: don't install symfony/symfony v4.0.2
- Conclusion: don't install symfony/symfony v4.0.1
- Conclusion: remove symfony/symfony v4.0.0
- don't install symfony/symfony v4.0.0|remove symfony/process v3.4.15
- don't install symfony/process v3.3.0|don't install symfony/symfony v4.0.0


composer.json (require section)



"require": 
"php": ">=7.1",
"symfony/symfony": "~4.0",
"symfony/process": "^3.3",
"doctrine/orm": "dev-fork as 2.5.6",
"doctrine/doctrine-bundle": "1.*",
"symfony/swiftmailer-bundle": "~3.1",
"symfony/monolog-bundle": "~3.1",
"sensio/framework-extra-bundle": "^5.1",
"graylog2/gelf-php": "^1.4",
"doctrine/doctrine-migrations-bundle": "^1.1",
"awt/webauth-bundle": "3.0.*",
"awt/canvas-client-bundle": "6.2.*"







symfony composer-php symfony4 symfony-process composer.json






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 14 '18 at 17:44









Trix

9,95785174




9,95785174










asked Nov 14 '18 at 0:59









user6313136user6313136

596




596







  • 1





    try composer update

    – Imanali Mamadiev
    Nov 14 '18 at 6:27











  • share the require sections of your composer.json

    – Trix
    Nov 14 '18 at 8:11











  • symfony/symfony includes symfony/process too. This leads to a conflict as a package cannot be installed in two versions. There was a bug in Composer that allowed this mistakenly in previous versions, but this bug was fixed in Composer 1.7.3. You now need to either remove the symfony/process dependency and stick with the Process component in version 3.4 or require all Symfony components explicitly if you need a newer version of the Process component (or update symfony/symfony to 4.1).

    – xabbuh
    Nov 14 '18 at 11:12











  • @Trix edited to include the require section

    – user6313136
    Nov 14 '18 at 17:14











  • @ImanaliMamadiev I did run composer update and get similar errors

    – user6313136
    Nov 14 '18 at 17:14












  • 1





    try composer update

    – Imanali Mamadiev
    Nov 14 '18 at 6:27











  • share the require sections of your composer.json

    – Trix
    Nov 14 '18 at 8:11











  • symfony/symfony includes symfony/process too. This leads to a conflict as a package cannot be installed in two versions. There was a bug in Composer that allowed this mistakenly in previous versions, but this bug was fixed in Composer 1.7.3. You now need to either remove the symfony/process dependency and stick with the Process component in version 3.4 or require all Symfony components explicitly if you need a newer version of the Process component (or update symfony/symfony to 4.1).

    – xabbuh
    Nov 14 '18 at 11:12











  • @Trix edited to include the require section

    – user6313136
    Nov 14 '18 at 17:14











  • @ImanaliMamadiev I did run composer update and get similar errors

    – user6313136
    Nov 14 '18 at 17:14







1




1





try composer update

– Imanali Mamadiev
Nov 14 '18 at 6:27





try composer update

– Imanali Mamadiev
Nov 14 '18 at 6:27













share the require sections of your composer.json

– Trix
Nov 14 '18 at 8:11





share the require sections of your composer.json

– Trix
Nov 14 '18 at 8:11













symfony/symfony includes symfony/process too. This leads to a conflict as a package cannot be installed in two versions. There was a bug in Composer that allowed this mistakenly in previous versions, but this bug was fixed in Composer 1.7.3. You now need to either remove the symfony/process dependency and stick with the Process component in version 3.4 or require all Symfony components explicitly if you need a newer version of the Process component (or update symfony/symfony to 4.1).

– xabbuh
Nov 14 '18 at 11:12





symfony/symfony includes symfony/process too. This leads to a conflict as a package cannot be installed in two versions. There was a bug in Composer that allowed this mistakenly in previous versions, but this bug was fixed in Composer 1.7.3. You now need to either remove the symfony/process dependency and stick with the Process component in version 3.4 or require all Symfony components explicitly if you need a newer version of the Process component (or update symfony/symfony to 4.1).

– xabbuh
Nov 14 '18 at 11:12













@Trix edited to include the require section

– user6313136
Nov 14 '18 at 17:14





@Trix edited to include the require section

– user6313136
Nov 14 '18 at 17:14













@ImanaliMamadiev I did run composer update and get similar errors

– user6313136
Nov 14 '18 at 17:14





@ImanaliMamadiev I did run composer update and get similar errors

– user6313136
Nov 14 '18 at 17:14












3 Answers
3






active

oldest

votes


















0














share your comooser.json file please , i think you should update it :



 "require": 
"symfony/process": "3.4.*",
"symfony/symfony": "3.4.*"
,


or



 "require": 
"symfony/process": "4.1.*",
"symfony/symfony": "4.1.*"
,





share|improve this answer























  • Edited to include the require section of the composer.json

    – user6313136
    Nov 14 '18 at 17:13


















0














You may use depends & prohibits on composer to see what exactly you should do:



composer depends symfony/process 3.4.15


and



composer prohibits symfony/symfony 4


This two commands tell you what is the conflict and what you should do.



The main problem is that your composer.json and composer.lock are not in sync. The first file tells composer what are required package & their version constraints, and the second one shares the exact same package version between collaborators, for consistency.



If the repository owner does not help you with this problem, the only way you have is:



rm composer.lock
rm -rf vendor
composer install


This will remove vendor directory contents and install a fressh copy of all dependencies, according to just composer.json






share|improve this answer






























    -1














    Solution was to download a previous version of composer (1.7.2) manually from the website and overwrite my 1.7.3 version.






    share|improve this answer























    • Conflicting composer.json & composer.lock files does not get solved by reinstalling other versions of composer

      – Trix
      Nov 16 '18 at 11:11










    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291681%2fthe-lock-file-is-not-up-to-date-with-the-latest-changes-in-composer-json%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    share your comooser.json file please , i think you should update it :



     "require": 
    "symfony/process": "3.4.*",
    "symfony/symfony": "3.4.*"
    ,


    or



     "require": 
    "symfony/process": "4.1.*",
    "symfony/symfony": "4.1.*"
    ,





    share|improve this answer























    • Edited to include the require section of the composer.json

      – user6313136
      Nov 14 '18 at 17:13















    0














    share your comooser.json file please , i think you should update it :



     "require": 
    "symfony/process": "3.4.*",
    "symfony/symfony": "3.4.*"
    ,


    or



     "require": 
    "symfony/process": "4.1.*",
    "symfony/symfony": "4.1.*"
    ,





    share|improve this answer























    • Edited to include the require section of the composer.json

      – user6313136
      Nov 14 '18 at 17:13













    0












    0








    0







    share your comooser.json file please , i think you should update it :



     "require": 
    "symfony/process": "3.4.*",
    "symfony/symfony": "3.4.*"
    ,


    or



     "require": 
    "symfony/process": "4.1.*",
    "symfony/symfony": "4.1.*"
    ,





    share|improve this answer













    share your comooser.json file please , i think you should update it :



     "require": 
    "symfony/process": "3.4.*",
    "symfony/symfony": "3.4.*"
    ,


    or



     "require": 
    "symfony/process": "4.1.*",
    "symfony/symfony": "4.1.*"
    ,






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 14 '18 at 9:49









    mohamed jebrimohamed jebri

    1019




    1019












    • Edited to include the require section of the composer.json

      – user6313136
      Nov 14 '18 at 17:13

















    • Edited to include the require section of the composer.json

      – user6313136
      Nov 14 '18 at 17:13
















    Edited to include the require section of the composer.json

    – user6313136
    Nov 14 '18 at 17:13





    Edited to include the require section of the composer.json

    – user6313136
    Nov 14 '18 at 17:13













    0














    You may use depends & prohibits on composer to see what exactly you should do:



    composer depends symfony/process 3.4.15


    and



    composer prohibits symfony/symfony 4


    This two commands tell you what is the conflict and what you should do.



    The main problem is that your composer.json and composer.lock are not in sync. The first file tells composer what are required package & their version constraints, and the second one shares the exact same package version between collaborators, for consistency.



    If the repository owner does not help you with this problem, the only way you have is:



    rm composer.lock
    rm -rf vendor
    composer install


    This will remove vendor directory contents and install a fressh copy of all dependencies, according to just composer.json






    share|improve this answer



























      0














      You may use depends & prohibits on composer to see what exactly you should do:



      composer depends symfony/process 3.4.15


      and



      composer prohibits symfony/symfony 4


      This two commands tell you what is the conflict and what you should do.



      The main problem is that your composer.json and composer.lock are not in sync. The first file tells composer what are required package & their version constraints, and the second one shares the exact same package version between collaborators, for consistency.



      If the repository owner does not help you with this problem, the only way you have is:



      rm composer.lock
      rm -rf vendor
      composer install


      This will remove vendor directory contents and install a fressh copy of all dependencies, according to just composer.json






      share|improve this answer

























        0












        0








        0







        You may use depends & prohibits on composer to see what exactly you should do:



        composer depends symfony/process 3.4.15


        and



        composer prohibits symfony/symfony 4


        This two commands tell you what is the conflict and what you should do.



        The main problem is that your composer.json and composer.lock are not in sync. The first file tells composer what are required package & their version constraints, and the second one shares the exact same package version between collaborators, for consistency.



        If the repository owner does not help you with this problem, the only way you have is:



        rm composer.lock
        rm -rf vendor
        composer install


        This will remove vendor directory contents and install a fressh copy of all dependencies, according to just composer.json






        share|improve this answer













        You may use depends & prohibits on composer to see what exactly you should do:



        composer depends symfony/process 3.4.15


        and



        composer prohibits symfony/symfony 4


        This two commands tell you what is the conflict and what you should do.



        The main problem is that your composer.json and composer.lock are not in sync. The first file tells composer what are required package & their version constraints, and the second one shares the exact same package version between collaborators, for consistency.



        If the repository owner does not help you with this problem, the only way you have is:



        rm composer.lock
        rm -rf vendor
        composer install


        This will remove vendor directory contents and install a fressh copy of all dependencies, according to just composer.json







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 14 '18 at 17:37









        TrixTrix

        9,95785174




        9,95785174





















            -1














            Solution was to download a previous version of composer (1.7.2) manually from the website and overwrite my 1.7.3 version.






            share|improve this answer























            • Conflicting composer.json & composer.lock files does not get solved by reinstalling other versions of composer

              – Trix
              Nov 16 '18 at 11:11















            -1














            Solution was to download a previous version of composer (1.7.2) manually from the website and overwrite my 1.7.3 version.






            share|improve this answer























            • Conflicting composer.json & composer.lock files does not get solved by reinstalling other versions of composer

              – Trix
              Nov 16 '18 at 11:11













            -1












            -1








            -1







            Solution was to download a previous version of composer (1.7.2) manually from the website and overwrite my 1.7.3 version.






            share|improve this answer













            Solution was to download a previous version of composer (1.7.2) manually from the website and overwrite my 1.7.3 version.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 15 '18 at 16:59









            user6313136user6313136

            596




            596












            • Conflicting composer.json & composer.lock files does not get solved by reinstalling other versions of composer

              – Trix
              Nov 16 '18 at 11:11

















            • Conflicting composer.json & composer.lock files does not get solved by reinstalling other versions of composer

              – Trix
              Nov 16 '18 at 11:11
















            Conflicting composer.json & composer.lock files does not get solved by reinstalling other versions of composer

            – Trix
            Nov 16 '18 at 11:11





            Conflicting composer.json & composer.lock files does not get solved by reinstalling other versions of composer

            – Trix
            Nov 16 '18 at 11:11

















            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53291681%2fthe-lock-file-is-not-up-to-date-with-the-latest-changes-in-composer-json%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            這個網誌中的熱門文章

            How to read a connectionString WITH PROVIDER in .NET Core?

            In R, how to develop a multiplot heatmap.2 figure showing key labels successfully

            Museum of Modern and Contemporary Art of Trento and Rovereto