Hello. Zypper can add iso files as repo. Can I simply go for a zypper dup (zypper in zypper maybe first?) via the downloaded .iso image file of 12.1(x86) on my running old 11.2 system? Or is it better to boot via 12.1 media and taking the system offline? Or is zypper able to handle all those changes just fine by now via dup? Thanks.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-02-24 11:30, cagsm wrote:
Hello. Zypper can add iso files as repo. Can I simply go for a zypper dup (zypper in zypper maybe first?) via the downloaded .iso image file of 12.1(x86) on my running old 11.2 system? Or is it better to boot via 12.1 media and taking the system offline? Or is zypper able to handle all those changes just fine by now via dup? Thanks.
Zypper dup procedure is only supported for one version jump. As to whether the method you propose via iso image works, I do not know. Have you read the wiki?
http://en.opensuse.org/SDB:System_upgrade http://en.opensuse.org/SDB:Offline_upgrade
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
On Fri, Feb 24, 2012 at 02:50:35PM +0100, Carlos E. R. wrote:
On 2012-02-24 11:30, cagsm wrote:
Hello. Zypper can add iso files as repo. Can I simply go for a zypper dup (zypper in zypper maybe first?) via the downloaded .iso image file of 12.1(x86) on my running old 11.2 system? Or is it better to boot via 12.1 media and taking the system offline? Or is zypper able to handle all those changes just fine by now via dup? Thanks.
Zypper dup procedure is only supported for one version jump.
It's only *tested* for one version jump is more correct.
As to whether the method you propose via iso image works, I do not know.
The pre-11.4 zyppers had a bit of a problem with package ordering, so you might run into trouble with a direct 'zypper dup'. It *should* work if you lock the "liblzma0" package (zypper al liblzma0) before doing the 'zypper dup'. I'd recommend to boot the iso so that the 12.1 software stack is used, just to be on the safe side. But, as I said above, a 11.2->12.1 update is untested, so there may be some other issues you might run into.
Cheers, Michael.
On 2012/02/24 15:36 (GMT+0100) Michael Schroeder composed:
The pre-11.4 zyppers had a bit of a problem with package ordering, so you might run into trouble with a direct 'zypper dup'. It *should* work if you lock the "liblzma0" package (zypper al liblzma0) before doing the 'zypper dup'.
Sounds backwards. Before I zypper dup to a newer version, I do
zypper in liblzma0 libzypp zypper rpm satsolver-tools perl-Bootloader \ openSUSE-release wget curl bzip2 yast2-bootloader udev mkinitrd
to pull in all the package management related things I'm aware of before proceeding with everything else.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-02-24 15:36, Michael Schroeder wrote:
On Fri, Feb 24, 2012 at 02:50:35PM +0100, Carlos E. R. wrote:
Zypper dup procedure is only supported for one version jump.
It's only *tested* for one version jump is more correct.
Kulow said "not supported" here:
+++···················· Date: Wed, 8 Dec 2010 11:00:07 +0100 From: Stephan Kulow <> To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] "zypper dup" from 11.2 to 11.4?
Am Mittwoch, 8. Dezember 2010 schrieb Karl Eichwalder:
In the past, we recommended to use the dup feature to upgrade from 11.2 to 11.3. I'm wondering whether it will be supported to upgrade directly from 11.2 to 11.4 and thus skipping one version (11.3)?
If yes, I'll adjust the manual accordingly.
It will not be supported - even if it may work.
Greetings, Stephan ····················++-
and later said:
+++···················· I forgot to answer this: lack of support in the context of openSUSE means RESOLVED/INVALID ····················++-
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar)
Hello,
On Fri, 24 Feb 2012, Michael Schroeder wrote:
On Fri, Feb 24, 2012 at 02:50:35PM +0100, Carlos E. R. wrote:
On 2012-02-24 11:30, cagsm wrote:
Hello. Zypper can add iso files as repo. Can I simply go for a zypper dup (zypper in zypper maybe first?) via the downloaded .iso image file of 12.1(x86) on my running old 11.2 system? Or is it better to boot via 12.1 media and taking the system offline? Or is zypper able to handle all those changes just fine by now via dup? Thanks.
Zypper dup procedure is only supported for one version jump.
It's only *tested* for one version jump is more correct.
I've done the 11.2 -> 11.4 upgrade. No problems I did not cause myself (having locked packages and broken dependencies ;)
Before that I did a 11.1/32bit -> 11.2/64bit upgrade with zypper.
As to whether the method you propose via iso image works, I do not know.
I have the ISO as a repo and also did the upgrade with that.
I did (and will do in the future) this: copy the system to a second partition with rsync. I.e. I made a second system-partition, and ran
rsync -auxlPRAXSHD --delete / /NEW_ROOT
and then added the copy to grubs menu.lst, and as I kept working during the rsync ran that rsync again directly before booting the copy (which also updated the menu.lst[1]). Then, having booted the copy I
- changed repos from 11.2 to 11.4 - checked that repo-priorities are correct, e.g: packman < update < iso < oss/non-oss main repo - zypper clean - zypper ref - zypper dup
and resolve any conflicts which in my case were fewer than I feared, as I break quite a few packages ... Talking of that, I'm just re-syncing back the upgraded system to the (cleaned) partition the 11.2 was on, in order to run the upgrade to 12.1 with that.
[1] if I wanted to remove the original and keep the copied and upgraded system it suffices to just reinstall grub from that system.
The pre-11.4 zyppers had a bit of a problem with package ordering, so you might run into trouble with a direct 'zypper dup'. It *should* work if you lock the "liblzma0" package (zypper al liblzma0) before doing the 'zypper dup'.
Haven't noticed that when I did the upgrade, never booted the old system since booting the copy to run the upgrade ;)
I'd recommend to boot the iso so that the 12.1 software stack is used, just to be on the safe side. But, as I said above, a 11.2->12.1 update is untested, so there may be some other issues you might run into.
Yeah, 11.2 -> 12.1 is a bit steep, esp. as the change to systemd may cause additional trouble. Well, doing the upgrade on a copy keeps the mind quite relaxed, just reformat the copy, and start fresh with rsyncing ;)
#include <stddisclaimer.h>
HTH, -dnh
-
cagsm -
Carlos E. R. -
David Haller -
Felix Miata -
Michael Schroeder