Language Selection

English French German Italian Portuguese Spanish

Hitch your wagon to a lizard: dist-upgrading openSUSE

Filed under
Linux

For the first time, openSUSE now officially supports a "dist-upgrade" feature, similar to Debian's. Which is to say, if you've got openSUSE 11.1 installed, you should be able to upgrade to openSUSE 11.2 by updating your list of software repositories to point to providers of software for openSUSE 11.2, doing a distribution upgrade via the Internet, and have a reasonable chance of success.

The stated reasoning behind the addition of this feature seems to focus on competition with Ubuntu. Fine then; although the openSUSE installation media's offered the option of updating rather than installing for a while now, it was always a hit and miss affair; usually more miss than hit, so that doing a clean install was often necessary. (One obvious reason is that the installation media only provides a few software repositories; if you had a whole bunch of online repositories active prior to installation, you probably had software installed that wasn't even on the installation media. Novell also seems to be admitting that its software management tools weren't up to the task until now.)

The easiest way to upgrade from openSUSE 11.1 to 11.2 is via the command line. However, that doesn't make for very exciting screenshots, so I elected to install a YaST module named "wagon" that does the same thing. It failed about halfway through the process, and I had to go back to the command line. If you use "wagon," I hope your results are better than mine! Here's the play-by-play.

