Am 05.06.2012 09:19, schrieb Peter Czanik:
On 06/04/2012 04:19 PM, Andreas Färber wrote:
I've managed to update to an rpm package that doesn't need --ignorearch via wget and rpm -Uhv --ignorearch (it got published to armv7hl/).
However, manually updating zypper does not seem to work since my current zypper wants libsolv-tools 0.0.0 and the latest armv7hl/ libzypp wants libsolv-tools 0.1.0 and I don't want to bust zypper. ;-)
Also, if the new zypper (still blocked last time I checked) gets published to armv7hl/ then currently deployed zypper up/dup won't find that version.
So what's the upgrade strategy there? Are you going to symlink select packages into armv7l so that upgrading works? Or are you going to publish instructions or a shell script and consider it a one-time breakage? Or is some other neat solution coming up?
I also ran into this. Is there any way to update my ARM system? Right now I get:
rm:~ # zypper -v dup Verbosity: 1 Initializing Target Checking whether to refresh metadata for factory Retrieving: repomd.xml [done] Loading repository data... Reading installed packages... Computing distribution upgrade... Force resolution: No Computing upgrade... 74 Problems: Problem: nothing provides ld-linux-armhf.so.3 needed by coreutils-8.16-4.1.armv7l Problem: nothing provides ld-linux-armhf.so.3 needed by cpio-2.11-17.2.armv7l Problem: nothing provides ld-linux-armhf.so.3 needed by cronie-1.4.8-36.1.armv7l [...] Problem: nothing provides ld-linux-armhf.so.3 needed by xz-5.0.3-11.2.armv7l Problem: nothing provides ld-linux-armhf.so.3 needed by libaugeas0-0.10.0-2.2.armv7l Problem: nothing provides ld-linux-armhf.so.3 needed by cronie-1.4.8-36.1.armv7l
Problem: nothing provides ld-linux-armhf.so.3 needed by coreutils-8.16-4.1.armv7l Solution 1: keep obsolete coreutils-8.14-5.1.armv7l Solution 2: break coreutils by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c):
I think I got past that one some time ago using rpm -Uhv --ignorearch --force path/to/glibc-xxx.rpm (that I had downloaded from the repository's armv7hl/ folder). One piece of advice that I can pass on, if zypper offers you to uninstall libgcc46 as a solution to upgrade to libgcc47, do NOT do so, it will brick your system. I recovered by extracting the library on another host (with File Roller) to the SD card with the rootfs. Last night I managed to get the new zypper installed on one of my machines. From what I remember, I did something like: osc getbinaries openSUSE:Factory:ARM zypper standard armv7l osc getbinaries openSUSE:Factory:ARM libzypp standard armv7l osc getbinaries openSUSE:Factory:ARM libsolv standard armv7l zypper rm libzypp # required libsolv-tools 0.0.0 rpm -Uhv binaries/libsolv-tools-xxx.rpm rpm -Uhv binaries/libzypp-xxx.rpm # required libsolv-tools 0.1.0 rpm -Uhv binaries/zypper-xxx.rpm That new zypper is then able to install packages from armv7hl/. The downside is that all armv7l packages are shown as "(System Packages)" in `zypper se -i -s` (they don't get recognized as stemming from suse-factory repository, so apparently it only considers armv7hl/). They don't seem to automatically get crossgraded where possible, so I went through the list manually to check on where we are. FWIW on my minimal installation there's around 208 packages still armv7l not yet updatable, among those perl and python due to their dependency trees. Checked by trying `zypper up packagename`. On my newly set up machine I didn't get as far yet. No handy osc command, for one. ;) Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org