The command transactional-update patch fails with the following message on my OpenSUSE Leap Micro 5.5 machine:
Problem: 1: nothing provides ‘libyaml-0.so.2()(64bit)’ needed by the to be installed python3-PyYAML-5.4.1-150300.3.3.1.x86_64
Solution 1: Following actions will be done:
deinstallation of python3-PyYAML-5.4.1-1.1.x86_64
deinstallation of python3-salt-3006.0-150500.4.41.2.x86_64
deinstallation of aws-cli-1.27.89-150200.30.11.1.noarch
deinstallation of salt-3006.0-150500.4.41.2.x86_64
deinstallation of salt-minion-3006.0-150500.4.41.2.x86_64
deinstallation of salt-transactional-update-3006.0-150500.4.41.2.x86_64
deinstallation of patterns-microos-salt_minion-5.5.1-150500.1.1.x86_64
Solution 2: do not install patch:openSUSE-Leap-Micro-5.5-2024-2912-1.noarch
Solution 3: break python3-PyYAML-5.4.1-150300.3.3.1.x86_64 by ignoring some of its dependencies
My purpose is to upgrade to OpenSUSE Leap Micro 6.0 and the procedure implies to perform the patching of 5.5 before.
Depends how important that system (and its VMs/containers or course) are to you. You could try to find and install an appropriate package from another repository. Micro 6.0 seems to have 6.0.1-1.9 of that package so I guess the update will end up overwriting it anyway. In case it isn’t obvious, I haven’t tried it and it obviously could go wrong (though you should then be able to roll back at least).
Maybe more worrying for you is that there are now three Micro 6.0 patches that fail to apply, two labeled as “security” fixes. The third has just appeared and I see no interest in fixing the other two, so for me the experiment is over and I’ll probably move to Proximox or a hand-rolled Debian Stable installation. Pity - Micro looked to be just what I wanted to replace VMWare ESXi…
For the first failed Micro 6 patch I tried experimentally to get the required QEMU packages from Tumbleweed. This worked, but of course resulted in non-standard hybrid installation so not really an acceptable solution.