openSUSE tumbleweed is a rolling version of openSUSE; meaning the latest packages are just rolling in without having a fixed version stack. Kind of like ArchLinux.
tumbleweed already exists for quite a while now but I never got the time or the need to use it. Due to my change of employer back in April 2015 I decided to use my openSUSE 13.2 VM and upgrade it to tumbleweed. If the upgrade breaks the whole VM I can just trash it.
On https://en.opensuse.org/openSUSE:Tumbleweed_installation there is a very basic guide how to do the upgrade. Well, it doesn't need to be more complicated than that as it's just replacing the repositories with the tumbleweed repos:
suse12-3:~ # mkdir /etc/zypp/repos.d/old
suse12-3:~ # mv /etc/zypp/repos.d/*.repo /etc/zypp/repos.d/old
suse12-3:~ # zypper ar -f -c http://download.opensuse.org/tumbleweed/repo/oss repo-oss
Adding repository 'repo-oss' ...................[done]
Repository 'repo-oss' successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: http://download.opensuse.org/tumbleweed/repo/oss
suse12-3:~ # zypper ar -f -c http://download.opensuse.org/tumbleweed/repo/non-oss/ repo-non-oss
Adding repository 'repo-non-oss' ...............[done]
Repository 'repo-non-oss' successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: http://download.opensuse.org/tumbleweed/repo/non-oss/
suse12-3:~ # zypper ar -f -c http://download.opensuse.org/tumbleweed/repo/debug/ repo-debug
Adding repository 'repo-debug' .................[done]
Repository 'repo-debug' successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: http://download.opensuse.org/tumbleweed/repo/debug/
suse12-3:~ # zypper ar -f -c http://download.opensuse.org/update/tumbleweed/ repo-update
Adding repository 'repo-update' ................[done]
Repository 'repo-update' successfully added
Enabled: Yes
Autorefresh: Yes
GPG check: Yes
URI: http://download.opensuse.org/update/tumbleweed/
suse12-3:~ # zypper lr -u
# | Alias | Name | Enabled | Refresh | URI
--+--------------+--------------+---------+---------+------------------------------------------------------
1 | repo-debug | repo-debug | Yes | Yes | http://download.opensuse.org/tumbleweed/repo/debug/
2 | repo-non-oss | repo-non-oss | Yes | Yes | http://download.opensuse.org/tumbleweed/repo/non-oss/
3 | repo-oss | repo-oss | Yes | Yes | http://download.opensuse.org/tumbleweed/repo/oss
4 | repo-update | repo-update | Yes | Yes | http://download.opensuse.org/update/tumbleweed/
Now that the tumbleweed repos are active, a distribution upgrade (dup) can be launched:
suse12-3:~ # zypper dup
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.
[...]
1671 packages to upgrade, 6 to downgrade, 1013 new, 149 to remove, 20 to change arch.
Overall download size: 1.79 GiB. After the operation, additional 2.6 GiB will be used.
Continue? [y/n/? shows all options] (y): y
[...]
The upgrade started and ran right up until this point:
( 688/2709) Installing: splashy-branding-openSUSE-0.3.13-49.1 .................................. [done]
Additional rpm output:
>Set theme as: openSUSE [ DONE ]
Run mkinitrd to update your initrd image
>Set theme as: default [ DONE ]
Run mkinitrd to update your initrd image
( 689/2709) Installing: systemd-224-1.1 .................................. <100%>[/]
The installation of systemd-224 hang for more than 30 minutes and I couldn't even login on the machine anymore, or even become root:
ckuenzler@suse12-3:~> su -
Password:
su: Module is unknown
I stopped the installation with ctrl-c and I got the following error:
Installation of systemd-224-1.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: nscd: relocation error: nscd: symbol h_errno, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
nscd: relocation error: nscd: symbol h_errno, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
[...]
Scanning scripts ...
Resolve dependencies ...
Install symlinks in /lib/mkinitrd/setup ...
Install symlinks in /lib/mkinitrd/boot ...
warning: %postun(systemd-195-13.45.1.x86_64) scriptlet failed, signal 2
Abort, retry, ignore? [a/r/i] (a):
A retry also didn't help:
Abort, retry, ignore? [a/r/i] (a): r
( 689/2709) Installing: systemd-224-1.1 .................................. <100%>[-]^C
OK OK! Exiting immediately...
After this i was unable to use the machine as I couldn't even start a new shell session anymore. And after a reboot, the machine was completely f*cked up. KDE was gone, no graphics and even a login on the console didn't work anymore. FAIL :-(
No comments yet.
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Containers CouchDB DB DNS Database Databases Docker ELK Elasticsearch Filebeat FreeBSD Galera GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Icingaweb Icingaweb2 Influx Internet Java KVM Kibana Kodi Kubernetes LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Rant Redis Roundcube SSL Samba Seafile Security Shell SmartOS Solaris Surveillance Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder