On 17.07.17 16:26, Marcus Gould wrote:
Hi,

(Please note that I've joined this mailinglist since this thread started)


              Re: [opensuse-arm] tumbleweed updates for armv6hl ?
              <https://lists.opensuse.org/opensuse-arm/2017-07/msg00021.html>

      * From: Michael Ströder <michael@xxxxxxxxxxxx>
      * Date: Thu, 13 Jul 2017 11:51:56 +0200
      * Message-id: <[email protected]
        <https://lists.opensuse.org/opensuse-arm/2017-07/msg00021.html>>

    Dirk Müller wrote:

        Unfortunately armv6hl is in a pretty bad state because it is still
        built in qemu emulation, and noone maintains that emulation layer.
        [..]
        Over the long run we need to find a different solution though (which
        could be dropping it alltogether, in the worst case). For now I take
        it as a positive sign that someone does actually care about it being
        available :-)


    Hmm, I have several rpi1 boards and it would be nice if they do not
    turn into
    Elektroschrott. The video output does not work but I use them
    headless anyway.

    Until two weeks ago zypper dup worked but currently the update is
    stuck with
    this message:

    Problem: libzypp-16.9.0-1.1.armv6hl requires libsolv-tools = 0.6.27,
    but this
    requirement
    cannot be provided
    deleted providers: libsolv-tools-0.6.27-2.1.armv6hl
    Solution 1: Following actions will be done:
    deinstallation of libzypp-16.9.0-1.1.armv6hl
    deinstallation of zypper-1.13.25-1.1.armv6hl
    Solution 2: keep obsolete libsolv-tools-0.6.27-2.1.armv6hl
    Solution 3: break libzypp-16.9.0-1.1.armv6hl by ignoring some of its
    dependencies

I'd like to register myself as a RaspPi+armv6hl user who cares about the repo being available :-) and mention that I am also seeing similar sorts of issues:

    # *zypper dup --no-allow-vendor-change -d*
    Warning: You are about to do a distribution upgrade with all enabled
    repositories. Make sure these repositories are compatible before you
    continue. See 'man zypper' for more information about this command.
    Loading repository data...
    Reading installed packages...
    Computing distribution upgrade...
    36 Problems:
    Problem: nothing provides zypper(auto-agree-with-product-licenses)
    needed by SUSEConnect-0.3.2-1.1.armv6hl
    Problem: libzypp-16.9.0-1.1.armv6hl requires libsolv-tools = 0.6.27,
    but this requirement cannot be provided
    Problem: yast2-perl-bindings-3.2.0-1.1.armv6hl requires perl =
    5.24.0, but this requirement cannot be provided
    Problem: yast2-core-3.2.2-1.1.armv6hl requires perl = 5.24.0, but
    this requirement cannot be provided
    Problem: vim-8.0.566-2.1.armv6hl requires perl = 5.24.0, but this
    requirement cannot be provided
    Problem: yast2-perl-bindings-3.2.0-1.1.armv6hl requires perl =
    5.24.0, but this requirement cannot be provided
         [3 More]
    Problem: yast2-core-3.2.2-1.1.armv6hl requires perl = 5.24.0, but
    this requirement cannot be provided
         [11 More]
    Problem: yast2-perl-bindings-3.2.0-1.1.armv6hl requires perl =
    5.24.0, but this requirement cannot be provided
         [13 More]
    Problem: yast2-core-3.2.2-1.1.armv6hl requires perl = 5.24.0, but
    this requirement cannot be provided

    Problem: nothing provides zypper(auto-agree-with-product-licenses)
    needed by SUSEConnect-0.3.2-1.1.armv6hl
      Solution 1: keep obsolete SUSEConnect-0.3.0-1.1.armv6hl
      Solution 2: break SUSEConnect-0.3.2-1.1.armv6hl by ignoring some
    of its dependencies

    Choose from above solutions by number or skip, retry or cancel
    [1/2/s/r/c] (c):

If I sit tight and wait, will this get fixed in some future maintenance?

Dirk and Andreas are currently working to fix up all builds. We're in the process to switch compilation over to native builds (previously it was all emulated with bitrotting emulation).

As always, helping hands are always welcome. If you see build failures for armv6 here:

  https://build.opensuse.org/project/show/openSUSE:Factory:ARM

and you have the time to google for failures and create OBS submitrequests to fix them, that would be great and helps to keep the target alive :).


Thanks,

Alex
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to