I did the architecture change via offline (usb key) and it somehow wasnt going all that bad after all. But it did write quite a lot of stuff such as wrong permissions 4755 0755 or all those kind of things I remember from past years, I always wanted to ask the community why there are constantly wrong permissions in the packages while install or upgrade. I even often experience these wrongly set permissions from one beta or releasecandidate edition of opensuse to the following or during zypper up in the past. Anyways, the x64 system first enumerated the external ethernet interface badly, but I had that update folder locally on the disk so I set that as an additional repo via yast as local folder or path, and zypper up found 600something patches and applied them including kernel and all, and after the next reboot the ethernet interface was back again enumerated properly again or maybe the reboot or udev or whatever fixed it and it came back online and the system was again working properly with ssh named squid ntp and some little normal things. About these many errors (not just the permission errors) during the opensuse install procedures: Some netscape NSS package struck me that it crashed the javaruntime that was mangling and working it with a java interpreter core crash or something, I dont know what it was eactly about some package containing the string nss some library or certificates or something? Does rpm -Va actually really verify all installed rpm packages and tell me for example if that java-crashing nss package was really executing fine or did rpm automatically somehow fix this at a later time or how does this really work on linux with rpm, how to make sure that an rpm really did all the steps according to what it should do, scripts and extracting and working on files and all? I think I remember from years back when during an offline update via dvd or so later inside the upgraded but somewhat crappy system I fired up yast software management module and it brought up some screen with some tens or so listed packages and yast module automatically told me that there was something wrong with those packages listed and it needed to work on them again and if I wanted to do that or so I remember. Is that the same as with rpm -Va or is there a way to really check packages? I never again found that place in yast ever again after that single incident. Any hints? Thanks. On Fri, Dec 12, 2014 at 10:45 PM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-12-12 22:18, cagsm wrote:
Okay thanks for the quick reply, I already found some posts at various places which say offline upgrade or change of architecture should rather work. Now it all boils down to specifying an additional location of the patch rpm packages in ly locally mirrored update folder from the update servers of the opensuse project. It is
Don't run the updates during the system upgrade.
You run the upgrade first. The DVD will not see the partition, you will have to manually enter it; then the installer will complain in red letters or something. Just go ahead. Well, better made a full backup in advance.
After the upgrade (do not attempt graphical mode yet, probably will crash), you have to search and update all remaining packages from the wrong architecture. Try:
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" | | egrep -v "noarch" | less -S
which will list all 32 bit packages, and other things, but not many. Some of the 32 bit packages do not have 64 bit versions, like grub.
You can create a mirror of the oss and non-oss repos, and point the updater to them, yes. But do not add the update repos initially, it complicates things. After purging the remaining 32 bit packages, and booting, you can attempt a zypper patch or yast online update, in graphical mode if you wish.
- -- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlSLYgcACgkQtTMYHG2NR9XA0QCePpCsKq66fpQ4zbPMmHNO5uAC hY0AoJPKNtc1u5aWjXUwNk6wVoJCsTDb =1Bix -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org