When %posttrans scripts are skipped because zypper had unknown failure requiring abort to be selected, do they need to be brought to life? # 2017-05-13 02:33:44 %posttrans scripts skipped while aborting: # coreutils-8.27-1.1.x86_64.rpm # kbd-2.0.3-4.1.x86_64.rpm # blog-2.18-4.1.x86_64.rpm # ucode-amd-20170422-1.1.noarch.rpm # kernel-firmware-20170422-1.1.noarch.rpm # cryptsetup-1.7.5-1.1.x86_64.rpm # dbus-1-1.10.18-1.1.x86_64.rpm # man-2.7.6-3.1.x86_64.rpm # xterm-327-2.1.x86_64.rpm # python2-CherryPy-10.2.1-1.1.noarch.rpm # cups-2.1.3-5.1.x86_64.rpm # adwaita-icon-theme-3.24.0-1.1.noarch.rpm The were unknown because something scrambled the vtty3 output while zypper was running, so I had no idea why the stoppage, and could barely make out the abort, retry, ignore from the Y/N included. When I restarted zypper, there were only 24 packages left to do, and I saw no subsequent zypper output suggesting those skipped were picked up on the restart. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org