Felix Miata composed on 2016-10-27 01:55 (UTC-0400):
On an alpha on host hpg33 last updated (installed?) in July, after zypper ref I tried to zypper up, and it aborted with $SUBJECT message. I got it to update by using the suggested-by-error-message --non-interactive option. Afterward, I tried to zypper dup, but it produces the same result as before the update. rpm --rebuilddb, zypper clean -a and zypper ref didn't help. Searching for $SUBJECT in boo as comment produces no hits in past 11 months. Rebooting seems to have fixed it.
Any ideas what happened, or didn't?
Happened again, but on host gx62b last updated 2 Aug. A little more detail this time: I normally don't just zypper up. Instead, I run the following script first (but after zypper ref): #!/bin/sh zypper -v in zypper libzypp libsolv-tools rpm openSUSE-release zypper -v in device-mapper dmraid glibc lvm2 multipath-tools mdadm systemd udev Running the script before zypper up/dup provides me opportunity to check if /etc/zypp /zypp*conf.rpmnew has appeared or changed so I can see if I want to make any adjustment before proceeding. So when the abort occurred trying to zypper up, unlike on hpg33, I rebooted instead of proceeding directly to up. After, zypper up worked as expected. -- "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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org