Welcome to Centmin Mod Community
Become a Member

problem with yum update

Discussion in 'Install & Upgrades or Pre-Install Questions' started by adamus007p, Nov 19, 2026 at 9:37 AM.

  1. adamus007p

    adamus007p Member

    381
    20
    18
    Feb 8, 2019
    Ratings:
    +40
    Local Time:
    3:44 PM
    Hi @eva200,

    I'm running Centmin Mod 132.00stable on AlmaLinux 9, and I'm experiencing a package dependency conflict when attempting to update the system.

    After investigating, I confirmed that python3-libselinux is locked to an older version by Centmin Mod's PHP libraries versionlock mechanism.

    Before making any changes, I'd like to confirm the recommended and safest way to resolve this issue.

    1. Environment

    • OS: AlmaLinux 9 (EL9)
    • Centmin Mod: 132.00stable
    • Nginx installed: 1.31.8
    • Latest Nginx available: 1.31.9
    • Centmin Mod local code: Up to date
    • Repository: Remi enabled during updates
    • Date: November 19, 2026

    2. Original update command and errors

    Command:

    Code (Text):
    yum update --disableplugin=priorities --setopt=deltarpm=0 --enablerepo=remi
    


    Output:

    Code (Text):
    No matches found for the following disable plugin patterns: priorities
    
    Last metadata expiration check: 0:00:19 ago on Thu 19 Nov 2026 12:28:02 AM CET.
    
    Error:
     Problem 1: cannot install both libselinux-3.6-4.el9.x86_64 from baseos and libselinux-3.6-3.el9.x86_64 from @System
      - package python3-libselinux-3.6-3.el9.x86_64 from @System requires libselinux(x86-64) = 3.6-3.el9, but none of the providers can be installed
      - cannot install the best update candidate for package libselinux-3.6-3.el9.x86_64
      - problem with installed package python3-libselinux-3.6-3.el9.x86_64
    
     Problem 2: cannot install both libselinux-3.6-4.el9.x86_64 from baseos and libselinux-3.6-3.el9.x86_64 from @System
      - package python3-libselinux-3.6-3.el9.x86_64 from @System requires libselinux(x86-64) = 3.6-3.el9, but none of the providers can be installed
      - package libselinux-devel-3.6-4.el9.x86_64 from appstream requires libselinux(x86-64) = 3.6-4.el9, but none of the providers can be installed
      - package cloud-init-24.4-8.el9_8.1.alma.1.noarch from @System requires libselinux-python3, but none of the providers can be installed
      - cannot install the best update candidate for package libselinux-devel-3.6-3.el9.x86_64
      - cannot install the best update candidate for package cloud-init-24.4-8.el9_8.1.alma.1.noarch
      - package python3-libselinux-3.6-4.el9.x86_64 from appstream is filtered out by exclude filtering
    
     Problem 3: package python3-libselinux-3.6-3.el9.x86_64 from @System requires libselinux(x86-64) = 3.6-3.el9, but none of the providers can be installed
      - cannot install both libselinux-3.6-4.el9.x86_64 from baseos and libselinux-3.6-3.el9.x86_64 from @System
      - package python3-libsemanage-3.6-5.el9_6.x86_64 from @System requires libselinux-python3, but none of the providers can be installed
      - package libselinux-utils-3.6-4.el9.x86_64 from baseos requires libselinux(x86-64) = 3.6-4.el9, but none of the providers can be installed
      - cannot install the best update candidate for package python3-libsemanage-3.6-5.el9_6.x86_64
      - cannot install the best update candidate for package libselinux-utils-3.6-3.el9.x86_64
      - package python3-libselinux-3.6-4.el9.x86_64 from appstream is filtered out by exclude filtering
    
    (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
    


    3. DNF exclude configuration

    I checked the exclusion rules:

    Code (Text):
    grep -RniE '^[[:space:]]*(exclude|excludepkgs|includepkgs)[[:space:]]*=' /etc/dnf/dnf.conf /etc/yum.conf /etc/yum.repos.d/ 2>/dev/null
    


    Output:

    Code (Text):
    /etc/dnf/dnf.conf:6:exclude=*.i686 perl-DBD-MySQL
    /etc/yum.conf:6:exclude=*.i686 perl-DBD-MySQL
    /etc/yum.repos.d/epel.repo:12:exclude=ImageMagick* mytop nodejs nginx scl-utils percona-xtrabackup
    /etc/yum.repos.d/mariadb.repo:7:exclude=MariaDB-Galera-server
    


    None of these explicit exclusions appears to block python3-libselinux.

    4. Versionlock investigation

    Command:

    Code (Text):
    dnf versionlock list | grep -Ei 'selinux|semanage'
    


    Output:

    Code (Text):
    python3-libselinux-0:3.6-3.el9.*
    



    I also checked the versionlock configuration file:

    Code (Text):
    grep -n -C 3 'python3-libselinux' /etc/dnf/plugins/versionlock.list*
    


    Output:

    Code (Text):
    11-libxcrypt-compat-0:4.4.18-3.el9.*
    12-oniguruma5php-0:6.9.10-1.el9.remi.*
    13-oniguruma5php-devel-0:6.9.10-1.el9.remi.*
    14:python3-libselinux-0:3.6-3.el9.*
    15-uw-imap-devel-0:2007f-30.el9.remi.*
    16-
    17-# Added lock on Wed Oct 21 16:37:14 2026
    


    This confirms that python3-libselinux is locked to 3.6-3.el9, while AlmaLinux repositories provide 3.6-4.el9.

    The locked version prevents the required libselinux packages from being updated together, resulting in dependency conflicts during a normal system update.

    5. Centmin Mod PHP libraries versionlock status

    Command:

    Code (Text):
    /usr/local/src/centminmod/tools/php-libs-versionlock.sh status
    


    Output:

    Code (Text):
    php-libs-versionlock: unmarked locks the next menu 5 run adopts: GeoIP GeoIP-devel libcap-ng-python3 libicu73 libicu73-devel libmcrypt libmcrypt-devel libtidy libtidy-devel libxcrypt-compat oniguruma5php oniguruma5php-devel python3-libselinux
    
    php-libs-versionlock: 13 locked packages: GeoIP GeoIP-devel libcap-ng-python3 libicu73 libicu73-devel libmcrypt libmcrypt-devel libtidy libtidy-devel libxcrypt-compat oniguruma5php oniguruma5php-devel python3-libselinux
    
      held: python3-libselinux 3.6-3.el9 -> 3.6-4.el9
    
      run centmin.sh menu option 5 to update held packages and rebuild PHP against them
    


    The script explicitly recommends running Centmin Mod menu option 5 to update the held package and rebuild PHP against the updated dependencies.

    6. Questions

    1. Is running Centmin Mod menu option 5 the officially recommended solution for this particular python3-libselinux conflict?
    2. Is rebuilding PHP really necessary when the only reported held package is python3-libselinux, which comes from AlmaLinux AppStream?
    3. Would it be safe to temporarily remove only the python3-libselinux versionlock, upgrade the related SELinux packages to 3.6-4.el9, and then restore the versionlock? Or could this cause compatibility issues with PHP-FPM?
    4. The script reports "unmarked locks the next menu 5 run adopts". Is that expected behavior with Centmin Mod 132.00stable? Does it mean the locks were created before the newer tracking mechanism was introduced?
    5. Is there a way to update these held libraries using php-libs-versionlock.sh without performing a complete PHP rebuild?
    6. Could this particular versionlock result in future AlmaLinux security updates being blocked, and is there a recommended permanent fix?

    7. Related forum discussions

    I found these potentially related discussions:


    I understand that Centmin Mod intentionally uses versionlocks to protect PHP-FPM from incompatible library updates.

    My preference is to resolve this safely without manually bypassing Centmin Mod's protection mechanisms, and ideally without rebuilding PHP unless it is genuinely necessary.

    No versionlocks have been removed, and no package changes have been made during troubleshooting.

    Any advice on the recommended procedure for Centmin Mod 132.00stable would be greatly appreciated.

    Thanks in advance!
     
    Last edited: Nov 19, 2026 at 10:09 AM
  2. ENF

    ENF SquareEnix (Eng.)

    21
    4
    3
    May 9, 2016
    Tokyo, Japan
    Ratings:
    +13
    Local Time:
    11:44 PM
    Latest
    10.6.x
    I had a client with this issue recently, the only thing that solved it was running the following:
    Code:
    dnf clean all
    dnf --refresh upgrade --assumeno
    
    @eva2000 might have a more specific solution, but this is what we had to do to get things running again.
     
  3. eva2000

    eva2000 Administrator Staff Member

    60,551
    12,627
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,292
    Local Time:
    12:44 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    Thanks for sharing

    This should be fixed now in 132.00stable, 140.00beta01 and 141.00beta01

    run cmupdate and then run centmin.sh menu option 5 to recompile once and it should fix it for future runs