1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1108142: nom: doesn't work with ruby 3

    From Holger Levsen@21:1/5 to All on Sat Jun 21 14:20:01 2025
    Package: nom
    Version: 0.1.5-6
    Severity: serious
    Tags: pending


    nom 0.1.5-6 doesnt work with ruby3 in trixie, as observed by myself
    now and previously in https://github.com/blinry/nom/issues/19.

    To fix this two small changes are needed as described in the upstream
    issue. I have these changes already done & tested locally and will
    upload them to unstable shortly.


    --
    cheers,
    Holger

    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
    ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
    ⠈⠳⣄

    The moon landing 50 years ago was paid by taxes, while Bezos space trip was paid by not paying taxes.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmhWoiYACgkQCRq4Vgaa qhwBvxAAgm5bLFxY/Wt5vt00lMUU/RR4yAnNpXFhLpGZh4DCMF0dscRrWyFYTeNJ o8HMQEuerYAqo42KYFZTRQLv9fb69XlG4HS4GEz0nHCK3tE4c7A55GRSIxBwn2Ow ZqNhkUlB4QHUNP4Y245J03DuDpz/jrRvUkNKgXXI+SiG01BBtfP/m9/RKXmupfM/ vOlvyA4kPY9u4JCLo8owXHMHI/YQJIDWmQUyTiRijN3PBQ+Kw1gQgufNnPyJWzwd adhVyngTf48jwlGbSz6NdCbl7r+HDAoi2QbnsNIhs3UPzWc8W+nb7kiVWwNzVT1N QaqC6uag9YDiMsYFoQAa2wJPYx29A3+jBTnPAuydYN1Lu1JqDrfPHaPMFcVowsXq e2oH+RkGnpZj8qq5bBlX0HT+9MhqWtCMp38s6Z6cVySWiaehyQeL6P97jo5i1KVR pR3m1gjd4D+hZisnbcF7tFPMgVe2eQBeRyUxTb0wNBLu22Dx8bZegAzonXkkaAmq KZ3G1WqHpCHta1JTH5rvbCnSm9olUuZ4DjzwJA6upPZSWJpv5FH/0xih0uSLfMDF
    2dbSR5GbYh
  • From Debian Bug Tracking System@21:1/5 to All on Sat Jun 21 15:30:02 2025
    This is a multi-part message in MIME format...

    Your message dated Sat, 21 Jun 2025 13:19:19 +0000
    with message-id <[email protected]>
    and subject line Bug#1108142: fixed in nom 0.1.5-7
    has caused the Debian Bug report #1108142,
    regarding nom: doesn't work with ruby 3
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected]
    immediately.)


    --
    1108142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108142
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 21 Jun 2025 12:14:40 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
    (2024-03-25) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-21.6 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,FROMDEVELOPER,HAS_PACKAGE,KHOP_HELO_FCRDNS,
    PGPSIGNATURE,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,
    RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
    SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no
    version=4.0.1-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 15; hammy, 147; neutral, 28; spammy,
    3. spammytokens:0.963-+--paid, 0.941-+--paying, 0.879-+--taxes
    hammytokens:0.000-+--trixie, 0.000-+--H*ct:application,
    0.000-+--H*ct:protocol, 0.000-+--H*ct:micalg, 0.000-+--H*ct:signed Return-path: <[email protected]>
    Received: from mail.holgerlevsen.