Learn about Centmin Mod LEMP Stack today
Become a Member

Stable Branch fix php-libs-versionlock.sh leaving aom unlocked beside a locked liba…

Discussion in 'Centmin Mod Github Commits' started by eva2000, Nov 19, 2026 at 6:02 PM.

  1. 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+
    fix php-libs-versionlock.sh leaving aom unlocked beside a locked libaom in 132.00stable

    EPEL builds aom, libaom and libaom-devel from one source rpm, and aom requires
    its exact libaom version. libaom-devel 3.13.3+ requires aom, so a menu 5 library
    update could pull aom in, and the update step only relocked the packages already
    locked. When the PHP build then failed before the post-build lock, aom stayed
    unlocked beside a locked libaom, and a plain yum update failed with "aom requires
    libaom = <ver> ... filtered out by exclude filtering".

    Changes:
    - update now also updates and locks installed subpackages built from the same
    source rpm as a locked package (with_siblings), before and after dnf update
    - update and lock share one repo origin filter (non_base); siblings installed
    from local rpm files or OS repos stay unlocked as before
    - no bare dnf update when no locked package is still installed
    - if the update removed every locked package, keep the previous locks and fail;
    if it removed some, warn and drop their locks
    - if the sibling check fails after dnf update, warn with the lock command to run
    - packages without a source rpm (gpg-pubkey) are never treated as siblings
    - same tool file as 141.00beta01

    Continue reading...


    132.00stable branch