Am 28.12.2013 14:58, schrieb Guillaume Gardet:
Le 23/12/2013 14:27, Andreas Färber a écrit :
Am 11.12.2013 16:11, schrieb Guillaume Gardet:
Le 04/12/2013 17:33, G. Heim a écrit :
Do you have any idea when your patch will be available in the official repositories? I do not see it yet on http://download.opensuse.org/ports/update/13.1/armv7hl/ nor on http://download.opensuse.org/ports/armv7hl/distribution/13.1/repo/oss/suse/a....
It is on the way:
- Maintenance request accepted: https://build.opensuse.org/request/show/208720
- Request to get it in 13.1:Update repo in review state: https://build.opensuse.org/request/show/210488
That request is marked accepted, but `zypper dup` gets stuck with "Illegal instruction" and not much working any more(*) and I don't spot a glibc RPM in: http://download.opensuse.org/ports/update/13.1/armv7hl/
You will be stuck with that unless you install the right RPM manually. Because zypper, yast or rpm will try to use the broken glibc before trying to download and install the new one.
Moreover, the new RPM is not yet out for ARM whereas it is for x86. Not sure why.
[...]
We must wait for the new glibc in 13.1 ARM update. :(
With Dirk's help I have managed to rescue my AC100 system:
$ osc getbinaries openSUSE:13.1:Update patchinfo.2349 ports aarch64
downloads all ports binaries of the update that includes glibc.
Mount the SD card and copy over .armv7hl.rpm and .noarch.rpm files. Chroot into the SD card as usual and install these RPMs:
/> rpm -Fvh /path/to/*.rpm
In my case the original update seems to have failed during PAM update, so that booting with the fixed glibc worked but login didn't. :/
The solution was to complete the update with `zypper up` inside the chroot. (Remember, you can't proceed with `zypper dup` as it would revert to the broken glibc.) After all update'able packages were installed, `zypper dup` (followed by 'n' to abort) gave me a short list of packages that needed downgrading via `zypper in --oldpackage foo-x.y.z`. In the end, `zypper dup` should only show glibc and nscd that you had manually installed, which - again - you should not touch before the glibc packages are officially published.
One problem to note is that apparently there is currently an inconsistency in the repositories with gnome-menus at 3.10.1 but gnome-menus-branding-openSUSE at 3.10.0. Deinstalling gnome-menus-branding-openSUSE and installing gnome-menus-branding-upstream seemed to work as conflict resolution.
So far so good, system is usable again. Yay!
My AC100 was configured to run XFCE via DISPLAYMANAGER="gdm". Unfortunately the screen stayed black and after a while a white screen
Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please contact a system administrator
appeared.
/var/log/gdm/:0.log had some warning about gpio-keys and duplicate .../event0, so that I dropped my xorg.conf in favor of a 20-fbdev.conf snippet from the JeOS package's config.sh. That resolved the log entry, but that screen is still with me.
I have worked through `zypper se -i -s | grep '(System'`, `zypper rm`ing any leftover or non-updatable packages except for glibc*, nscd, kernel-tegra-ac100 and Mozilla{Firefox,Thunderbird}. `zypper ve` shows nothing. I've disabled the newly installed AppArmor just to be sure.
Any ideas what else to check?
Regards, Andreas