Upgrade from fedora 25 to 27 - Conflict issue

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I tried to upgrade from fedora 25 to fedora 27. When running



sudo dnf system-upgrade download --releasever=27 --allowerasing


I encountered a transaction check error regarding python. The error summary can be found here



I paste here the first five lines



 file /usr/lib/python2.7/site-packages/IPython/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/magics/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/kernel/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch


Any idea on how to overcome this issue and upgrade?







share|improve this question
















  • 1




    You could start by not skipping releases - upgrade to 26 first and then to 27.
    – schaiba
    Jan 5 at 13:59






  • 1




    Did you apply all the updates to F25 before attempting to upgrade to F27?
    – fpmurphy1
    Jan 5 at 14:01










  • @fpmurphy1 : Thank you for your comment! Yes, first I run sudo dnf upgrade --refresh
    – Thanos
    Jan 5 at 14:44










  • What if you add --best?
    – mattdm
    Jan 5 at 19:06










  • @schaiba : Thanks for your comment. I tried to upgrde to f26, but I couldn't. Check this question. unix.stackexchange.com/questions/415059/…
    – Thanos
    Jan 5 at 19:24














up vote
0
down vote

favorite












I tried to upgrade from fedora 25 to fedora 27. When running



sudo dnf system-upgrade download --releasever=27 --allowerasing


I encountered a transaction check error regarding python. The error summary can be found here



I paste here the first five lines



 file /usr/lib/python2.7/site-packages/IPython/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/magics/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/kernel/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch


Any idea on how to overcome this issue and upgrade?







share|improve this question
















  • 1




    You could start by not skipping releases - upgrade to 26 first and then to 27.
    – schaiba
    Jan 5 at 13:59






  • 1




    Did you apply all the updates to F25 before attempting to upgrade to F27?
    – fpmurphy1
    Jan 5 at 14:01










  • @fpmurphy1 : Thank you for your comment! Yes, first I run sudo dnf upgrade --refresh
    – Thanos
    Jan 5 at 14:44










  • What if you add --best?
    – mattdm
    Jan 5 at 19:06










  • @schaiba : Thanks for your comment. I tried to upgrde to f26, but I couldn't. Check this question. unix.stackexchange.com/questions/415059/…
    – Thanos
    Jan 5 at 19:24












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I tried to upgrade from fedora 25 to fedora 27. When running



sudo dnf system-upgrade download --releasever=27 --allowerasing


I encountered a transaction check error regarding python. The error summary can be found here



I paste here the first five lines



 file /usr/lib/python2.7/site-packages/IPython/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/magics/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/kernel/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch


Any idea on how to overcome this issue and upgrade?







share|improve this question












I tried to upgrade from fedora 25 to fedora 27. When running



sudo dnf system-upgrade download --releasever=27 --allowerasing


I encountered a transaction check error regarding python. The error summary can be found here



I paste here the first five lines



 file /usr/lib/python2.7/site-packages/IPython/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/magics/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/kernel/__init__.py from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch
file /usr/lib/python2.7/site-packages/IPython/core/__init__.pyc from install of python2-ipython-5.5.0-1.fc27.noarch conflicts with file from package python-ipython-console-3.2.1-8.fc25.noarch


Any idea on how to overcome this issue and upgrade?









share|improve this question











share|improve this question




share|improve this question










asked Jan 5 at 13:57









Thanos

17510




17510







  • 1




    You could start by not skipping releases - upgrade to 26 first and then to 27.
    – schaiba
    Jan 5 at 13:59






  • 1




    Did you apply all the updates to F25 before attempting to upgrade to F27?
    – fpmurphy1
    Jan 5 at 14:01










  • @fpmurphy1 : Thank you for your comment! Yes, first I run sudo dnf upgrade --refresh
    – Thanos
    Jan 5 at 14:44










  • What if you add --best?
    – mattdm
    Jan 5 at 19:06










  • @schaiba : Thanks for your comment. I tried to upgrde to f26, but I couldn't. Check this question. unix.stackexchange.com/questions/415059/…
    – Thanos
    Jan 5 at 19:24












  • 1




    You could start by not skipping releases - upgrade to 26 first and then to 27.
    – schaiba
    Jan 5 at 13:59






  • 1




    Did you apply all the updates to F25 before attempting to upgrade to F27?
    – fpmurphy1
    Jan 5 at 14:01










  • @fpmurphy1 : Thank you for your comment! Yes, first I run sudo dnf upgrade --refresh
    – Thanos
    Jan 5 at 14:44










  • What if you add --best?
    – mattdm
    Jan 5 at 19:06










  • @schaiba : Thanks for your comment. I tried to upgrde to f26, but I couldn't. Check this question. unix.stackexchange.com/questions/415059/…
    – Thanos
    Jan 5 at 19:24







1




1




You could start by not skipping releases - upgrade to 26 first and then to 27.
– schaiba
Jan 5 at 13:59




You could start by not skipping releases - upgrade to 26 first and then to 27.
– schaiba
Jan 5 at 13:59




1




1




Did you apply all the updates to F25 before attempting to upgrade to F27?
– fpmurphy1
Jan 5 at 14:01




