Comment # 1 on bug 1218459 from Dirk Weber

Comparing with the second system:
the files started to appear or rather remain leftover with the snapshot update
following the snapshot which contained the update of libzypp to version
17.31.22-2.1 on the respective system.

This version of libzypp was part of snapshot 20231012.


The announcement 
"New Tumbleweed snapshot 20231012 released!"
mentioned these changes:

==== libzypp ====
Version update (17.31.20 -> 17.31.22)

- Preliminary disable 'rpm --runposttrans' usage for chrooted
  systems (bsc#1216091)
  This limits the %transfiletrigger(postun|in) support in the
  default installer iff --root is used (as described in bug
  1041742). The chrooted execution of the scripts in 'rpm
  - -runposttrans' broke in rpm-4.18. It's expected to be fixed in
  rpm-4.19. Then we'll enable the feature again.
- fix comment typo on zypp.conf (boo#1215979)
- version 17.31.22 (22)
- Attempt to delay %transfiletrigger(postun|in) execution if rpm
  supports it (bsc#1041742)
  Decide during installation whether rpm is capable of delayed
  %posttrans %transfiletrigger(postun|in) execution or whether we
  can just handle the packages %posttrans. On TW a delayed
  %transfiletrigger handling is possible since rpm-4.17.
- Make sure the old target is deleted before a new one is created
  (bsc#1203760)
- version 17.31.21 (22)