[opensuse-factory] offline 13.1 32 bit to 13.1 64 bit upgrade awful
Before starting the "upgrade", I removed all optional repos, then did zypper dup. When done there remained 13 'System Packages', which I removed manually before rebooting into the upgrade process via Grub. http://fm.no-ip.com/Tmp/SUSE/131/offline13132to13164upgrade-gx151.txt lists installed packages state on completion of offline upgrade. Summary: i586 packages 821 i686 packages 6 x86_64 packages 80 noarch packages 642 Upgrading did not change /etc/os-release from i586 to x86_64. In fact, openSUSE-release currently installed is among the i586, though openSUSE-release-ftp is x86_64. I've gotten the i586 count down to around 700 by installing a few packages with zypper that caused arch changes, and some others by feeding zypper the entire filename of selected packages. Is there some simple way to get zypper or yast to replace the balance of i586/i686 with x86_64? I see in zypper man page maybe capability might apply, but if so, there's no example there I can grok. Would it be enough to use zypper dup after upgrading openSUSE-release to x86_64? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 15.02.2016 um 05:44 schrieb Felix Miata:
Is there some simple way to get zypper or yast to replace the balance of i586/i686 with x86_64?
I've successfully done this (32 -> 64 bit) on a couple of occasions, but always by installing from the DVD and then choosing to upgrade an existing installation. And I was always in deed going from an older to a newer openSUSE version. Sometimes I had to click something like "list all installed openSUSE versions" in order to be able to chose the one I wanted to upgrade. Recently it has worked for me with 12.3/32 -> 13.1/64 and even with 12.1/32 -> Leap 42.1/64 on a few test machines. I never tried your explicit scenario (13.1/32 -> 13.1/64), though. HTH -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 15.02.2016 05:44, Felix Miata wrote:
Upgrading did not change /etc/os-release from i586 to x86_64. In fact, openSUSE-release currently installed is among the i586, though openSUSE-release-ftp is x86_64. I've gotten the i586 count down to around 700 by installing a few packages with zypper that caused arch changes, and some others by feeding zypper the entire filename of selected packages. Is there some simple way to get zypper or yast to replace the balance of i586/i686 with x86_64? I see in zypper man page maybe capability might apply, but if so, there's no example there I can grok. Would it be enough to use zypper dup after upgrading openSUSE-release to x86_64?
http://seifesrants.blogspot.de/2011/02/opensuse-32bit-to-64bit-live-conversi... -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-02-15 05:44, Felix Miata wrote:
Before starting the "upgrade", I removed all optional repos, then did zypper dup.
Then you did an online upgrade, not an offline upgrade. Offline means booting the installation DVD, then choosing upgrade. Many people have used that procedure to upgrade from 32 to 64 bit, although not supported. After done, you still have to upgrade many other packages because they were not found in the DVD. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. composed on 2016-02-15 13:47 (UTC+0100):
Felix Miata wrote:
Before starting the "upgrade", I removed all optional repos, then did zypper dup.
Then you did an online upgrade, not an offline upgrade. Offline means booting the installation DVD, then choosing upgrade.
Obviously you didn't understand what I meant what I wrote to say. Steps performed: 1-remove optional repos from i586 13.1 installation 2-zypper dup (to restore installed packages to OSS/Non-OSS/Update versions only) 3-cleanup leaves manually (all (System Packages) removed) 4-boot x86_64 13.1 installation media with upgrade=1 on kernel cmdline 5-select i586 13.1 installation as upgrade target 6-ack arch change 7-let yast do its job (double digit "packages to upgrade" count was obviously low) 8-boot "upgraded" 13.1 installation Resulting installed packages at this point: i586 821 i686 6 x86_64 80 noarch 642 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-02-15 19:06, Felix Miata wrote:
Carlos E. R. composed on 2016-02-15 13:47 (UTC+0100):
Obviously you didn't understand what I meant what I wrote to say. Steps performed:
You are right :-}
1-remove optional repos from i586 13.1 installation
2-zypper dup (to restore installed packages to OSS/Non-OSS/Update versions only)
Ah.
3-cleanup leaves manually (all (System Packages) removed)
4-boot x86_64 13.1 installation media with upgrade=1 on kernel cmdline
Didn't know that option.
5-select i586 13.1 installation as upgrade target
6-ack arch change
The DVD should complain bitterly :-P
7-let yast do its job (double digit "packages to upgrade" count was obviously low)
8-boot "upgraded" 13.1 installation
Resulting installed packages at this point: i586 821 i686 6 x86_64 80 noarch 642
Only 80 x86_64 packages? That's weird, something must have gone wrong. Perhaps the list of installed packages contained only a few from the DVD, so most could not be upgraded. Verify the package containing os-release, /etc/SuSE-release, and SUSE-brand. Once correct, do a "zypper dup". Run this: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist | less -S and check the list. or better: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "x86_64" | less -S and update those manually. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Le 15/02/2016 19:06, Felix Miata a écrit :
Obviously you didn't understand what I meant what I wrote to say. Steps performed:
understood, now. but I don't see what is the use of such action, seems to me very close to a fresh install, and much more risky. You seems to think every package installed through extra repo have the equivalent in official repos, don't seems likely, so the zypper dup should get many problems. and you will have to reinstall extra repos to get the same system?? Thinking about the problem, I wondered if it could be possible to export the package list, blank the /, replace all occurrences of xi86 by amd64, then reinstall. But can we presume that any 32 bits package have the exact counterpart as 64 bits? probably no. so seems to be much trouble for little use. Keep 32bits as long as you can, after that, if you need Leap, go to fresh install (ATM probably Leap 42.2 or 43.1) jdd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. composed on 2016-02-15 20:13 (UTC+0100):
Felix Miata wrote:
Carlos E. R. composed on 2016-02-15 13:47 (UTC+0100):
Obviously you didn't understand what I meant what I wrote to say. Steps performed:
You are right :-}
1-remove optional repos from i586 13.1 installation
2-zypper dup (to restore installed packages to OSS/Non-OSS/Update versions only)
Ah.
3-cleanup leaves manually (all (System Packages) removed)
4-boot x86_64 13.1 installation media with upgrade=1 on kernel cmdline
Didn't know that option.
5-select i586 13.1 installation as upgrade target
6-ack arch change
The DVD should complain bitterly :-P
I rarely use DVDs. I normally, as I did here, use Grub, installation linux and initrd, and HTTP source. Since this is for a release version, I could have used a DVD, since I have the .iso, but HTTP is a habit.
7-let yast do its job (double digit "packages to upgrade" count was obviously low)
8-boot "upgraded" 13.1 installation
Resulting installed packages at this point: i586 821 i686 6 x86_64 80 noarch 642
Only 80 x86_64 packages? That's weird, something must have gone wrong.
Hence the thread here.
Perhaps the list of installed packages contained only a few from the DVD, so most could not be upgraded.
I doubt there's anything on the DVD that isn't in HTTP, unless Evergreening the repos went wrong somewhere.
Verify the package containing os-release, /etc/SuSE-release, and SUSE-brand. Once correct, do a "zypper dup".
Too late. That's all been done. The only remaining i586 package is master-boot-code, which apparently is not available for 13.1 in x86_64 version. Excerpts from .bash_history tail: http://fm.no-ip.com/Tmp/SUSE/131/gx151-s13132to13164fixup.txt You may note a lot of logic gaps in it, but that's what happens utilizing mc instead of bash. Unrecognized commands are either aliases or miniscripts in /usr/local/bin. e.g. zypse picks out x86 and noarch packages, strips source and DVD packages, and sorts zypper se -s results. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
jdd composed on 2016-02-15 20:32 (UTC+0100):
Felix Miata composed:
Obviously you didn't understand what I meant what I wrote to say. Steps performed:
understood, now.
but I don't see what is the use of such action, seems to me very close to a fresh install, and much more risky.
To which action do you refer? Removing packages from optional repos? That's covered...
You seems to think every package installed through extra repo have the equivalent in official repos,
Dunno why you think that.
don't seems likely, so the zypper dup should get many problems.
Before starting, I created user-packages.xml with YaST. And, the upgrade was performed on a modified (UUID, volume label, bootloader & fstab) clone of the original, keeping the original intact. After the optional repo removal and dup, I used zypper to remove the remaining (System Packages), so .bash_history contains a record, in addition to /var/log/zypp/history, of what was removed to reach an OSS/Non-OSS/Update-only state.
and you will have to reinstall extra repos to get the same system??
No problem. Just rsync /etc/zypp/repos.d/* from original to new, and use command history to install the manually removed. Or utilize use-packages.xml. Or a combination. Still, I expected much much better of an offline upgrade than getting only 80 32 bit packages replaced by 64 bit. Even the old kernels were left in place. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le 15/02/2016 22:00, Felix Miata a écrit :
jdd composed on 2016-02-15 20:32 (UTC+0100):
Felix Miata composed:
Obviously you didn't understand what I meant what I wrote to say. Steps performed:
understood, now.
but I don't see what is the use of such action, seems to me very close to a fresh install, and much more risky.
To which action do you refer? Removing packages from optional repos? That's covered...
trying to update in place of making a fresh install
No problem. Just rsync /etc/zypp/repos.d/* from original to new, and use command history to install the manually removed. Or utilize use-packages.xml.
this one keeps the bit number
Or a combination.
Still, I expected much much better of an offline upgrade than getting only 80 32 bit packages replaced by 64 bit. Even the old kernels were left in place.
why keep anything of the old install. You still can use /etc config from the old kept install. I do this most of the time: keep the old one (some weeks or even month), make a fresh one and go to the other folder when I need it (for example, I copy from one to the other my scripts in ~/bin) jdd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-15 22:00, Felix Miata wrote:
Still, I expected much much better of an offline upgrade than getting only 80 32 bit packages replaced by 64 bit. Even the old kernels were left in place.
I think that the old kernels should remain, but together with the new kernels. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbCWFcACgkQja8UbcUWM1xQJwD/aE/diuWxpX0EGwMNHGW9TyVv lf8mmaoM7O+S8NRpjt0A/1A8pQfCOfC/+kW04ajswepg3I7aCRKJ0IIuGCzA8t17 =zJoz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. composed on 2016-02-15 23:59 (UTC+0100):
Felix Miata wrote:
Still, I expected much much better of an offline upgrade than getting only 80 32 bit packages replaced by 64 bit. Even the old kernels were left in place.
I think that the old kernels should remain, but together with the new kernels.
In a normal upgrade, of course, but for what use on a system with no other 32 bit binaries except compats, as this kind of upgrade is expected to produce? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-16 00:20, Felix Miata wrote:
Carlos E. R. composed on 2016-02-15 23:59 (UTC+0100):
Felix Miata wrote:
Still, I expected much much better of an offline upgrade than getting only 80 32 bit packages replaced by 64 bit. Even the old kernels were left in place.
I think that the old kernels should remain, but together with the new kernels.
In a normal upgrade, of course, but for what use on a system with no other 32 bit binaries except compats, as this kind of upgrade is expected to produce?
Maybe... just an idea. Maybe it didn't work right because it is an upgrade of the same release number. Maybe 13.1-32 to 13.2-64 would go right. Maybe many packages were not upgraded because it was in fact a downgrade. Think: the 64 bit libraries in the install media would be older than the updated 32 bit libraries in the installation. This would explain the low number of upgraded packages. Still, it is strange... a DVD upgrade should replace everything in sight, regardless of version. But you say it is not a DVD... should not matter, if it is the iso image of the DVD. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlbChPsACgkQja8UbcUWM1yqbgD+JBQyki9S70p0wdJCLqj2i22u vBjz5kZp2KxckOMQYHQA/Aq4HMvqXYuw6p9Gu/ptKKxB4iwpiYI6BTFbBf/aDTaO =R+kT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. composed on 2016-02-16 03:10 (UTC+0100):
Felix Miata wrote:
Carlos E. R. composed on 2016-02-15 23:59 (UTC+0100):
Felix Miata wrote:
Still, I expected much much better of an offline upgrade than getting only 80 32 bit packages replaced by 64 bit. Even the old kernels were left in place.
I think that the old kernels should remain, but together with the new kernels.
In a normal upgrade, of course, but for what use on a system with no other 32 bit binaries except compats, as this kind of upgrade is expected to produce?
Maybe... just an idea. Maybe it didn't work right because it is an upgrade of the same release number. Maybe 13.1-32 to 13.2-64 would go right. Maybe many packages were not upgraded because it was in fact a downgrade.
Think: the 64 bit libraries in the install media would be older than the updated 32 bit libraries in the installation.
The "install media" was HTTP, which includes the two update repos, and so includes the exact versions installed on the target before beginning the upgrade.
This would explain the low number of upgraded packages. Still, it is strange... a DVD upgrade should replace everything in sight, regardless of version. But you say it is not a DVD... should not matter, if it is the iso image of the DVD. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Stefan Seyfried composed on 2016-02-15 13:39 (UTC+0100):
http://seifesrants.blogspot.de/2011/02/opensuse-32bit-to-64bit-live-conversi...
Dunno if I'll ever want to upgrade same distro from 32 to 64 again, but given my experience described here, your method will be welcome for trying first. Zypper is my strong preference for upgrades anyway. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Carlos E. R. -
Felix Miata -
jdd -
Stefan Seyfried -
Till Dörges