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

  • Bug#1095369: marked as pending in python-dicompylercore

    From =?UTF-8?B?w4l0aWVubmUgTW9sbGllcg==?@21:1/5 to All on Sun Feb 16 10:20:01 2025
    Control: tag -1 pending

    Hello,

    Bug #1095369 in python-dicompylercore 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/med-team/python-dicompylercore/-/commit/a57a216182a0830a19673f6dc20056ba244d36bb

    ------------------------------------------------------------------------ skip-tight-comparison.patch: new: skip a failing test with numpy 2.x.

    This is the second part of the #1095369 correction.

    Closes: #1095369 ------------------------------------------------------------------------

    (this message was generated automatically)
    --
    Greetings

    https://bugs.debian.org/1095369

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Feb 16 10:20:01 2025
    Processing control commands:

    tag -1 pending
    Bug #1095369 [src:python-dicompylercore] python-dicompylercore: FTBFS: AssertionError
    Added tag(s) pending.

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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Feb 16 11:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Sun, 16 Feb 2025 09:49:48 +0000
    with message-id <E1tjbHY-00BKH8-Lt@fasolo.debian.org>
    and subject line Bug#1095369: fixed in python-dicompylercore 0.5.6-3
    has caused the Debian Bug report #1095369,
    regarding python-dicompylercore: FTBFS: AssertionError
    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.)


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

    Received: (at submit) by bugs.debian.org; 7 Feb 2025 12:12:23 +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=-111.1 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,
    META_ATTENDEES_DBSPAM1,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, 497; hammy, 150; neutral, 471; spammy,
    0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--trixie, 0.000-+--sk:dh_auto
    Return-path: <sanvila@debian.org>
    Received: from muffat.debian.org ([2607:f8f0:614:1::1274:33]:47548)