• 2 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: February 18th, 2025

help-circle





  • I would start by grepping /var/log/zypper.log for aborted or posttrans, seeing where the previous installation failed to run the post transaction hook. Then check the timestamp and see if it makes more sense what happened.

    I don’t use opensuse, or zypper, (arch btw) so I’m sorry I can’t give more detailed help.

    The good news is I’ve seen multiple broken Ubuntu/Debian/etc systems from aborted upgrades too. So I don’t think your situation is unique to your distro. It’s more about learning what you system is actually doing when you update and how catch when something has gone wrong.



  • I’m not 100% sure because I don’t use that package manager, but from the looks of it what happened was:

    • you ran an upgrade that failed or you aborted an upgrade
    • that update added a new selinux policy
    • because it failed/aborted it didn’t run the post-transaction hooks that reload your selinux policies
    • you ran the upgrade that you posted about
    • this upgrade failed because it relies on the selinux policy that didn’t get loaded