• Bug#1066872: mozjs102: Fails to build with Python 3.12

    From Jeremy =?UTF-8?Q?B=C3=ADcha?=@21:1/5 to All on Thu Mar 14 20:00:01 2024
    Source: mozjs102
    Version: 102.15.1-3
    Severity: serious
    Tags: ftbfs sid
    X-Debbugs-CC: cjs@packages.debian.org
    Control: affects -1 src:cjs

    mozjs102 fails to build with Python 3.12 as default. We fixed similar
    issues with mozjs115. Could we please convince cjs to switch to
    mozjs115?

    https://launchpad.net/ubuntu/+source/mozjs102/102.15.1-3

    Thank you,
    Jeremy BĂ­cha

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat Mar 16 00:30:01 2024
    Processing control commands:

    forwarded -1 https://src.fedoraproject.org/rpms/mozjs102/c/72d6ad552c3087fafb475370b1a8a7?branch=rawhide
    Bug #1066872 [src:mozjs102] mozjs102: Fails to build with Python 3.12
    Set Bug forwarded-to-address to 'https://src.fedoraproject.org/rpms/mozjs102/c/72d6ad552c3087fafb475370b1a8a7?branch=rawhide'.

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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bastian Germann@21:1/5 to All on Sat Mar 16 00:30:01 2024
    Control: forwarded -1 https://src.fedoraproject.org/rpms/mozjs102/c/72d6ad552c3087fafb475370b1a8a7?branch=rawhide

    Fedora has included two patches to fix this.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Wed Apr 10 20:10:01 2024
    This is a multi-part message in MIME format...

    Your message dated Wed, 10 Apr 2024 17:59:41 +0000
    with message-id <E1rucEX-006DnE-WA@fasolo.debian.org>
    and subject line Bug#1066872: fixed in mozjs102 102.15.1-4
    has caused the Debian Bug report #1066872,
    regarding mozjs102: Fails to build with Python 3.12
    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.)


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

    Received: (at submit) by bugs.debian.org; 14 Mar 2024 18:48:04 +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=-5.0 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
    DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,
    RCVD_IN_SORBS_WEB,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 15; hammy, 107; neutral, 22; spammy,
    0. spammytokens: hammytokens:0.000-+--H*F:D*canonical.com,
    0.000-+--H*rp:D*canonical.com, 0.000-+--H*RU:sk:jeremy.,
    0.000-+--Hx-spam-relays-external:sk:jeremy.,
    0.000-+--H*rp:U*jeremy.bicha
    Return-path: <jeremy.bicha@canonical.com>
    Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]:525