Did you apply all the updates to F25 before attempting to upgrade to F27?
– fpmurphy1
Jan 5 at 14:01












@fpmurphy1 : Thank you for your comment! Yes, first I run sudo dnf upgrade --refresh
– Thanos
Jan 5 at 14:44




@fpmurphy1 : Thank you for your comment! Yes, first I run sudo dnf upgrade --refresh
– Thanos
Jan 5 at 14:44












What if you add --best?
– mattdm
Jan 5 at 19:06




What if you add --best?
– mattdm
Jan 5 at 19:06












@schaiba : Thanks for your comment. I tried to upgrde to f26, but I couldn't. Check this question. unix.stackexchange.com/questions/415059/…
– Thanos
Jan 5 at 19:24




@schaiba : Thanks for your comment. I tried to upgrde to f26, but I couldn't. Check this question. unix.stackexchange.com/questions/415059/…
– Thanos
Jan 5 at 19:24










3 Answers
3






active

oldest

votes

















up vote
2
down vote













Had exact same issue. Not as complex as it seems. You first need to do:
sudo dnf remove python-ipython-console



Then proceed with
sudo dnf system-upgrade download --releasever=27 --allowerasing
which will automatically reinstall ipython (which I presume was a faulty install).






share|improve this answer



























    up vote
    1
    down vote













    I'm not sure offhand what's causing this particular issue, but a general approach which works in most cases is: remove the package that's causing the problem, and add it back after the upgrade.



    Of course, this doesn't work if it's a core package which can't be removed without breaking the system, and it's inconvenient if it's a package which a lot of things require, but neither of those should be the case with python-ipython-console.






    share|improve this answer




















    • Thank you very much for your answer! I tried first to upgrade to fedora 26, but I couldn't... See here.. unix.stackexchange.com/questions/415059/…
      – Thanos
      Jan 5 at 19:22

















    up vote
    1
    down vote













    I am having the same issue, but I think I have tracked down the problem. First, a question for you: are you using Sage? (package sagemath) The Sage packages require ipython-console, but they seem to have something wrong with their dependencies. It seems like the Sage packages aren't recognizing the new version of ipython-console in F27, so in the upgrade from F25, Sage is still expecting to see the older version of ipython-console. The result is that the upgrade fails due to file conflicts. The suggestion to remove ipython-console, then upgrade, seems right, but you need to be aware that you will also be uninstalling Sage and will need to reinstall it, too. Backing up your Sage data before any of this would probably be a good idea.






    share|improve this answer




















    • That seems very plausible. Have you filed a bug against the sagemath package?
      – mattdm
      Jan 23 at 1:12










    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414988%2fupgrade-from-fedora-25-to-27-conflict-issue%23new-answer', 'question_page');

    );

    Post as a guest






























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    Had exact same issue. Not as complex as it seems. You first need to do:
    sudo dnf remove python-ipython-console



    Then proceed with
    sudo dnf system-upgrade download --releasever=27 --allowerasing
    which will automatically reinstall ipython (which I presume was a faulty install).






    share|improve this answer
























      up vote
      2
      down vote













      Had exact same issue. Not as complex as it seems. You first need to do:
      sudo dnf remove python-ipython-console



      Then proceed with
      sudo dnf system-upgrade download --releasever=27 --allowerasing
      which will automatically reinstall ipython (which I presume was a faulty install).






      share|improve this answer






















        up vote
        2
        down vote










        up vote
        2
        down vote









        Had exact same issue. Not as complex as it seems. You first need to do:
        sudo dnf remove python-ipython-console



        Then proceed with
        sudo dnf system-upgrade download --releasever=27 --allowerasing
        which will automatically reinstall ipython (which I presume was a faulty install).






        share|improve this answer












        Had exact same issue. Not as complex as it seems. You first need to do:
        sudo dnf remove python-ipython-console



        Then proceed with
        sudo dnf system-upgrade download --releasever=27 --allowerasing
        which will automatically reinstall ipython (which I presume was a faulty install).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 8 at 17:57









        user269488

        211




        211






















            up vote
            1
            down vote













            I'm not sure offhand what's causing this particular issue, but a general approach which works in most cases is: remove the package that's causing the problem, and add it back after the upgrade.



            Of course, this doesn't work if it's a core package which can't be removed without breaking the system, and it's inconvenient if it's a package which a lot of things require, but neither of those should be the case with python-ipython-console.






            share|improve this answer




















            • Thank you very much for your answer! I tried first to upgrade to fedora 26, but I couldn't... See here.. unix.stackexchange.com/questions/415059/…
              – Thanos
              Jan 5 at 19:22














            up vote
            1
            down vote













            I'm not sure offhand what's causing this particular issue, but a general approach which works in most cases is: remove the package that's causing the problem, and add it back after the upgrade.



            Of course, this doesn't work if it's a core package which can't be removed without breaking the system, and it's inconvenient if it's a package which a lot of things require, but neither of those should be the case with python-ipython-console.






            share|improve this answer




















            • Thank you very much for your answer! I tried first to upgrade to fedora 26, but I couldn't... See here.. unix.stackexchange.com/questions/415059/…
              – Thanos
              Jan 5 at 19:22












            up vote
            1
            down vote










            up vote
            1
            down vote









            I'm not sure offhand what's causing this particular issue, but a general approach which works in most cases is: remove the package that's causing the problem, and add it back after the upgrade.



            Of course, this doesn't work if it's a core package which can't be removed without breaking the system, and it's inconvenient if it's a package which a lot of things require, but neither of those should be the case with python-ipython-console.






            share|improve this answer












            I'm not sure offhand what's causing this particular issue, but a general approach which works in most cases is: remove the package that's causing the problem, and add it back after the upgrade.



            Of course, this doesn't work if it's a core package which can't be removed without breaking the system, and it's inconvenient if it's a package which a lot of things require, but neither of those should be the case with python-ipython-console.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 5 at 19:07









            mattdm

            27k1170109




            27k1170109











            • Thank you very much for your answer! I tried first to upgrade to fedora 26, but I couldn't... See here.. unix.stackexchange.com/questions/415059/…
              – Thanos
              Jan 5 at 19:22
















            • Thank you very much for your answer! I tried first to upgrade to fedora 26, but I couldn't... See here.. unix.stackexchange.com/questions/415059/…
              – Thanos
              Jan 5 at 19:22















            Thank you very much for your answer! I tried first to upgrade to fedora 26, but I couldn't... See here.. unix.stackexchange.com/questions/415059/…
            – Thanos
            Jan 5 at 19:22




            Thank you very much for your answer! I tried first to upgrade to fedora 26, but I couldn't... See here.. unix.stackexchange.com/questions/415059/…
            – Thanos
            Jan 5 at 19:22










            up vote
            1
            down vote













            I am having the same issue, but I think I have tracked down the problem. First, a question for you: are you using Sage? (package sagemath) The Sage packages require ipython-console, but they seem to have something wrong with their dependencies. It seems like the Sage packages aren't recognizing the new version of ipython-console in F27, so in the upgrade from F25, Sage is still expecting to see the older version of ipython-console. The result is that the upgrade fails due to file conflicts. The suggestion to remove ipython-console, then upgrade, seems right, but you need to be aware that you will also be uninstalling Sage and will need to reinstall it, too. Backing up your Sage data before any of this would probably be a good idea.






            share|improve this answer




















            • That seems very plausible. Have you filed a bug against the sagemath package?
              – mattdm
              Jan 23 at 1:12














            up vote
            1
            down vote













            I am having the same issue, but I think I have tracked down the problem. First, a question for you: are you using Sage? (package sagemath) The Sage packages require ipython-console, but they seem to have something wrong with their dependencies. It seems like the Sage packages aren't recognizing the new version of ipython-console in F27, so in the upgrade from F25, Sage is still expecting to see the older version of ipython-console. The result is that the upgrade fails due to file conflicts. The suggestion to remove ipython-console, then upgrade, seems right, but you need to be aware that you will also be uninstalling Sage and will need to reinstall it, too. Backing up your Sage data before any of this would probably be a good idea.






            share|improve this answer




















            • That seems very plausible. Have you filed a bug against the sagemath package?
              – mattdm
              Jan 23 at 1:12












            up vote
            1
            down vote










            up vote
            1
            down vote









            I am having the same issue, but I think I have tracked down the problem. First, a question for you: are you using Sage? (package sagemath) The Sage packages require ipython-console, but they seem to have something wrong with their dependencies. It seems like the Sage packages aren't recognizing the new version of ipython-console in F27, so in the upgrade from F25, Sage is still expecting to see the older version of ipython-console. The result is that the upgrade fails due to file conflicts. The suggestion to remove ipython-console, then upgrade, seems right, but you need to be aware that you will also be uninstalling Sage and will need to reinstall it, too. Backing up your Sage data before any of this would probably be a good idea.






            share|improve this answer












            I am having the same issue, but I think I have tracked down the problem. First, a question for you: are you using Sage? (package sagemath) The Sage packages require ipython-console, but they seem to have something wrong with their dependencies. It seems like the Sage packages aren't recognizing the new version of ipython-console in F27, so in the upgrade from F25, Sage is still expecting to see the older version of ipython-console. The result is that the upgrade fails due to file conflicts. The suggestion to remove ipython-console, then upgrade, seems right, but you need to be aware that you will also be uninstalling Sage and will need to reinstall it, too. Backing up your Sage data before any of this would probably be a good idea.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 22 at 19:38









            user128390

            1111




            1111











            • That seems very plausible. Have you filed a bug against the sagemath package?
              – mattdm
              Jan 23 at 1:12
















            • That seems very plausible. Have you filed a bug against the sagemath package?
              – mattdm
              Jan 23 at 1:12















            That seems very plausible. Have you filed a bug against the sagemath package?
            – mattdm
            Jan 23 at 1:12




            That seems very plausible. Have you filed a bug against the sagemath package?
            – mattdm
            Jan 23 at 1:12












             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414988%2fupgrade-from-fedora-25-to-27-conflict-issue%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?