- Rpm has traditionally (at least for the last decade) preserved
existing %ghost %config file on erasure. Whether this was intentional
or not, changing the behavior now risks data loss in case people
are relying on this long-standing behavior.
- This fails now: The behavior changed as (an unexpected) side-effect
of commit
389b1ab706be8eddba9f00c7084759f670ce96ac.
(cherry picked from commit
4efec66338ef04d2f1ed20cfba84c47145269d0d)
runroot rpm -U "${TOPDIR}"/RPMS/noarch/configtest-1.0-1.noarch.rpm
cat "${cf}"
runroot rpm -e configtest
-test ! -f "${cf}" && echo OK1
+cat "${cf}"
+rm -f "${cf}"
# post-install config, upgrade, erase
runroot rpm -U "${TOPDIR}"/RPMS/noarch/configtest-1.0-1.noarch.rpm
runroot rpm -U "${TOPDIR}"/RPMS/noarch/configtest-2.0-1.noarch.rpm
cat "${cf}"
runroot rpm -e configtest
-test ! -f "${cf}" && echo OK2
+cat "${cf}"
],
[],
[OK1
keaton
keaton
-OK1
+keaton
OK2
buster
buster
-OK2
+buster
],
[])
AT_CLEANUP