Bug#953008: talloc: ftbfs with python3.8
Source: talloc Version: 2.3.0-3 Severity: grave python3.8 is now default python3 in unstable, while talloc is unable to build with it. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#949259: buster-pu: package linux/4.19.67-2+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu In Jessie and Buster cycles, we finished the process from FP32 to FPXX. And I test the whole Buster archive, and be sure that all packages are built with FPXX now. Since FPXX uses only even FPRs, then wastes other 16 FPRs. And another problem of FPXX is that it may need help of RAM for some operation. FP64 also has better co-operation with MIPS SIMD Architecture (MSA). The CONFIG_MIPS_O32_FP64_SUPPORT has just enabled in master branch of kernel-team/linux[2]. Is it possible to enable this config for buster? So we can start the migration to FP64 now, and release it with bullseye. Otherwise we will have to start this work after bullseye released. [1]. https://web.archive.org/web/20180828210612/https://dmz- portal.mips.com/wiki/MIPS_O32_ABI_-_FR0_and_FR1_Interlinking https://salsa.debian.org/kernel-team/linux/merge_requests/199
