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

Oracle: New VirtualBox 5.2 Beta, SPARC M8 Processors Launched

  • VirtualBox 5.2 to Let Users Enable or Disable Audio Input and Output On-the-Fly
    Oracle announced new updates for its popular, cross-platform and open-source virtualization software, the third Beta of the upcoming VirtualBox 5.2 major release and VirtualBox 5.1.28 stable maintenance update. We'll start with the stable update, VirtualBox 5.1.28, as it's more important for our readers using Oracle VM VirtualBox for all of their virtualization needs. The VirtualBox 5.1 maintenance release 28 is here to improve audio support by fixing various issues with both the ALSA and OSS backends, as well as an accidental crash with AC'97.
  • SPARC M8 Processors Launched
    While Oracle recently let go of some of their SPARC team, today marks the launch of the SPARC M8. The initial SPARC M8 line-up includes the T8-1, T8-2, T8-4. M8-8, and SuperCluster M8-8 servers.

Wikileaks Releases Spy Files Russia, CCleaner Infected, Equifax Has a Dirty Little Secret

  • Spy Files Russia
    This publication continues WikiLeaks' Spy Files series with releases about surveillance contractors in Russia. While the surveillance of communication traffic is a global phenomena, the legal and technological framework of its operation is different for each country. Russia's laws - especially the new Yarovaya Law - make literally no distinction between Lawful Interception and mass surveillance by state intelligence authorities (SIAs) without court orders. Russian communication providers are required by Russian law to install the so-called SORM ( Система Оперативно-Розыскных Мероприятий) components for surveillance provided by the FSB at their own expense. The SORM infrastructure is developed and deployed in Russia with close cooperation between the FSB, the Interior Ministry of Russia and Russian surveillance contractors.
  • Malware-Infected CCleaner Installer Distributed to Users Via Official Servers for a Month
    Hackers have managed to embed malware into the installer of CCleaner, a popular Windows system optimization tool with over 2 billion downloads to date. The rogue package was distributed through official channels for almost a month. CCleaner is a utilities program that is used to delete temporary internet files such as cookies, empty the Recycling Bin, correct problems with the Windows Registry, among other tasks. First released in 2003, it has become hugely popular; up to 20 million people download it per month. Users who downloaded and installed CCleaner or CCleaner Cloud between Aug. 15 and Sept. 12 should scan their computers for malware and update their apps. The 32-bit versions of CCleaner v5.33.6162 and CCleaner Cloud v1.07.3191 were affected.
  • Equifax Suffered a Hack [sic] Almost Five Months Earlier Than the Date It Disclosed
  • This is why you shouldn’t use texts for two-factor authentication

    For a long time, security experts have warned that text messages are vulnerable to hijacking — and this morning, they showed what it looks like in practice.

Amazon Changes Rental ('Cloud') Model on GNU/Linux

Devices/Hardware: Embedded/Boards, CODESYS, and EPYC Linux Performance

  • Linux friendly IoT gateway runs on 3.5-inch Bay Trail SBC
    While the MB-80580 SBC lists SATA II, the gateway indicates SATA III. Also, the gateway datasheet notes that the RS232 ports can all be redirected to RS232/422/485. Software includes Windows IoT Core and Server, as well as Yocto, Ubuntu Snappy Core, and CentOS Linux distributions.
  • Rugged panel PC scales up to a 19-inch touchscreen
    The fanless, IP65-rated WinSystems “PPC65B-1x” panel PC runs Linux or Win 10 on a quad-core Atom E3845, and offers 10.4 to 19-inch resistive touchscreens.
  • CODESYS announces CODESYS-compatible SoftPLC for open Linux device platforms
  • EPYC Linux performance from AMD
    Phoronix have been hard at work testing out AMD's new server chip, specifically the 2.2/2.7/3.2GHz EPYC 7601 with 32 physical cores.  The frequency numbers now have a third member which is the top frequency all 32 cores can hit simultaneously, for this processor that would be 2.7GHz.  Benchmarking server processors is somewhat different from testing consumer CPUs, gaming performance is not as important as dealing with specific productivity applications.   Phoronix started their testing of EPYC, in both NUMA and non-NUMA configurations, comparing against several Xeon models and the performance delta is quite impressive, sometimes leaving even a system with dual Xeon Gold 6138's in the dust.  They also followed up with a look at how EPYC compares to Opteron, AMD's last server offerings.  The evolution is something to behold.
  • Opteron vs. EPYC Benchmarks & Performance-Per-Watt: How AMD Server Performance Evolved Over 10 Years
    By now you have likely seen our initial AMD EPYC 7601 Linux benchmarks. If you haven't, check them out, EPYC does really deliver on being competitive with current Intel hardware in the highly threaded space. If you have been curious to see some power numbers on EPYC, here they are from the Tyan Transport SX TN70A-B8026 2U server. Making things more interesting are some comparison benchmarks showing how the AMD EPYC performance compares to AMD Opteron processors from about ten years ago.