This bug was initially created as a copy of Bug #2121447 I am copying this bug because: The problem has reappeared with a different symlink Description of problem: There is a broken symlink /usr/lib/firmware/qcom/LENOVO/21BX.xz in the linux-firmware package. The target /usr/lib/firmware/qcom/sc8280xp/LENOVO/21BX.xz does not exist (but there is a /usr/lib/firmware/qcom/sc8280xp/LENOVO/21BX directory). This is annoying, because there is a utility (ReaR) that produces a bootable rescue image (including modules and firmware) and checks whether the content of the image is valid. If it encounters a broken symlink, it complains, because it indicates a potential problem and it will be then seen as false alarm that can ultimately obscure a real problem (see bz2021935). Version-Release number of selected component (if applicable): 20230310-133.el9_2.noarch How reproducible: easily in the default install Steps to Reproduce: 1. file /usr/lib/firmware/qcom/LENOVO/21BX.xz Actual results: /usr/lib/firmware/qcom/LENOVO/21BX.xz: broken symbolic link to ../sc8280xp/LENOVO/21BX.xz Expected results: symlink is readable
scratch build for interested parties: https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=2333761 # ls -la /usr/lib/firmware/qcom/LENOVO/21BX lrwxrwxrwx. 1 root root 23 Jun 13 04:22 /usr/lib/firmware/qcom/LENOVO/21BX -> ../sc8280xp/LENOVO/21BX # diff -u -r orig/usr new/usr Only in new/usr/lib/firmware/qcom/LENOVO: 21BX Only in orig/usr/lib/firmware/qcom/LENOVO: 21BX.xz