That's a 5.25" floppy. Back when they were actually a bit floppy. Before that there was an 8" floppy.
Next to it is the 3.5" floppy that came much later.
5.25" were square, so maybe you're referring to the VHS that comes after the 3.5" floppy?
Edit: I should continue reading before replying.
Yeah they're small whittle groups.
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
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 might be thinking of the Meese on Isle Royale: https://en.wikipedia.org/wiki/Wolves_and_moose_on_Isle_Royale
..and if not it's still a fun read.
My bird weather picked one of these up this morning!
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.
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:
So the actual root cause was that you had aborted an upgrade was earlier.
Caught the little guy resting last August.
