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

Programming: Buzzwords, Meson, Tracealyzer, LLVM, Python and Rust

  • What is DevSecOps? Everything You Need To Know About DevSecOps

    Most people are familiar with the term “DevOps,” but they don’t know how to really utilize it. There’s more to DevOps than just development and operational teams. There’s an essential element of DevOps that is often missing from the equation; IT security. Security should be included in the lifecycle of apps.  The reason you need to include security is that security was once assigned to one team that integrated security near the end-stages of development. Taking such a lax approach to security wasn’t such a problem when apps were developed in months or years. The average development cycle has changed quite a bit, though, and apps can be developed in a matter of days or weeks. Outdated security practices like leaving security too late can bring DevOps initiatives to their knees. 

  •   
  • Nibble Stew: The Meson Manual: Good News, Bad News and Good News

    Starting with good news, the Meson Manual has been updated to a third edition. In addition to the usual set of typo fixes, there is an entirely new chapter on converting projects from an existing build system to Meson. Not only are there tips and tricks on each part of the conversion, there is even guidance on how to get it done on projects that are too big to be converted in one go.

  • Percepio Releases Tracealyzer Visual Trace Diagnostics Solution Version 4.4 with Support for Embedded Linux

    Percepio announced the availability of Tracealyzer version 4.4 with support for embedded Linux. Tracealyzer gives developers insight during software debugging and verification at the system level by enabling visual exploratory analysis from the top down. This makes the software suitable for spotting issues during full system testing and drill down into the details to find the cause. Version 4.4 adds several views optimized for Linux tracing, in addition to a set of visualizations already in Tracealyzer, and leverages Common Trace Format (CTF) and the widely supported LTTng, an open source tracing framework.

  •   
  • LLVM Adds A SPIR-V CPU Runner For Handling GPU Kernels On The CPU - Phoronix

    LLVM has merged an experimental MLIR-based SPIR-V CPU runner that the developers are working towards being able to handle CPU-based execution of GPU kernels.  This new SPIR-V runner is built around the MLIR intermediate representation (Multi-Level Intermediate Representation) with a focus of going from GPU-focused code translated through SPIR-V and to LLVM and then executed on the CPU. The runner focus is similar to that of the MLIR-based runners for NVIDIA CUDA, AMD ROCm, and Vulkan, but just executing on the CPU itself. It was earlier this year LLVM added the MLIR-Vulkan-Runner for handling MLIR on Vulkan hardware. 

  • Python Modulo in Practice: How to Use the % Operator – Real Python

    Python supports a wide range of arithmetic operators that you can use when working with numbers in your code. One of these operators is the modulo operator (%), which returns the remainder of dividing two numbers.

  • Test & Code : Python Testing for Software Engineering 136: Wearable Technology - Sophy Wong

    Wearable technology is not just smart consumer devices like watches and activity trackers. Wearable tech also includes one off projects by designers, makers, and hackers and there are more and more people producing tutorials on how to get started. Wearable tech is also a great way to get both kids and adults excited about coding, electronics, and in general, engineering skills. Sophy Wong is a designer who makes really cool stuff using code, technology, costuming, soldering, and even jewelry techniques to get tech onto the human body.

  • Librsvg's test suite is now in Rust

    Some days ago, Dunja Lalic rewrote the continuous integration scripts to be much faster. A complete pipeline used to take about 90 minutes to run, now it takes about 15 minutes on average. [...] The most complicated thing to port was the reference tests. These are the most important ones; each test loads an SVG document, renders it, and compares the result to a reference PNG image. There are some complications in the tests; they have to create a special configuration for Fontconfig and Pango, so as to have reproducible font rendering. The pango-rs bindings do not cover this part of Pango, so we had to do some things by hand.

ARM32 in Linux and Open Source Hardware Certification

  • ARM32 Page Tables

    As I continue to describe in different postings how the ARM32 start-up sequence works, it becomes necessary to explain in-depth the basic kernel concepts around page tables and how it is implemented on ARM32 platforms. To understand the paging setup, we need to repeat and extend some Linux paging lingo. Some good background is to read Mel Gormans description of the Linux page tables from his book “Understanding the Linux Virtual Memory Manager”. This book was published in 2007 and is based on Mel’s PhD thesis from 2003. Some stuff has happened in the 13 years since then, but the basics still hold. It is necessary to also understand the new layers in the page tables such as the five layers of page tables currently used in the Linux kernel. First a primer: the ARM32 architecture with a classic MMU has 2 levels of page tables and the more recent LPAE (Large Physical Address Extension) MMU has 3 levels of page tables. Only some of the ARMv7 architectures have LPAE, and it is only conditionally enabled, i.e. the machines can also use the classic MMU if they want, they have both. It is not enabled by default on the multi_v7 configuration: your machine has to explicitly turn it on during compilation. The layout is so different that the same binary image can never support both classic and LPAE MMU in the same kernel image.

  • Announcing the Open Source Hardware Certification API – Open Source Hardware Association

    Today we are excited to announce the launch of a read/write API for our Open Source Hardware Certification program. This API will make it easier to apply for certification directly from where you already document your hardware, as well as empower research, visualizations, and explorations of currently certified hardware. OSHWA’s Open Source Hardware Certification program has long been an easy way for creators and users alike to identify hardware that complies with the community definition of open source hardware. Since its creation in 2016, this free program has certified hardware from over 45 countries on every continent except Antarctica. Whenever you see the certification logo on hardware:

LibreOffice: Presentation Size Decreasing and New Presentations About LibreOffice

Games: Monster Prom, Möbius Front '83 and League Of Legends

  • The absurd multiplayer dating sim Monster Prom 2: Monster Camp is out now | GamingOnLinux

    I will admit that the original Monster Prom is something special as it remains as the only dating sim type of game I've enjoyed, and now there's a brand new helping of it out with Monster Prom 2: Monster Camp. The original was an unexpected pleasure for me, as a genre I've rarely been able to enjoy. Let's face it, "In Monster Prom I was rejected even after letting a princess ride me", is not a typical GamingOnLinux headline. Monster Prom 2: Monster Camp was funded thanks to a Kickstarter campaign back in 2019, and it has released as of October 23 along with full Linux support as expected. Developer Beautiful Glitch mentioned how they've pretty much taken all that was tasty from the original, and threw in some spices to make Monster Prom 2: Monster Camp.

  • Möbius Front '83 is a tactical turn-based strategy game from Zachtronics | GamingOnLinux

    Releasing with Linux support on November 5 is Möbius Front '83 latest title from Zachtronics (SpaceChem, Infinifactory, Opus Magnum, Eliza). Unlike most of their previous titles, it's not a puzzle game. They say it's actually a conventional strategy game designed from scratch by the clever minds at Zachtronics, so it will have their own special feel to it. "The year is 1983 and the United States of America must defend itself from an enemy it could have never imagined— an America from an alternate universe that will stop at nothing to seize control of the country’s heartland!"

  • How to play League of Legends on Linux | FOSS Linux

    League Of Legends is a game made into a snap, meaning that the software package can be installed and executed across different Linux distributions. Being among the largest footprints of any game in streaming media communities on platforms like Twitch and YouTube, installing it in your Linux system will be great. For our case, we will install it in Ubuntu distro.