Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Sandro Tosi Newsgroups: linux.debian.maint.python Subject: Help needed: numpy FTBFS with newer setuptools Date: Mon, 31 Oct 2022 06:10:01 +0100 Message-ID: X-Original-To: debian-python X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Oct 31 05:05:02 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.73 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-ua1-f52.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: ACrzQf1Dpf0c3e0ncEX4bwBmgsZ3oTAAmRzZs/QbfqPVqNXjIO4xLo0g 8Fi3bCcz8vWSDWiMC9FcDhgxJqb7vQcmUSq0Znt1ubPWTbU= X-Google-SMTP-Source: AMsMyM50PXN7lW2gWR+bbx9DJVZXTEkMdgVv+OL6TtuMCYt+8NE67vVQ264fObJNGOUep9FZCLtB+Ufjde4FDEVMJqA= X-Received: by 2002:ab0:204b:0:b0:3b5:7f97:3000 with SMTP id g11-20020ab0204b000000b003b57f973000mr3857853ual.13.1667192678905; Sun, 30 Oct 2022 22:04:38 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailing-List: archive/latest/20421 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAB4XWXzQ92Fjyu8uiNyUV5jWE0=qd68oGdMkwGtFBt8or7S4Hw@mail.gmail.com Approved: robomod@news.nic.it Lines: 36 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 31 Oct 2022 01:04:13 -0400 X-Original-Message-ID: Xref: csiph.com linux.debian.maint.python:14569 Hello, with the recent upload of setuptools/65.3.0 (and following) in unstable, numpy FTBFS[1]. The reason is that numpy build system (both used internally and by other packages) customizes setuptools/distutils. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020135 Upstream is unwilling[2] to continue patching their build system in response to setuptools changes. While there may be merit in their position, this leaves Debian in a state where numpy is unbuildable, and the freeze is approaching. [2] https://github.com/numpy/numpy/issues/21114 I tried to look at addressing this problem myself, but i had no luck, so i'm here to ask for the help of the wider python team to address this issue. A build log from my machine is available here[3] (error is at the end of the page, as usual). [3] https://paste.debian.net/1259001/ My plan would be, once this is addressed, to package the latest 1.23.4 in experimental, ask for an archive rebuild and later upload 1.23.x to unstable in time for the freeze. This plan is currently on hold due to [1]. Thanks in advance for your help! -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi