• Bug#1077314: unblock: pytest-jupyter/0.9.1-2

    From Julian Gilbey@21:1/5 to All on Sun Jul 28 11:20:01 2024
    XPost: linux.debian.bugs.dist

    Package: release.debian.org
    Severity: normal
    User: release.debian.org@packages.debian.org
    Usertags: unblock

    Please unblock package pytest-jupyter

    [ Reason ]
    It's failing the autopkgtest on riscv64 quite badly. It's a new
    package, and I have no idea where in the toolchain the problem lies;
    given that pytest also fails on this architecture, it's probably not pytest-jupyter itself that is problematic. It's also quite probable
    that all of the newer versions of the jupyter suite will also fail on
    riscv64 because of the same reason, but we'll find out...

    [ Impact ]
    The newer versions of the jupyter suite all depend on pytest-jupyter
    for their autopkgtests.

    [ Tests ]
    N/A

    [ Risks ]
    The Jupyter suite may not work on riscv64.

    [ Checklist ]
    N/A

    [ Other info ]
    Will I need to request unblocks for riscv64 for each of the other
    Jupyter packages separately if they also fail the autopkgtests on
    riscv64 once I have uploaded them?

    Thanks!

    unblock pytest-jupyter/0.9.1-2
    # Perhaps instead:
    # unblock pytest-jupyter/0.9.1-2/riscv64

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to Julian Gilbey on Mon Jul 29 09:10:01 2024
    This is a multi-part message in MIME format...

    Your message dated Mon, 29 Jul 2024 08:04:13 +0100
    with message-id <Zqc-7SPMDRsb1cm9@d-and-j.net>
    and subject line Re: Bug#1077314: unblock: pytest-jupyter/0.9.1-2
    has caused the Debian Bug report #1077314,
    regarding unblock: pytest-jupyter/0.9.1-2
    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.)


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

    Received: (at submit) by bugs.debian.org; 28 Jul 2024 09:10:34 +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=-117.3 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_NONE,
    SPF_NONE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,
    USER_IN_DKIM_WHITELIST,XMAILER_REPORTBUG autolearn=ham
    autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 10; hammy, 127; neutral, 37; spammy,
    0. spammytokens:
    hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
    0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
    0.000-+--H*RT:311, 0.000-+--H*RT:108
    Return-path: <jdg@debian.org>
    Received: from stra