[opensuse-arm] armv7l vs. armv7hl rpm arch
Hi, to avoid package incompatibilities with other rpm based distros, I am about to switch the rpm architecture to "armv7hl" again. "armv7l" will be used as backward compatibility, so it should not cause trouble. However, I will wait for the new gcc with new runtime linker path before doing an entire rebuild. Just in case you wonder why we will have both rpm architectures for some time. We will not hack the kernel to report (the not existing) armv7hl architecture, we will go with a hack in rpm instead assuming that armv7l hardware is always armv7hl. In case we want to have armv7l (or armv7nhl or whatever) later on in parallel, we will need to enhance the rpm dependency scripts to extend the keys similar to the 64bit approach. But there is no cross distro standard atm. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 24.05.2012, at 22:37, Adrian Schröter <adrian@suse.de> wrote:
Hi,
to avoid package incompatibilities with other rpm based distros, I am about to switch the rpm architecture to "armv7hl" again. "armv7l" will be used as backward compatibility, so it should not cause trouble.
However, I will wait for the new gcc with new runtime linker path before doing an entire rebuild. Just in case you wonder why we will have both rpm architectures for some time.
We will not hack the kernel to report (the not existing) armv7hl architecture, we will go with a hack in rpm instead assuming that armv7l hardware is always armv7hl.
In case we want to have armv7l (or armv7nhl or whatever) later on in parallel, we will need to enhance the rpm dependency scripts to extend the keys similar to the 64bit approach. But there is no cross distro standard atm.
Sounds good to me :) Alex
bye adrian
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 24/05/2012 22:37, Adrian Schröter a écrit :
Hi,
to avoid package incompatibilities with other rpm based distros, I am about to switch the rpm architecture to "armv7hl" again. "armv7l" will be used as backward compatibility, so it should not cause trouble.
Could not we keep the armv7l and have armv7hl as compatibility? Maybe this way is fine for openSUSE but not for other distros? They may also do some hacks to be compatible. Which distro use armv7l, armv7hl or other? I think we should use the right name (armv7l?) and not use a bad name because some other distro use it. Guillaume
However, I will wait for the new gcc with new runtime linker path before doing an entire rebuild. Just in case you wonder why we will have both rpm architectures for some time.
We will not hack the kernel to report (the not existing) armv7hl architecture, we will go with a hack in rpm instead assuming that armv7l hardware is always armv7hl.
In case we want to have armv7l (or armv7nhl or whatever) later on in parallel, we will need to enhance the rpm dependency scripts to extend the keys similar to the 64bit approach. But there is no cross distro standard atm.
bye adrian
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hallo Adrian, Am 24.05.2012 22:37, schrieb Adrian Schröter:
to avoid package incompatibilities with other rpm based distros, I am about to switch the rpm architecture to "armv7hl" again. "armv7l" will be used as backward compatibility, so it should not cause trouble.
However, I will wait for the new gcc with new runtime linker path before doing an entire rebuild. Just in case you wonder why we will have both rpm architectures for some time.
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? 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
On 06/04/2012 04:19 PM, Andreas Färber wrote:
Hallo Adrian,
Am 24.05.2012 22:37, schrieb Adrian Schröter:
to avoid package incompatibilities with other rpm based distros, I am about to switch the rpm architecture to "armv7hl" again. "armv7l" will be used as backward compatibility, so it should not cause trouble.
However, I will wait for the new gcc with new runtime linker path before doing an entire rebuild. Just in case you wonder why we will have both rpm architectures for some time. 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?
Regards, Andreas
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): Bye, CzP -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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
Am Dienstag, 5. Juni 2012, 16:35:50 schrieb Andreas Färber: ...
That new zypper is then able to install packages from armv7hl/. The
zypp people refused a patch to make it forward compatible, because it is just needed temporary. So you need to update libzypp, libsolv and zypper manually with rpm to the armv7hl architecture for once.
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
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 11.06.2012 16:42, schrieb Adrian Schröter:
Am Dienstag, 5. Juni 2012, 16:35:50 schrieb Andreas Färber: ...
That new zypper is then able to install packages from armv7hl/. The
zypp people refused a patch to make it forward compatible, because it is just needed temporary.
So you need to update libzypp, libsolv and zypper manually with rpm to the armv7hl architecture for once.
That's not the end of the story though: We also need a rebuild of quite a few packages to actually appear in the armhl/ folder, including omnipresent libgcc47. 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
Am Montag, 11. Juni 2012, 21:09:04 schrieb Andreas Färber:
Am 11.06.2012 16:42, schrieb Adrian Schröter:
Am Dienstag, 5. Juni 2012, 16:35:50 schrieb Andreas Färber: ...
That new zypper is then able to install packages from armv7hl/. The
zypp people refused a patch to make it forward compatible, because it is just needed temporary.
So you need to update libzypp, libsolv and zypper manually with rpm to the armv7hl architecture for once.
That's not the end of the story though: We also need a rebuild of quite a few packages to actually appear in the armhl/ folder, including omnipresent libgcc47.
I triggered a rebuild a week ago. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 11.06.2012 23:15, schrieb Adrian Schröter:
Am Montag, 11. Juni 2012, 21:09:04 schrieb Andreas Färber:
Am 11.06.2012 16:42, schrieb Adrian Schröter:
[...] you need to update libzypp, libsolv and zypper manually with rpm to the armv7hl architecture for once.
That's not the end of the story though: We also need a rebuild of quite a few packages to actually appear in the armhl/ folder, including omnipresent libgcc47.
I triggered a rebuild a week ago.
I won't dispute that, but take a look yourself: http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/standard/ar... (No libgcc-*) https://build.opensuse.org/package/show?package=gcc47&project=openSUSE%3AFactory%3AARM (standard armv7l "succeeded") Maybe you only triggered a rebuild for "gcc" or something? Alex wanted to wait with a full repository rebuild until some icecream issues were resolved, is that done already? 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
Am Montag, 11. Juni 2012, 23:38:49 schrieb Andreas Färber:
Am 11.06.2012 23:15, schrieb Adrian Schröter:
Am Montag, 11. Juni 2012, 21:09:04 schrieb Andreas Färber:
Am 11.06.2012 16:42, schrieb Adrian Schröter:
[...] you need to update libzypp, libsolv and zypper manually with rpm to the armv7hl architecture for once.
That's not the end of the story though: We also need a rebuild of quite a few packages to actually appear in the armhl/ folder, including omnipresent libgcc47.
I triggered a rebuild a week ago.
I won't dispute that, but take a look yourself:
http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/standard/ar... (No libgcc-*)
https://build.opensuse.org/package/show?package=gcc47&project=openSUSE%3AFactory%3AARM (standard armv7l "succeeded")
Maybe you only triggered a rebuild for "gcc" or something?
Alex wanted to wait with a full repository rebuild until some icecream issues were resolved, is that done already?
we have published a repo the last time on 2nd June. Most likely because of the never ending qemu package build ... I can enforce a publish tomorrow (by disabling the build for some seconds). -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Dienstag, 12. Juni 2012, 00:09:19 schrieb Adrian Schröter:
Am Montag, 11. Juni 2012, 23:38:49 schrieb Andreas Färber:
Am 11.06.2012 23:15, schrieb Adrian Schröter:
Am Montag, 11. Juni 2012, 21:09:04 schrieb Andreas Färber:
Am 11.06.2012 16:42, schrieb Adrian Schröter:
[...] you need to update libzypp, libsolv and zypper manually with rpm to the armv7hl architecture for once.
That's not the end of the story though: We also need a rebuild of quite a few packages to actually appear in the armhl/ folder, including omnipresent libgcc47.
I triggered a rebuild a week ago.
I won't dispute that, but take a look yourself:
http://download.opensuse.org/repositories/openSUSE:/Factory:/ARM/standard/ar... (No libgcc-*)
https://build.opensuse.org/package/show?package=gcc47&project=openSUSE%3AFactory%3AARM (standard armv7l "succeeded")
Maybe you only triggered a rebuild for "gcc" or something?
Alex wanted to wait with a full repository rebuild until some icecream issues were resolved, is that done already?
we have published a repo the last time on 2nd June. Most likely because of the never ending qemu package build ...
I can enforce a publish tomorrow (by disabling the build for some seconds).
I did this now. A new tree is out there. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
Adrian Schröter -
Alexander Graf -
Andreas Färber -
Guillaume Gardet -
Peter Czanik