[fix] Hold aquamarine with the pinned Hyprland ABI - #136
Conversation
Omarchy updates were pulling aquamarine 0.15 (libaquamarine.so=14) while IgnorePkg kept the patched Hyprland that still needs .so=13, aborting the transaction. Keep aquamarine on the same hold until the compositor pin moves.
Chessing234
left a comment
There was a problem hiding this comment.
ignorepkg coupling matches the described libaquamarine abi break; test updated.
|
Follow-up: #136 is the right guest update hold, but it does not unblock empty-root factory builds — ALA no longer publishes SONAME 13, so Opened #142 to vendor |
themartiano
left a comment
There was a problem hiding this comment.
Thanks for the pull request!
Codex comments
The guest ABI hold matches #134. CI and the combined merge-result tests passed.
Summary
aquamarine 0.15.0-2(libaquamarine.so=14) whileIgnorePkgkeeps the patched Hyprland that still requireslibaquamarine.so=13.aquamarineto the existing kernel/HyprlandIgnorePkghold and document the ABI coupling.Test plan
python3 guest/tests/verify.py/etc/pacman.conf(via restored/usr/share/try-omarchy/pacman.conf) listsaquamarineonIgnorePkgNote for existing VMs: this lands in new/reset guest images. Already-provisioned disks still have the old baked
pacman.conf; they can addaquamarinetoIgnorePkgin both/usr/share/try-omarchy/pacman.confand/etc/pacman.conf(or reset) until they pick up a new image.