Patches are marked as broken in YaST2 Online Update
This document (3132147) is provided subject to the disclaimer at the end of this document.
Novell SUSE Linux Enterprise Server 10 Service Pack 1
Novell SUSE Linux Enterprise Desktop 10 Service Pack 1
This can have two causes: the first one is due to a user interaction regarding changing package versions, the second one is mainly due to a shortcoming in the way how YaST/ZYPP metadata is handled.
Case 1)The dependencies of a patch got broken. This can be the case if the administrator of the system has manually downgraded required packages to an older version, and the downgraded version does not fulfill the requirements for the patch.
A patch consists of dependencies to packages in specific versions (or, rather, versions >= a specific version). As long as those versions of those packages are installed, the patch is "satisfied". If one of those packages get downgraded (e.g. via "rpm --force mypkg" with an older version), those dependencies are no longer satisfied, and the patch is displayed as "broken".
Dependencies can furthermore get broken when overriding dependency resolver complaints during software installation in YaST.
YaST/ZYPP metadata is missing after a certain software/update catalog is removed.Installing a patch saves the patch meta data below /var/lib/zypp/db/patches. However, the amount of data saved is not sufficient to reconstruct the complete patch information. Therefore, after a certain update catalog is removed, some metadata of already-installed patches is missing. However, the affected patches are installed correctly.
Opposite to case 1, typically the patch description field in YaST is empty, also the package name field is empty.
Only SLES/SLED 10 systems that have been updated to Service Pack 1 are affected by this issue. It is planned to resolve the problem in upcoming Service Pack 2.
resolution for case 1)If the older package versions are to be kept, it would make sense to delete the patch meta data (rightclick on the patch, then"delete"). This will not change any packages, it will only delete the patch meta data -- the dependencies to the newer package versions.
If the system is to remain on that patch level, the package versions should be updated to at least the versions required by the patch. This can simply be done by doing a rightclick on the patch, then "update").
resolution for case 2)Since this is mainly a cosmetical issue, you can safely remove the patches from the list (rightclick on the patch, then"delete").
If deleting the patch does not work in YaST2, it is also possible to delete the patch file in the /var/lib/zypp/db/patches directory.
- In the patches window in YaST, there's a row for the name of the patch, a summary, the category, and finally the version of the patch, e.g. 2994-0. Bear the version of the patch which you want to remove in mind.
- In a root shell, change to the /var/lib/zypp/db/patches directory:
# cd /var/lib/zypp/db/patches
- Search for the file that has the version of the patch, e.g. by performing the following command:
# grep -l 2994-0 *
- Remove the patch file by moving it to an other location, e.g.
# mv 187f15debb97f48d0ac34fab36262159 /tmp/
- Do this for every patch you want to remove from YaST Online Update.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3132147
- Creation Date:18-JAN-08
- Modified Date:27-APR-12
- SUSESUSE Linux Enterprise DesktopSUSE Linux Enterprise Server
Did this document solve your problem? Provide Feedback< Back to Support Search