• Bug#1103962: RM: raku [arm64 armel armhf] -- ROM; depends on moarvm whi

    From Dominique Dumont@21:1/5 to All on Wed Apr 23 10:00:01 2025
    XPost: linux.debian.ports.arm

    Package: ftp.debian.org
    Severity: normal
    X-Debbugs-Cc: raku@packages.debian.org, debian-arm@lists.debian.org, debian-arm@lists.debian.org
    Control: affects -1 + src:raku
    User: ftp.debian.org@packages.debian.org
    Usertags: remove
    User: debian-arm@lists.debian.org
    Usertags: arm64 armel armhf
    User: debian-arm@lists.debian.org
    Usertags: arm arm64 armel armhf
    Control: clone -1 -2
    Control: retitle -2 RM: dh-raku [arm64 armel armhf] -- ROM; depends on moarvm which is not provided on arm*

    Currently, moarvm and nqp packages have a bug on arm that can't be
    reproduced. This bug triggers a random crash and can trip build on
    nqp, rakudo and all raku modules.

    The short term solution is to disable build on all arm arches until
    this bug is sorted out. This means that trixie will be released
    without raku on ARM. Hopefully, we will be able to enable again builds
    on arm later on.

    moarvm was removed from testing and unstable on arm*. Now all raku
    modules must also be removed from arm architectures.

    All the best

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Emanuele Rocca@21:1/5 to Dominique Dumont on Wed Apr 23 10:20:01 2025
    XPost: linux.debian.ports.arm

    Hi Dominique,

    On 2025-04-23 09:55, Dominique Dumont wrote:
    Currently, moarvm and nqp packages have a bug on arm that can't be reproduced. This bug triggers a random crash and can trip build on
    nqp, rakudo and all raku modules.

    Is there a BTS entry for this bug? Is it known upstream? Where can we
    find out more about it?

    Thanks,
    Emanuele

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dominique Dumont@21:1/5 to Rocca on Wed Apr 23 11:20:01 2025
    XPost: linux.debian.ports.arm

    Hi

    On Wednesday, 23 April 2025 10:11:46 Central European Summer Time Emanuele Rocca wrote:
    On 2025-04-23 09:55, Dominique Dumont wrote:
    Currently, moarvm and nqp packages have a bug on arm that can't be reproduced. This bug triggers a random crash and can trip build on
    nqp, rakudo and all raku modules.

    Is there a BTS entry for this bug?

    No.

    Is it known upstream?

    Yes, by Timo Paulssen who is also the maintainer of all raku packages for Debian. I act as sponsor.

    Where can we
    find out more about it?

    Timo should be able to answer.

    All the best

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dominique Dumont@21:1/5 to debian@alteholz.de on Wed Apr 23 12:50:01 2025
    On Wed, 23 Apr 2025 09:34:34 +0000 (UTC) Thorsten Alteholz <debian@alteholz.de> wrote:
    I am not really sure why you request the removal of an arch:all package from
    a specific architecture.

    I admit I'm quite confused about the removal from specific arch process.

    Anyway, I logged this bug because https://tracker.debian.org/pkg/raku-zef page mentions:

    excuses:
    Migration status for raku-zef (0.13.8-1 to 0.13.8-2): BLOCKED: Rejected/ violates migration policy/introduces a regression
    Issues preventing migration:
    ∙ ∙ removing raku-zef/0.13.8-1/arm64 from testing makes raku/6.d.7/arm64
    uninstallable

    The last line makes me believe that it was necessary to remove raku from arm arch even if it's an arch all package.

    So closing this bug again ...

    Sorry about the mess...

    All the best

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)