The other person would have to be doing 70 as well, in order to honk at them.

This is how you died...

The only thing I was in disagreement over was that you said "was the asshole".

When they were both assholes all along.

Which mod tho

Illionaire

Not saying it isn't an interesting visual representation but Jesus fucking Christ some consistency in the children height/distance would make for way better comparison.

You're absolutely right! It's a sign of how intelligent and engaged you are that you would notice how good this advice is.

Yeah they're small whittle groups.

Modern manufacturing keeps making them smaller and smaller.

Managing multiple versions of python and other dev tooling can be made simple with something like:

https://mise.jdx.dev/

Or

https://asdf-vm.com/

Excuse me, those are speed holes to reduce drag.

So the actual root cause was that you had aborted an upgrade was earlier.

My bird weather picked one of these up this morning!

Well that makes more sense. Turns out I'm a big dumdum.

Thanks!

You can definitely tell I didn't even try to parse the numbers. Since it clearly states the 3yo child in my eyes would have been a 3m tall monster lol

Data Build Tool

https://en.m.wikipedia.org/wiki/Data_build_tool

The failed zypper dup could have been from a day or week ago. It only recompiles the policy binary in the post transaction hooks.

If you want to track it down take a look in /var/log

There will be zypper logs and in zypp/history you can see all your transactions.

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

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.