• Processed: Bug#1093439 marked as pending in libatteanx-serializer-rdfa-

    From Debian Bug Tracking System@21:1/5 to All on Sun Mar 2 13:30:01 2025
    Processing control commands:

    tag -1 pending
    Bug #1093439 [src:libatteanx-serializer-rdfa-perl] libatteanx-serializer-rdfa-perl: FTBFS: Failed test 'no (unexpected) warnings (via done_testing)'
    Added tag(s) pending.

    --
    1093439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093439
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonas Smedegaard@21:1/5 to All on Sun Mar 2 13:30:01 2025
    Control: tag -1 pending

    Hello,

    Bug #1093439 in libatteanx-serializer-rdfa-perl reported by you has been fixed in the
    Git repository and is awaiting an upload. You can see the commit
    message below and you can check the diff of the fix at:

    https://salsa.debian.org/perl-team/modules/packages/libatteanx-serializer-rdfa-perl/-/commit/a86d6dbf9c8bd5f68964dbfd4292bd8a284a8ee1

    ------------------------------------------------------------------------
    add patch 1001 to avoid superfluous use of Test::Modern; closes: bug#1093439, thanks to Santiago Vila
    ------------------------------------------------------------------------

    (this message was generated automatically)
    --
    Greetings

    https://bugs.debian.org/1093439

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Mar 2 13:40:02 2025
    This is a multi-part message in MIME format...

    Your message dated Sun, 02 Mar 2025 12:36:31 +0000
    with message-id <E1toiYZ-009GYT-5p@fasolo.debian.org>
    and subject line Bug#1093439: fixed in libatteanx-serializer-rdfa-perl 0.110-3 has caused the Debian Bug report #1093439,
    regarding libatteanx-serializer-rdfa-perl: FTBFS: Failed test 'no (unexpected) warnings (via done_testing)'
    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 owner@bugs.debian.org
    immediately.)


    --
    1093439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093439
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 18 Jan 2025 19:24:35 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-121.2 required=4.0 tests=ALL_TRUSTED,BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FROMDEVELOPER,HAS_PACKAGE,
    USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 150; neutral, 268; spammy,
    0. spammytokens: hammytokens:0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--trixie, 0.000-+--sk:dh_auto,
    0.000-+--H*F:U*sanvila
    Return-path: <sanvila@debian.org>
    Received: from muffat.debian.org ([2607:f8f0:614:1::1274:33]:40152)
    from C=NA,ST=NA