Updated my PHP, phpMyAdmin & Other Errors

General support questions
Post Reply
rnacker
Posts: 1
Joined: 2018/02/26 19:25:33

Updated my PHP, phpMyAdmin & Other Errors

Post by rnacker » 2018/02/26 19:27:23

So I updated PHP and trying to access phpMyAdmin and it keeps saying denied. I try and remove it and it cant find the package, I try and reinstall it and get this huge error. Not sure where to go from here.

Code: Select all

    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
     * base: mirror.atlanticmetro.net
     * epel: fedora-epel.mirrors.tds.net
     * extras: mirror.cs.pitt.edu
     * updates: mirror.steadfast.net
     * webtatic: us-east.repo.webtatic.com
    Resolving Dependencies
    --> Running transaction check
    ---> Package phpMyAdmin.noarch 0:4.4.15.10-2.el7 will be installed
    --> Processing Dependency: php-php-gettext for package: phpMyAdmin-4.4.15.10-2.el7.noarch
    --> Processing Dependency: php-tcpdf for package: phpMyAdmin-4.4.15.10-2.el7.noarch
    --> Processing Dependency: php-tcpdf-dejavu-sans-fonts for package: phpMyAdmin-4.4.15.10-2.el7.noarch
    --> Running transaction check
    ---> Package php-php-gettext.noarch 0:1.0.12-1.el7 will be installed
    ---> Package php-tcpdf.noarch 0:6.2.13-1.el7 will be installed
    --> Processing Dependency: php-bcmath for package: php-tcpdf-6.2.13-1.el7.noarch
    --> Processing Dependency: php-composer(fedora/autoloader) for package: php-tcpdf-6.2.13-1.el7.noarch
    --> Processing Dependency: php-posix for package: php-tcpdf-6.2.13-1.el7.noarch
    --> Processing Dependency: php-tidy for package: php-tcpdf-6.2.13-1.el7.noarch
    ---> Package php-tcpdf-dejavu-sans-fonts.noarch 0:6.2.13-1.el7 will be installed
    --> Running transaction check
    ---> Package php-fedora-autoloader.noarch 0:1.0.0-1.el7 will be installed
    ---> Package php56w-bcmath.x86_64 0:5.6.33-1.w7 will be installed
    ---> Package php56w-process.x86_64 0:5.6.33-1.w7 will be installed
    ---> Package php56w-tidy.x86_64 0:5.6.33-1.w7 will be installed
    --> Processing Dependency: libtidy.so.5()(64bit) for package: php56w-tidy-5.6.33-1.w7.x86_64
    --> Running transaction check
    ---> Package libtidy.x86_64 0:0.99.0-31.20091203.el7 will be updated
    ---> Package libtidy.x86_64 0:5.4.0-1.el7 will be an update
    Removing libtidy.x86_64 0:0.99.0-31.20091203.el7 - ud due to obsoletes from installed compat-libtidy-0.99.0-37.20091203.el7.x86_64
    --> Restarting Dependency Resolution with new changes.
    --> Running transaction check
    ---> Package libtidy.x86_64 0:0.99.0-31.20091203.el7 will be updated
    --> Finished Dependency Resolution
    Error:  Multilib version problems found. This often means that the root
           cause is something else and multilib version checking is just
           pointing out that there is a problem. Eg.:
           
             1. You have an upgrade for libtidy which is missing some
                dependency that another package requires. Yum is trying to
                solve this by installing an older version of libtidy of the
                different architecture. If you exclude the bad architecture
                yum will tell you what the root cause is (which package
                requires what). You can try redoing the upgrade with
                --exclude libtidy.otherarch ... this should give you an error
                message showing the root cause of the problem.
           
             2. You have multiple architectures of libtidy installed, but
                yum can only see an upgrade for one of those architectures.
                If you don't want/need both architectures anymore then you
                can remove the one with the missing update and everything
                will work.
           
             3. You have duplicate versions of libtidy installed already.
                You can use "yum check" to get yum show these errors.
           
           ...you can also use --setopt=protected_multilib=false to remove
           this checking, however this is almost never the correct thing to
           do as something else is very likely to go wrong (often causing
           much more problems).
           
           Protected multilib versions: libtidy-5.4.0-1.el7.x86_64 != libtidy-0.99.0-31.20091203.el7.x86_64

Post Reply