Comment # 3 on bug 1208963 from Santiago Zarate

(In reply to Andreas Stieger from comment #2)
> and it just landed in a snapshot. message no longer appears after 2nd
> update, the postun of the previous package still triggers. I think this can
> be closed.


Nope, on one of my systems:

> The following 58 packages are going to be upgraded:
>  MicroOS-release MicroOS-release-appliance branding-openSUSE btrfsprogs btrfsprogs-udev-rules checkpolicy elfutils ethtool grep grub2 grub2-branding-openSUSE grub2-i386-pc grub2-i386-pc-extras grub2-snapper-plugin grub2-x86_64-efi grub2-x86_64-efi-extras iproute2 kdump krb5 libasm1 libblkid1 libbrotlicommon1 libbrotlidec1 libbtrfs0 libbtrfsutil1 libdw1 libelf1 libfdisk1 libhugetlbfs liblz4-1 libmount1 libpython3_10-1_0 libselinux1 libsemanage-conf libsemanage2 libsepol2 libsmartcols1 libsystemd0 libudev1 libuuid1 policycoreutils policycoreutils-python-utils python3-policycoreutils python3-selinux python310 python310-base python310-semanage selinux-policy selinux-policy-targeted selinux-tools systemd timezone udev util-linux util-linux-systemd vim-data-common vim-small yast2-logs

> The following product is going to be upgraded:
> openSUSE MicroOS
>   20230304-0 -> 20230309-0
>
> ...
>
> Mar 09 01:18:06 ninlil transactional-update[7595]: /sbin/ldconfig: relative path `1' used to build cache
> Mar 09 01:18:06 ninlil transactional-update[7595]: warning: %postun(libfdisk1-2.38.1-7.1.x86_64) scriptlet failed, exit status 1
> Mar 09 01:18:06 ninlil transactional-update[7595]: done]