Can't upgrade openSUSE 42.3 to Leap 15

File /usr/lib/python2.7/site-packages/six-1.11.0-py2.7.egg-info
  from install of
     python2-six-1.11.0-lp150.2.3.noarch (Main Repository (OSS))
  conflicts with file from package
     python-six-1.11.0-9.4.1.noarch (@System)

File /usr/lib/python2.7/site-packages/six.py
  from install of
     python2-six-1.11.0-lp150.2.3.noarch (Main Repository (OSS))
  conflicts with file from package
     python-six-1.11.0-9.4.1.noarch (@System)

File /usr/lib/python2.7/site-packages/six.pyc
  from install of
     python2-six-1.11.0-lp150.2.3.noarch (Main Repository (OSS))
  conflicts with file from package
     python-six-1.11.0-9.4.1.noarch (@System)

File /usr/lib/python2.7/site-packages/six.pyo
  from install of
     python2-six-1.11.0-lp150.2.3.noarch (Main Repository (OSS))
  conflicts with file from package
     python-six-1.11.0-9.4.1.noarch (@System)

File /usr/share/doc/packages/kernel-syms/README.SUSE
  from install of
     kernel-syms-4.12.14-lp150.12.45.1.x86_64 (Main Update Repository)
  conflicts with file from package
     kernel-syms-4.4.143-65.1.x86_64 (@System)

File /usr/share/doc/packages/kernel-syms/README.SUSE
  from install of
     kernel-syms-4.12.14-lp150.12.45.1.x86_64 (Main Update Repository)
  conflicts with file from package
     kernel-syms-4.4.165-81.1.x86_64 (@System)

Any idea pls ?

@boycottsystemd:

My method to figure out how to resolve such issues is to use the following:

  • rpm --query --whatprovides «Directory or file to be associated with a package»
  • zypper search --installed-only «partial package name»
  • zypper info «package name»
  • zypper repos --uri | grep -i ‘«Repository name»’

 > rpm --query --whatprovides /usr/lib/python2.7/site-packages/
python-talloc-32bit-2.1.11-lp150.2.3.1.x86_64
python-base-2.7.14-lp150.6.3.1.x86_64
 > 
 > zypper search --installed-only python-base
Loading repository data...
Reading installed packages...

S  | Name        | Summary                         | Type
---+-------------+---------------------------------+--------
i+ | python-base | Python Interpreter base package | package
 > 
 > zypper info python-base
Loading repository data...
Reading installed packages...


Information for package python-base:
------------------------------------
Repository     : Hauptaktualisierungs-Repository
Name           : python-base
Version        : 2.7.14-lp150.6.3.1
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 23.2 MiB
Installed      : Yes
Status         : up-to-date
Source package : python-base-2.7.14-lp150.6.3.1.src
Summary        : Python Interpreter base package
Description    :
    Python is an interpreted, object-oriented programming language, and is
    often compared to Tcl, Perl, Scheme, or Java.  You can find an overview
    of Python in the documentation and tutorials included in the python-doc
    (HTML) or python-doc-pdf (PDF) packages.

    This package contains all of stand-alone Python files, minus binary
    modules that would pull in extra dependencies.

 > 
 > zypper repos --uri | grep -i 'Hauptaktualisierungs-Repository'
11 | download.opensuse.org-oss_4       | Hauptaktualisierungs-Repository                         | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/leap/15.0/oss
 > 

Your issue is possibly the Repositories you’re using.

  • Check the output of “zypper repos --uri”.
  • Clean up (i.e. delete) any conflicting repositories you happen to have defined; «You may have to use the graphical YaST Software “Versions” tab to inspect which Repositories have been defined» …

Please check all the steps in the following openSUSE Upgrade “How-To” Wiki articles:

There’s also the following openSUSE documentation: <https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/cha.update.osuse.html>.
Please note that, your Repository names will possibly not be the German language ones …

Others may balk at this suggestion, but I don’t remember it ever causing me any trouble beyond the typing involved:

rpm -e --nodeps each of the currently installed packages that cause a reported conflict, then proceed with zypper dup.

It hasn’t happened often, probably because I don’t use very many optional repos, and when I do, the need, except for Packman, is usually only short term.

Please show outout of


zypper lr -d

When I upgraded 42.3 to 15.0 (experimentally in a VM) a few months ago, I got several conflicts. They were all due to packages from packman. I was upgrading using the DVD which did not have packman. I went with the suggested solution (switch to the opensuse repos) and the upgrade went fine.

