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

Mozilla: Virtual Reality in Mixed Reality, Taskcluster Development

  • Building Bold New Worlds With Virtual Reality
    From rich text to video to podcasts, the Internet era offers an array of new ways for creators to build worlds. Here at Mozilla, we are particularly excited about virtual reality. Imagine moving beyond watching or listening to a story; imagine also feeling that story. Imagine being inside it with your entire mind and body. Now imagine sharing and entering that experience with something as simple as a web URL. That’s the potential before us.
  • This Week in Mixed Reality: Issue 3
    This week we’re heads down focusing on adding features in the three broad areas of Browsers, Social and the Content Ecosystem.
  • New to me: the Taskcluster team
    At this time last year, I had just moved on from Release Engineering to start managing the Sheriffs and the Developer Workflow teams. Shortly after the release of Firefox Quantum, I also inherited the Taskcluster team. The next few months were *ridiculously* busy as I tried to juggle the management responsibilities of three largely disparate groups.
  • Taskcluster migration update: we're finished!
    Over the past few weeks we've hit a few major milestones in our project to migrate all of Firefox's CI and release automation to taskcluster. Firefox 60 and higher are now 100% on taskcluster!

OSS Leftovers

  • After the First US Transaction, Propy Announces an Open Source Developer Program
    California-based blockchain startup Propy, is bringing the commercial use of blockchain technology to the US. After facilitating the first US Blockchain-based real estate deed in Vermont, Propy announced a new open source Developer Program. The idea behind Propy: it allows anyone to buy or sell real estate, anywhere, online. Propy provides an efficient crypto and fiat payment and an immutable record on the blockchain, ensuring that title deeds and property rights will be there forever.
  • Titus, the Netflix container management platform, is now open source
    Titus powers critical aspects of the Netflix business, from video streaming, recommendations and machine learning, big data, content encoding, studio technology, internal engineering tools, and other Netflix workloads. Titus offers a convenient model for managing compute resources, allows developers to maintain just their application artifacts, and provides a consistent developer experience from a developer’s laptop to production by leveraging Netflix container-focused engineering tools.
  • Netflix's Container Management System Is Now Open Source
    On Thursday Netflix announced it's made its home grown container management system, Titus, open source.
  • Lumina Networks on delivering open source SDN
    What kinds of companies should consider open source SDN, and what are the associated challenges in using such open source deployments? Lumina Networks has unrivalled expertise in working with customers and partners to deliver implementations, and explains its processes and outlines the benefits of using open source SDN.
  • Luxoft launches PELUX 1.0 open source platform for automotive
    Luxoft’s automotive division has launched PELUX 1.0, an open source platform available to developers. This has been developed from its PELUX software suite as used by carmakers and tier 1 suppliers to build converged infotainment, autonomous driving, communication, HMI and car body control systems.
  • Dev Preview: MongoDB Enterprise Running on OpenShift
    In order to compete and get products to market rapidly, enterprises today leverage cloud-ready and cloud-enabled technologies. Platforms as a Service (or PaaS) provide out-of-the-box capabilities which enable application developers to focus on their business logic and users instead of infrastructure and interoperability. This key ability separates successful projects from those which drown themselves in tangential work which never stops. In this blog post, we’ll cover MongoDB’s general PaaS and cloud enablement strategy as well as touch upon some new features of Red Hat’s OpenShift which enable you to run production-ready MongoDB clusters. We’re also excited to announce the developer preview of MongoDB Enterprise Server running on OpenShift. This preview allows you to test out how your applications will interact with MongoDB running on OpenShift.
  • Is Open Source The AI Nirvana for Intel? [Ed: openwashing a malicious company using buzzwords and urban myths]
  • Writing Chuck – Joke As A Service
    Recently I really got interested to learn Go, and to be honest I found it to be a beautiful language. I personally feel that it has that performance boost factor from a static language background and easy prototype and get things done philosophy from dynamic language background. The real inspiration to learn Go was these amazing number of tools written and the ease with which these tools perform although they seem to be quite heavy. One of the good examples is Docker. So I thought I would write some utility for fun, I have been using fortune, this is a Linux utility which gives random quotes from a database. I thought let me write something similar but let me do something with jokes, keeping this mind I was actually searching for what can I do and I landed up on jokes about Chuck Norris or as we say it facts about him. I landed up on chucknorris.io they have an API which can return different jokes about Chuck, and there it was my opportunity to put something up and I chose Go for it.

today's howtos

Security: Updates, IBM, Elytron and Container Vulnerability Scanning

  • Security updates for Friday
  • IBM Security launches open-source AI
    IBM Security unveiled an open-source toolkit at RSA 2018 that will allow the cyber community to test their AI-based security defenses against a strong and complex opponent in order to help build resilience and dependability into their systems.
  • Elytron: A New Security Framework in WildFly/JBoss EAP
    Elytron is a new security framework that ships with WildFly version 10 and Red Hat JBoss Enterprise Application Platform (EAP) 7.1. This project is a complete replacement of PicketBox and JAAS. Elytron is a single security framework that will be usable for securing management access to the server and for securing applications deployed in WildFly. You can still use the legacy security framework, which is PicketBox, but it is a deprecated module; hence, there is no guarantee that PicketBox will be included in future releases of WildFly. In this article, we will explore the components of Elytron and how to configure them in Wildfly.
  • PodCTL #32 – Container Vulnerability Scanning