Am 08.08.19 um 20:57 schrieb Roger Oberholtzer:
On Thu, Aug 8, 2019 at 8:44 PM Simon Becherer <simon@becherer.de> wrote:
and make sure you do not have a installation CD still enabled in the list. sometimes if i had problems with zypper, i stay on the old version of the problematic dependency and use yast later on the problematic pieces to update it. i have had situations where it then would update in yast (after a zypper dup with problems) without problems (all resolved automatically).
The ISO/CD is disabled and not in the computer.
What worries me is that if zypper gets messed up, things surely will go bad. zypper-migration-plugin seems like something one does not want to take chances with.
An up-to-date (within a week) Tumbleweed has these zypper-named packages:
zypper-aptitude-1.14.28-1.2.noarch zypper-log-1.14.28-1.2.noarch zypper-needs-restarting-1.14.28-1.2.noarch zypper-lifecycle-plugin-0.6.1490613702.a925823-2.9.noarch zypper-1.14.28-1.2.x86_64
Maybe zypper-migration-plugin is no longer needed? Or perhaps it needs to do some migration stuff first?
sorry no good idea, but maybe (if you use the tumbleweed cli) try to set to another target and check if it updates there. tumbleweed list 20190806 20190805 20190730 20190726 20190724 20190723 20190721 20190718 20190717 20190716 20190713 20190708 20190704 20190703 20190702 20190701 20190630 20190628 20190627 20190626 on my systems 20190607 zypper-migration-plugin is installed. i will update maybe next week so if its a problem, i will run (maybe) into it also.... if you find a solution, .... :-)) simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org