You have not indicated whether you were upgrading with DVD, or you were upgrading online with “zypper dup”. And if the latter, please indicate what you did with repos before using “zypper dup”.

Hello,

Thank for replies. I followed instruction on https://en.opensuse.org/SDB:System_upgrade

Unfortunately, Xorg crashed during ‘zypper dup’ so upgrade has been halted (and I could not read your replies). I’ve re-run upgrade in TTY. It has finished but with errors:

...
removing filesystem
warning: directory /sys: remove failed: Device or resource busy.
...
Problem occured during or after installation or removal of packages:
Failed to cache rpm database (129)

grub.cfg is missing. I tried boot opensuse from other distros’s grub:

<too fast to read messages>
...
 OK ] Stopped ...
 OK ] Stopped ...
 OK ] Stopped ...
...
...
 OK ] Reached target Switch root.
Started switch root...
systemd-journald: Received SIGTERM from PID 1 (systemd)

sh-4.4 #
sh-4.4 # rpm -i <somepackage>
sh-4.4 # error: can't create transaction lock on /var/lib/rpm/.rpm.lock (read only filesystem)
sh-4.4 #

Is it please possible to read logs ?
journalctl and dmesg command was not found.

That URL has this very important instruction that you apparently ignored:

Warning: It is strongly recommended that you run the upgrade outside the X-window graphical mode. Thus it is recommended you run the command from either runlevel 3 (text + network), or a virtual console.

Your installation might be repairable via a boot from installation media to first perform the /sys/ removal, then reinstall grub. You can also read the journal with it either directly after having chrooted, or indirectly using the -D or --directory= option.

42.3 is booting fine now. It’s without Xorg and network. Is DVD offline upgrade using https://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64.iso best option now ?

I can’t think of any better one.

https://en.opensuse.org/SDB:Offline_upgrade
*The supported starting point is an openSUSE release with all current updates applied.

*Can this be done or verify need for it using openSUSE-Leap-15.0-DVD-x86_64.iso ?

I’m not sure that I understand the question.

Yes, you should be able to do an offline update using the Leap 15.0 release DVD.

There are some catches to watch for. Check the release notes before you start.

As best I can recall, the main catches are:

  • if you were using legacy grub (sometimes called grub1), the upgrade may break booting. In that case, best to switch to grub2 before attempting the upgrade.
  • if using encrypted partitions, the upgrade can cause problems. If you make sure that all “/etc/crypttab” entries use UUID to reference the partitions, and “/etc/fstab” used UUID of the encrypted file systems for mounting, then all should be fine.

Thank you. In other words, how can I make sure that openSUSE 42.3 has all current updates applied ? There is no network.

If you upgrade with the DVD you will have a mostly up-to-date system. There might be a few old packages left, if the DVD does not contain an update. But many of those will be removed by the update due to conflicts (and you are asked what to do about conflicts).

If you don’t have a network connection, you just do the best that you can.

Excuse me I should have written that I didn’t have network support in openSUSE 42.3. I have it now and I need to connect to wifi using command line tools. Is there please any Howto ?

There are a couple of command line tools – “nmcli” and “nmtui”.

I have used “nmcli”, though not to setup a connection. It’s not easy to use. There should be a man page.

I have never used “nmtui”, but I believe it to be a ncurses application that should be easier to use (compared to “nmcli”). Maybe give it a try.

Note: “nmcli” – NetworkManager Command Line Interface
and: “nmtui” – NetworkManager Terminal User Interface

Thank you. Using nmcli is simple:

nmcli device wifi connect your_SSID_or_BSSID password your_wifi_password  private yes 

If you’re very brave, you could take a look at “systemd-networkd” (man 8) and, especially (5) “systemd.network” – there’s a mention of “wlp3s0” for WLAN configuration …

There’s a Forums discussion here: <et0 not (auto) enabled at boot time, no static ip addresses are assigned - Network/Internet - openSUSE Forums.
It seems that, this systemd method to enable network interfaces is fast – about 20 ms, against Network Manager needing about 100 ms …

Thank you, I prefer to avoid Lemart Potering’s software as much as possible.

Is there any way to make total boot time of any OS with systemd shorter ? It is tens of seconds (in best case) longer than boot time of Devuan for example.

Removing the systemd issue for the moment – fast boots/resets: <https://docs.blackfin.uclinux.org/doku.php?id=fast_boot_example&gt;.

  • Mostly, less than 1 s – best in class: 421 ms.

Interesting, thank you.