On 2014-12-13 02:18, cagsm wrote:
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.
I don't know if this is your case, but it is normal in openSUSE for an rpm to contain files with some permissions, which are later adjusted to some other permissions via /etc/permissions, and there are reasons for this.
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
No, it does nothing of the sort. It only verifies that the files on disk match or not what was contained in the rpms. It can not take into account the rpm scripts, I think.
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?
There are some verification options in YaST, but I don't know if that is what you saw. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)