Removal can be done in %pre or %post of the new package. In node, I choose %post since I'm not installing anything in place of the update-alternative symlink. For packages that replace the update-alternatives symlink with one to alts, they probably would call update-alternatives --remove in %pre Yes, that could really becomes tricky. While updating packages to

https://bugzilla.suse.com/show_bug.cgi?id=1187037 https://bugzilla.suse.com/show_bug.cgi?id=1187037#c17 --- Comment #17 from Stefan Schubert <schubi@suse.com> --- (In reply to Adam Majer from comment #3) libalternatives I have had two cases where the call in %post has "crashed" the package and I have had to move it to the %pre install script. It seems the even origin update-alternatives does not check where e.g. a binary comes from and if it is a link of update-alternatives only. The question is how to tell the package maintainer that he should be careful here ? -- You are receiving this mail because: You are on the CC list for the bug.