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

Security News

Red Hat and Fedora

Technical
  • Red Hat Takes OpenShift Dedicated to Google Cloud Platform
    Red Hat has steadily taken significant steps in the cloud computing arena, expanding the focus of its OpenShift open source Platform-as-a-Service hybrid cloud computing offering, including launching a cloud-hosted commercial edition called OpenShift Online. Now, the company has announced the availability of OpenShift Dedicated on Google Cloud Platform. The new offering brings Red Hat’s container platform as a managed service offering to enterprise customers who want to build, launch, and manage applications on OpenShift Dedicated with Google Cloud Platform as their underlying cloud infrastructure. With the availability of OpenShift Dedicated on Google Cloud Platform, users can speed adoption of containers, Kubernetes, and cloud-native application patterns, according to Red Hat. Users also get access to Google’s global, container-optimized infrastructure and can more easily augment their applications with Google’s ecosystem of data analytics, machine learning, compute, network, and storage services.
  • Red Hat Launches OpenShift Dedicated on Google Cloud Platform
    Red Hat, Inc. (NYSE: RHT), the world's leading provider of open source solutions, today announced the general availability of OpenShift Dedicated on Google Cloud Platform. The new offering brings Red Hat’s award-winning container platform as a managed service offering to enterprise customers who want to build, launch, and manage applications on OpenShift Dedicated with Google Cloud Platform as their underlying cloud infrastructure. With the availability of OpenShift Dedicated on Google Cloud Platform, users can speed adoption of containers, Kubernetes, and cloud-native application patterns, benefiting from Red Hat’s deep enterprise experience. Users also benefit from Google’s global, container-optimized infrastructure and can more easily augment their applications with Google’s ecosystem of data analytics, machine learning, compute, network, and storage services.
  • Image Gallery: Synnex Cloud Catalyst Conference Featuring Red Hat, XMedius, Plantronics
Financial Fedora/Community
  • Fedora 23 End of Life
    With the recent release of Fedora 25, Fedora 23 will officially enter End Of Life (EOL) status on December 20th, 2016. After December 20th, all packages in the Fedora 23 repositories will no longer receive security, bugfix, or enhancement updates, and no new packages will be added to the Fedora 23 collection. Upgrading to Fedora 24 or Fedora 25 before December 20th 2016 is highly recommended for all users still running Fedora 23.
  • What Is Wayland and What Does It Means for Linux Users
    Fedora 25 is now out. People are buzzing, as the team have decided to make Wayland the default graphical session going forward. For many Linux users Wayland is a new term that has popped up, but one that they do not understand. In this article we’ll briefly go over what Wayland is, what it does, and why developers are flocking to it in droves! What exactly is Wayland? Let’s find out!
  • Korora 25 is Ready
    The Korora Project has released version 25 (codename "Gurgle") which is now available for download. As usual, you can find a list of already known problems at the common F25 bugs page.
  • Fedora Design Interns Update
  • Holiday Break 2016.
    It’s sad I don’t get more time to post here these days. Being a manager is a pretty busy job, although I have no complaints! It’s enjoyable, and fortunately I have one of the best teams imaginable to work with, the Fedora Engineering team.

openSUSE Says Goodbye to AMD/ATI Catalyst (fglrx) Proprietary Graphics Drivers

openSUSE developer Bruno Friedmann, informed the community of the openSUSE Linux operating system about the fact that he's planning to remove the old ATI/AMD Catalyst (also known as fglrx) proprietary graphics drivers. Read more

Maximizing the benefits of open source in IoT

With the dawn of the Internet of Things, software is making its way into every product, into every industry. And along with software come developers, who bring their beliefs, attitudes, expertise, and habits along with them. One of those is open source technology — a staple in the software industry since the 1980s, but a new and often scary concept for many traditional industries, whose businesses are built on protecting their assets and intellectual property. In this article, we will illustrate how open source technologies permeate every part of the IoT development stack, and outline how open source can be used as a means of market control as well as a booster of innovation and a way to tap into the IoT developer talent pool. The data have been collected from 3,700 IoT developers in 150 countries across the globe, surveyed in Q4 2015 and shines a light on how big a deal open source really is in IoT, why developers love it, and how companies can create a successful commercial strategy around the use of open source by aligning themselves with the values of that core stakeholder group that are developers. Read more