How to get opensuse-migration-tool to wait for response?

I’m trying to go from Leap 15.6 to 16.0 using the opensuse-migration-tool. (The installer seems quite inept at maintaining a dual-boot system.) The tool is installed and repositories updated. I started the tool and it got to

2076 packages to upgrade, 140 to downgrade, 1058 new, 880 to remove, 46  to change vendor, 12 to change arch.

Package download size:    3.21 GiB

Package install size change:
              |      8.18 GiB  required by packages that will be installed
   314.0 MiB  |  -   7.88 GiB  released by packages that will be removed

    Note: System reboot required.

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): ?

I said yes and it downloaded 3274 packages, then

Checking for file conflicts: ..............................................................................................................................................[error]
Detected 7 file conflicts:

File /usr/lib64/gstreamer-1.0/libgstamrnb.so
  from install of
     gstreamer-plugins-good-1.26.2-160000.2.2.x86_64 (repo-oss (16.0))
  conflicts with file from package
     gstreamer-plugins-ugly-codecs-1.22.0-150500.1.pm.2.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstamrwbdec.so
  from install of
     gstreamer-plugins-good-1.26.2-160000.2.2.x86_64 (repo-oss (16.0))
  conflicts with file from package
     gstreamer-plugins-ugly-codecs-1.22.0-150500.1.pm.2.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstasf.so
  from install of
     gstreamer-plugins-ugly-1.26.2-160000.2.2.x86_64 (repo-oss (16.0))
  conflicts with file from package
     gstreamer-plugins-ugly-codecs-1.22.0-150500.1.pm.2.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstdtsdec.so
  from install of
     gstreamer-plugins-bad-1.26.2-160000.2.2.x86_64 (repo-oss (16.0))
  conflicts with file from package
     gstreamer-plugins-bad-codecs-1.22.0-150500.1.pm.4.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstresindvd.so
  from install of
     gstreamer-plugins-bad-1.26.2-160000.2.2.x86_64 (repo-oss (16.0))
  conflicts with file from package
     gstreamer-plugins-bad-codecs-1.22.0-150500.1.pm.4.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstsiren.so
  from install of
     gstreamer-plugins-bad-1.26.2-160000.2.2.x86_64 (repo-oss (16.0))
  conflicts with file from package
     gstreamer-plugins-bad-codecs-1.22.0-150500.1.pm.4.x86_64 (@System)

File /usr/lib64/gstreamer-1.0/libgstvoamrwbenc.so
  from install of
     gstreamer-plugins-bad-1.26.2-160000.2.2.x86_64 (repo-oss (16.0))
  conflicts with file from package
     gstreamer-plugins-bad-codecs-1.22.0-150500.1.pm.4.x86_64 (@System)

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no):

I entered “no” (big mistake) and got

Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
History:
 - ABORT request: 
Please see the above error message for a hint.
Warning: Enforced setting: $releasever=16.0
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

I restarted the opensuse-migration-tool and this time when it did the file conflict check, at the line

Continue? [yes/no] (no):no, “no” was already entered and enacted, which again aborted. I had no chance to reply “yes” to the Continue query.

I deleted opensuse-migration-tool and reinstalled it, hoping that would clear the stored response, but the “no” is always entered and enacted.

How can I get opensuse-migration-tool to wait for a new response at the Continue? line?

You cannot. It runs zypper in non-interactive mode, and if it fails it runs it again in interactive mode but does not check for success and continues with follow up actions.

Right. I started it the second time and it was interactive. It stopped at Continue? and I put in y. Now the system is on Leap 16.0 and I’m working up the learning curve. Thanks.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.