(Two things of note: They say that the more repositories you have enabled, the greater the chance that a distribution upgrade won't work. And my screenshots of KDE and GNOME won't look like what you see if you install openSUSE out-of-the-box, since I've re-decorated.)


Step 1: Install "wagon" via YaST.


Step 2: Disable and/or update existing software repositories to their openSUSE 11.2 equivalents.

(This was tedious but mostly meant changing a "1" to a "2" in the repo's URL.)

Existing repository New repository
Gnome:Backports:2.6 (openSUSE v11.1) No v11.2 equivalent. Disable.
Gnome:Stable:2.6 (openSUSE v11.1) Gnome:Stable:2.8 (openSUSE v11.2)
server:monitoring - v11.1 v11.2
Packman - v11.1 v11.2
openSUSE BuildService - Mozilla - v11.1 v11.2
openSUSE BuildService - Virtualization (VirtualBox) - v11.1 v11.2
openSUSE BuildService - KDE:Community - v11.1 v11.2
openSUSE BuildService - KDE:Backports - v11.1 v11.2
openSUSE BuildService - GNOME:STABLE (v11.1) No 11.2 equivalent. Disable.
openSUSE BuildService - GNOME:Community - v11.1 v11.2
NVIDIA repository - v11.1 v11.2
Main Repository (OSS) - v11.1 v11.2
Main Repository (NON-OSS) - v11.1 v11.2
openSUSE BuildService - KDE:Core Packages - v11.1 v11.2
openSUSE-11.1-Updates v11.2
home:ecanuto (Gnome colors icons) - v11.1 Factory
home:cyberorg:experimental (Fusion icon) (v11.1) No v11.2 equivalent. Disable.
Qt 4.5 - v11.1 v11.2
Qt 4.4 - v11.1 v11.2
KDE 4 Playground - 11.1 v11.2
KDE 4 Community - 11.1 v11.2
KDE 4 Core Packages - 11.1 v11.2


Step 3: Run "wagon." (Alt+F2 brings up the "run" dialog box in KDE. Command: "kdesu -c yast2 wagon")


Step 4: Follow the prompts.


Fixing dependency errors.


Updating zypper and friends.

Step 5: At this point, the problems started: windows with nothing in them. After several full-sized blank windows came up, another one came up that I couldn't close. I finally used xkill on "wagon".


Step 6: At this point I gave up on "wagon," started up a Konsole session, and used the "zypper dup" command. After answering a few dependency solver questions and accepting the openSUSE license, it was a matter of sitting back and waiting...


Step 7: I'm not sure how long the upgrade took (had to catch some zzzZZZ's) but it was over 3 hours. The only steps left to do were to run the "SuSEconfig" command and reboot.


KDE 4.3.1


GNOME 2.28


KDE 3.5.10

The only thing I had to do afterwards was to use YaST's "/etc/sysconfig Editor" to change the session manager from "kdm" to "kdm4". Apparently openSUSE 11.1 used a KDE 3-based login manager, and so I got an ugly login screen upon reboot. The only thing that's broken is PulseAudio, GNOME's sound server, which is now often belching static when changing the volume level or playing system sounds. Otherwise, everything seems to work OK. Good job, Novell.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Umm

They actually refer to "Debian/Ubuntu" in terms of compatibility. No just Ubuntu.

Also, the feature of being able to do said upgrade is a feature made prominent and possible by APT. Which is the mainstay package management core tool in Debian, and consequently Ubuntu.

Because Opensuse uses zypper and not APT was one of the main reasons they could not offer said compatibility.

other rpm based distros do offer an online update/upgrade capability, such as PCLOS, because they use a tool like (in PCLOS's case, APT4rpm).

Up until recently, zypper did not have this functionality built into it.

Big Bear

Interesting

OpenSUSE is trying to copy Ubuntu. Apt is like Zypper in a sense, that it manages packages and that is the type of functionality that OpenSUSE wishes they could have. That is why Slackware is built in with prominent reasons of use, like PCLOS did first. I hope that OpenSUSE can catch up to Debian in this sense.

More in Tux Machines

Android Leftovers

Intel Core i9 9900K vs. AMD Ryzen 7 2700X Linux Gaming Benchmarks

Complementing the just-published Intel Core i9 9900K Linux benchmarks with the launch-day embargo lift are the Linux gaming benchmarks... This article is looking at the Linux performance between the Core i9 9900K and AMD's Ryzen 7 2700X in a variety of native Linux games as well as comparing the performance-per-Watt. So if you are a Linux gamer and deciding between these sub-$500 processors, this article is for you. If you didn't yet read the main article that features a 15-way CPU comparison on Ubuntu 18.10 with the Linux 4.19 kernel, here is a recap of this new Coffeelake refresh CPU. The Core i9 9900K is an eight-core / sixteen-thread processor with 3.6GHz base frequency and 5.0GHz turbo frequency. This 14nm CPU has a 16MB L3 cache, dual channel DDR4-2666 support, and a 95 Watt TDP. There is also the onboard UHD Graphics 630, but if you're a gamer, that isn't going to cut it. The Core i9 9900K is launching at $499 USD. Read more

Intel Core i9 9900K Linux Benchmarks - 15-Way Intel/AMD Comparison On Ubuntu 18.10

Intel sent over the Core i9 9900K as their first 9th Gen Coffeelake-S CPU hitting store shelves today. With the embargo on that now expired, let's have a look at how well this eight-core / sixteen-thread processor performs under Linux. The Core i9 9900K is Intel's new answer for competing with the likes of the AMD Ryzen 7 2700X, but does come at a higher price point of $499 USD. While the Core i9 9900K is a Coffeelake refresh, rather than being six cores / twelve threads, they are matching AMD's precedent set by the Ryzen 7 processors in having eight cores / sixteen threads. This 14nm 8C / 16T processor has a base clock frequency of 3.6GHz with a turbo frequency at 5.0GHz, a 16MB L3 cache and supports dual-channel DDR4-2666 memory. Read more

Google: Desktop, Server and Kernel

  • Chrome OS Linux support to gain folder sharing, Google Drive, more
    Chrome OS has been shaping up to be the all-in-one system, combining the best of Google’s ecosystem, including Android apps, with the power of Linux apps. The latter is still in beta phase with improvements and new features in every update. Today we take a look at some of the features coming soon to Chrome OS Linux apps. Chrome OS first gained its Linux app support, also known as Crostini, with version 69. While it’s certainly not flawless, the support has been groundbreaking, enabling everything from full photo editors to Android Studio on Chrome OS. With upcoming versions of Chrome OS, Google is working to smoothen the rough edges of Crostini to make it easier to use.
  • Google Cloud CTO Brian Stevens on using open source for competitive advantage in the public cloud
    As all three continue to vie for the affections of CIOs, how they market their respective public cloud propositions to enterprise IT buyers has subtly shifted over time. For evidence of this, one only has to look at how little fuss the big three now make about rolling out price cuts for their services compared to several years ago, when one provider announcing a price drop would not only make headlines, but prompt its competitors to publicly follow suit too. This in itself is indicative of the fact enterprises expect more from providers than just access to cheap commodity IT services these days, and that ongoing cost reductions are simply an accepted part of using cloud, Google Cloud CTO Brian Stevens, tells Computer Weekly.
  • KUnit: A new unit testing framework for Linux Kernel
    On Tuesday, Google engineer Brendan Higgins announced an experimental set of 31 patches by introducing KUnit as a new Linux kernel unit testing framework to help preserve and improve the quality of the kernel’s code. KUnit is a lightweight unit testing and mocking framework designed for the Linux kernel. Unit tests necessarily have finer granularity, they are able to test all code paths easily solving the classic problem of difficulty in exercising error handling code.