* Ken Schneider - openSUSE <suse-list3@bout-tyme.net> [08-09-19 18:04]:
On 8/8/19 3:20 PM, Simon Becherer wrote:
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?
I highly, highly recommend updating zypper and it's dependencies first. Then run... zypper -v dup --dry-run (to test if the dup will actually first then run...) zypper -v dup -d
run a second or third time until all packages have been downloaded. Once all package updates are downloaded then proceed with the actual DUP.
zypper -v ref ; zypper -v dup --no-r --no-allow-v -d && zypper -v dup --no-r --no-allow-v -y -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org