On 6/6/25 13:31, Samuel Thibault wrote:
I just had the first successful nvidia-cuda-toolkit 12.4.0 build on amd64
;-) If ppc64el and arm64 don't fail (slow builds, happens in qemu), I should
be able to upload that to experimental/NEW tomorrow.
It seems to have gone fine? Is something else neede
Source: hwloc-contrib
Version: 2.12.0-3
Severity: serious
Please stop building src:hwloc-contrib for ppc64el. NVIDIA has
discontinued ppc64el driver support, and after the driver removal
there is no longer any package in testing providing libnvidia-ml.so.1
on ppc64el, making libhwloc-contrib-plugi
Control: fixed -1 7.2.0~b1-1
On 6/6/25 05:57, Yue Gui wrote:
Source: papi
Version: 7.1.0-5
Severity: serious
Why the high severity? The RISC-V FTBFS is not a regression ...
My solution to this issue:
The issue is caused by the lack of RISC-V support in papi. Therefore, it
can be resolved by
ing
an arch:all-only-build, it cannot record the files that it does *not*
install and therefore dh_missing complains.
Let's just make that less complicated ...
AndreasFrom 79d98c8219f050639c4a2678e8ff9fd3a2695e15 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Wed, 21 May 2025
Control: severity -1 important
Control: tag -1 moreinfo
On 2/27/25 05:06, Andreas Beckmann wrote:
On 2/26/25 10:27, Thomas Goirand wrote:
Package: nvidia-driver
Version: 545.23.06-4
I've just uploaded 535.216.03-2~bpo12+1, that should work for 6.12.
In unstable and stable-proposed-up
Control: tag -1 pending
On 5/11/25 13:08, Matthias Klose wrote:
many nvidia related packages still build-depend on g++-12. Is this
something to change for the trixie release, or is this targeted to
future releases?
I hope they only get this transitively via a
B-D: nvidia-cuda-toolkit-gcc
Control: tag -1 moreinfo
Control: severity -1 important
On 4/22/25 09:41, Andreas Beckmann wrote:
On 4/22/25 08:24, david wrote:
Package: firmware-nvidia-gsp
Version: 535.216.01-1~deb12u1
The following packages have unmet dependencies:
nvidia-kernel-dkms : Depends: firmware-nvidia-gsp
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2025-2
On 4/22/25 08:24, david wrote:
Package: firmware-nvidia-gsp
Version: 535.216.01-1~deb12u1
The following packages have unmet dependencies:
nvidia-kernel-dkms : Depends: firmware-nvidia-gsp (= 535.183.01) or
firmware-nvidia-gsp-535.183.01 but it is not
installab
Source: hwloc-contrib
Version: 2.12.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
while rebuilding all packages build-depending on nvidia-cuda-toolkit,
hwloc-contrib did FTBFS with a failing test:
FAIL: hwloc_type_sscanf
===
Control: severity -1 normal
On 4/12/25 13:45, Charlemagne Lasse wrote:
Source: nvidia-graphics-drivers
Version: 535.216.03-3
The 535 LTSB driver series is supported until June 2026
https://docs.nvidia.com/datacenter/tesla/drivers/index.html
Andreas
Control: severity -1 important
On 4/14/25 13:26, Lucas Nussbaum wrote:
Source: cccl
Version: 2.2.0-3
This package builds only arch:all packages, therefore I'm downgrading
the severity. It is not supposed to work on i386.
Will add a B-D on architecture-is-64bit to make this explicit.
Andrea
On 4/11/25 20:58, Jonas Nothhelfer wrote:
I tried to build to compile the nvidia cuda toolkit 12.2.2-2 by just
changing the DEFAULT_GCC_VERSION in the rules.defs from 12 to 13 and it
ran through without any issues. Is there a particular reason why it has
not been done yet. Am I missing somethin
Control: tag -1 moreinfo unreproducible
Hi Santiago,
On 3/12/25 17:32, Santiago Vila wrote:
Package: src:pyopencl
Version: 2024.1-3
Build on :
Device cpu-skylake-avx512-AMD EPYC 9R14 failed to build the program
If you could not reproduce the bug please contact me privately, as I
am willi
Followup-For: Bug #1101409
Hi,
I just did an undelayed NMU in order not to block the new dkms.
Andreas
>From d54049f6890eaf89b50f2b29b9cc37a0693d255f Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Fri, 4 Apr 2025 09:40:04 +0200
Subject: [PATCH] release dahdi-linux (1:3.1.0+git20230
quick anti autorm ping
I somehow lost track reviewing the antpm updates ...
Andreas
Followup-For: Bug #1097326
still need to check the spirv tests regression
reas
>From fe296f9dfe6266c6ff241eb45e360a940b5d4c0e Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Thu, 6 Feb 2025 16:48:06 +0100
Subject: [PATCH 1/4] dkms.conf: drop duplicate module
---
debian/dkms.conf.in | 4
1 file changed, 4 deletions(-)
diff --git a/debian/dkms.conf.in b/debian/dkms.
Control: reassign -1 src:osmocom-dahdi-linux 0.0~git20241003.b2ea348-1
Control: close -1 0.0~git20241003.b2ea348-2
On Sun, 23 Mar 2025 11:48:45 +0100 Helmut Grohne wrote:
Package: dahdi-source,osmocom-dahdi-source
Severity: serious
User: debian...@lists.debian.org
The packages dahdi-source a
On 3/8/25 21:07, Jeremy Sowden wrote:
From 8abc78fcab6c128da8cb53510bd8c149a40137cd Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Wed, 19 Feb 2025 22:06:29 +0100
Subject: [PATCH 4/6] Fix building twice in a row
This shouldn't have been necessary. The .oo.d files are listed i
On 3/5/25 14:42, Sudip Mukherjee wrote:
Move it to DELAYED/0 please. :)
Done and pushed the commits and tag to salsa.
Andreas
Hi Eric,
On 2/11/25 14:21, Andreas Beckmann wrote:
thanks for explaining whats' going on here, now I also understand the
need for your other "weird" dependencies.
The current kernel headers in sid and experimental now ship the BTF bits
and tools (e.g. linux-headers-* depend
13 support part from upstream's commit as
that didn't apply cleanly.
Andreas
>From 3f6aaeed9fe2df55ed9dd4b5fa99d5e8ea2c5c8a Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Wed, 5 Mar 2025 11:37:25 +0100
Subject: [PATCH 3/4] Fix build with v6.12 kernel
Closes: #1089505
---
debian
Followup-For: Bug #1098896
Control: tag -1 pending
Hi,
I've just uploaded my proposed changes as a NMU to DELAYED/5.
Please let me know if I should delay it longer.
Andreas
>From 530b140e3e076079993e9c046ae673212c30c2a9 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Wed, 5 Mar
Package: rtpengine-kernel-dkms
Version: 12.5.1.24-1
Severity: serious
https://ci.debian.net/packages/r/rtpengine/testing/amd64/58458753/
116s == /var/lib/dkms/rtpengine/12.5.1.24/build/make.log ==
116s DKMS (dkms-3.1.5) make.log for rtpengine/12.5.1.24 for kernel
6.12.12-amd64 (x
00:00:00 2001
From: Andreas Beckmann
Date: Mon, 24 Feb 2025 22:11:40 +0100
Subject: [PATCH 1/6] dkms.conf: Declare BUILD_EXCLUSIVE_KERNEL_MIN="4.3"
The skcipher interface was introduced in Linux v4.3.
---
debian/gost-crypto-dkms.dkms | 4
1 file changed, 4 insertions(+)
diff -
Control: found -1 6.13.5-1~exp1
with pahole available, the next script is missing:
/usr/src/linux-headers-@KVERS@/tools/bpf/resolve_btfids/resolve_btfids
DKMS (dkms-3.1.5) make.log for dkms_test/1.0 for kernel 6.13-amd64 (x86_64)
Sat Mar 1 01:09:31 UTC 2025
Building module(s)
# command: make -
Followup-For: Bug #1076456
A patch for this issue as well as patches for supporting up to Linux
v6.13 are available in
https://salsa.debian.org/debian/iptables-netflow/-/merge_requests/4
I have only tested that the module builds again for all the kernels in
oldstable, stable, testing, sid, experi
Control: tag -1 wontfix
On 3/1/25 22:01, Santiago Vila wrote:
Package: src:libthrust
Version: 2.1.1-1
The following configuration files were considered but not accepted:
/usr/share/cmake/libcudacxx/libcudacxx-config.cmake, version: 2.2.0.0
src:libthrust, src:cub, src:libcudacxx are
Please clean up all the 'pahole: not found' bugs, that's #1098706 in
src:linux and an upload for that is on the way to sid.
Thanks.
Andreas
Control: notfound -1 6.13.5-1~exp1
Control: fixed -1 6.13.5-1~exp1
Control: tag -1 - moreinfo unreproducible
On 3/1/25 07:57, Salvatore Bonaccorso wrote:
I would like to see this fixed ASAP for unstable but I have now
postponed my 6.12.17-1 upload. It would be great if you can confirm if
there w
- restore compatibility with some older kernels by correcting version
constraints
Andreas
>From d3ea20dc911d3298e9e92f085463993c75b6de76 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Thu, 27 Feb 2025 04:21:16 +0100
Subject: [PATCH 1/2] Simplify -dkms package installation
Don't hard
On 2/26/25 10:27, Thomas Goirand wrote:
Package: nvidia-driver
Version: 545.23.06-4
Severity: serious
Hi,
Thanks for maintaining this package.
I'm running Bookworm with the 6.12.9+bpo-amd64 kernel. In there, I did my own
backport of nvidia-graphics-drivers 545.23.06-4~bpo12+1. At least, X-Wind
breakage earlier.
Restrict the -dkms autopkgtest to amd64 (the only architecture where the
-dkms package is built).
Thanks for considering.
Andreas
>From 96f3c3c7dc01d56a87353e8b4d494fea853bf2ff Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Thu, 20 Feb 2025 14:56:53 +0100
Subj
Control: fixed -1 3.8-1
On 2/26/25 10:20, Russell Coker wrote:
https://qa.debian.org/excuses.php?package=libsemanage
It says that libsemanage is not migrating due to bug #1091109.
That bug never affected version 3.8 as the issue was addressed upstream. I
accidentally dropped the changelog ent
doing funny 'find, ln, cp, tar xf, echo' dances to get
to the headers from the -dkms or -source package.
Thanks for considering.
Andreas
>From 2c9f312ec07859876d071164b412d75a93877768 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Wed, 19 Feb 2025 21:51:16 +0100
Subject: [PA
Followup-For: Bug #1089497
While you fix this, please also set BUILD_EXCLUSIVE_KERNEL_MIN in
dkms.conf to document the oldest supported kernel version.
See the attached patch for this.
Thanks
Andreas
>From d35e0b78ceb0ea42ad0652a1b53814b308815e59 Mon Sep 17 00:00:00 2001
From: Andreas Beckm
Control: severity -1 important
downgrading the severity temporarily as the 535.230.02 upstream release
misses the .run file for ppc64el
Andreas
Source: linux
Version: 6.12.16-1
Severity: serious
Hi,
the last linux upload causes regressions building (probably) all
out-of-tree dkms modules, e.g.
DKMS (dkms-3.1.5) make.log for dkms_test/1.0 for kernel 6.12.16-amd64 (x86_64)
Sun Feb 23 00:18:07 UTC 2025
Building module(s)
# command: make -
On 1/10/25 17:41, Emilio Pozuelo Monfort wrote:
nvidia-cuda-toolkit-gcc depends on g++-12, which is likely not going to be
a part of trixie. Please update to g++-13 or preferably g++-14.
This will need more time as it requires new upstream releases to be
packaged.
Andreas
Control: severity -1 important
downgrading the severity temporarily as the 535.230.02 upstream release
misses the .run file for ppc64el
Andreas
On 2/19/25 19:13, Vincas Dargis wrote:
Yep, works with 6.12.13-1.
Thanks for confirming!
Andreas
Control: tag -1 patch
On Fri, 13 Sep 2024 15:51:12 +0200 Andreas Beckmann wrote:
trickle FTBFS with 64-bit time_t on 32-bit platforms (e.g. armel, armhf,
but not i386 (keeps its 32-bit time_t):
I've pushed a tentative fix to salsa. It builds fine on amd64/i386/armhf
(nothing else
Followup-For: Bug #1095902
Control: tag -1 patch
Control: fixed -1 debian/2.13.14-1
Attached are patches for bullseye and bookworm that adjust the
preprocessor condition in the same way as it was fixed upstream in
2.13.14.
Tested in bullseye/bookworm chroots with the bullseye kernel installed.
Package: lttng-modules-dkms
Version: 2.12.5-1+deb11u1
Severity: serious
Control: found -1 2.13.9-1
Hi,
the bullseye kernel at some point seems to have enabled
-Werror=implicit-function-declaration, causing the module to now fail to
build:
DKMS make.log for lttng-modules-2.12.5 for kernel 5.10.0-
Followup-For: Bug #1076456
Control: found -1 2.6-4
That is an incorrect constraint:
#if LINUX_VERSION_CODE >= KERNEL_VERSION(5,12,0) || LINUX_VERSION_CODE >=
KERNEL_VERSION(5,10,220)
you probably want
#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,12,0)) || \
((LINUX_VERSION_CODE >= KER
---
This is probably nothing that needs to be fixed.
Instead I'm documenting the fact in dkms.conf by setting
BUILD_EXCLUSIVE_KERNEL_MIN="6.6". You may want to add a comment with an
explanation.
Andreas
>From 92a1b779da1a4926e229d2c95c981d63e93fcc54 Mon Sep 17 00:00:00 2001
Hi Eric,
thanks for explaining whats' going on here, now I also understand the
need for your other "weird" dependencies.
On 2/11/25 12:32, Eric Long wrote:
`extract-linux` from kernel source code tries to do it at first (it only
supports bzImage, so another custom binary runs to extract vmlin
dkms/mimic/0.6.3+ds/build clean
make[1]: Entering directory '/usr/src/linux-headers-6.12.13-amd64'
CLEAN /var/lib/dkms/mimic/0.6.3+ds/build/Module.symvers
make[1]: Leaving directory '/usr/src/linux-headers-6.12.13-amd64'
# exit code: 0
# elapsed time: 00:00:00
Andreas
&
Followup-For: Bug #1095643
Control: tag -1 patch
Merge request:
https://salsa.debian.org/debian-mobcom-team/osmocom-dahdi-linux/-/merge_requests/1
CI passes except for a Lintian error:
E: osmocom-dahdi-linux source: debian-watch-file-pubkey-file-is-missing
[debian/watch]
The autopkgtests pass o
Source: osmocom-dahdi-linux
Version: 0.0~git20241003.b2ea348-1
Severity: serious
Hi,
src:osmocom-dahdi-linux has a few problems:
The -dkms package only builds for $(uname -r) ignoring any -k arguments
given to dkms. This was not noticed since the package did not have dkms
autopkgtests enabled. T
Package: vpb-driver-source
Version: 4.2.61-1.4
Severity: serious
vpb-driver-source fails to build a module for Linux 6.1 in bookworm and
Linux 6.12 in trixie.
Shouldn't there a corresponding -dkms package for this kernel module?
I: Trying to build vpb-driver-source for 6.1.0-29-amd64
Extracting
clude/common-rules.mk:56: kdist_build] Error 2
ESC[7mBUILD FAILED!
ESC[27mSee /var/cache/modass/cloop-src.buildlog.6.1.0-29-amd64.1738806017 for
details.
Build failed. Press Return to continue...
Andreas
>From 78d70ff156c2be3233397f471e89de3bd5df8b46 Mon Sep 17 00:00:00 2001
From: An
Package: python3-numpy
Version: 1:2.2.2+ds-2
Severity: serious
Control: block 1095213 with -1
Control: block 1095214 with -1
Hi,
while rebuilding pycuda for the Numpy 2 transition, I noticed these
changes in the generated dependencies (debdiff wdiff format):
Depends: ..., python3-numpy (>= [-1:1
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2024-0131,
On 1/15/25 14:11, Johannes Schauer Marin Rodrigues wrote:
Phew, I'm glad I asked before sinking more time into this.
try again with rc7
Andreas
Package: dkms
Version: 3.1.0-1
Severity: serious
Tags: upstream
dkms_autoinstaller no longer propagates errors
working on getting this fixed upstream
On 1/15/25 13:53, Johannes Schauer Marin Rodrigues wrote:
aarch64-linux-gnu-ld: read in flex scanner failed
known issue with the kernel in experimental: #1092969
wait and retest once there is a newer -rc in experimental
Andreas
Package: rapiddisk-dkms
Version: 9.1.0-3
Severity: serious
Tags: upstream
Control: forwarded -1 https://github.com/pkoutoupis/rapiddisk/issues/190
DKMS make.log for rapiddisk-9.1.0 for kernel 6.11-rc5-amd64 (x86_64)
Thu Sep 12 11:51:16 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.11
Source: linux
Version: 6.13~rc6-1~exp1
Severity: serious
building dkms modules for 6.13 in experimental fails with:
...
# LD [M] dm-writeboost.ko
x86_64-linux-gnu-ld -r -m elf_x86_64 -z noexecstack --no-warn-rwx-segments
--build-id=sha1 -T /usr/src/linux-headers-6.13-rc6-amd64/ -o dm-writebo
Followup-For: Bug #1091161
A few rounds of cvise produced this minimized reproducer:
extern "C" double copysign(double, double);
double ccosh_x;
struct type {
double x;
double y;
};
template struct complex {
complex(T, T);
complex() = default;
T real() { return data.x; }
T imag() { r
On 1/6/25 16:38, Adrian Bunk wrote:
Source: nvidia-cuda-toolkit
Version: 12.2.1-1
The following packages have unmet dependencies:
liboss4-salsa-asound2 : Conflicts: libasound2
Conflicts: libasound2t64
Argh ...
As part of the 64-bit time_t changes the library wa
Followup-For: Bug #1074913
In case anyone is still interested, I've pushed a fix for this FTBFS to
Git. Tested on amd64/i386/armel/armhf/arm64/ppc64el.
Andreas
Control: affects -1 + src:slepc src:fenics-dolfinx src:mpich
On Sat, 21 Dec 2024 19:19:43 +0200 Drew Parsons wrote:
This is a delicate issue. The strict version test is in the upstream
headers. I imagine they have their reasons for making it so.
I don't think so ...
Anyway, if you want to
Control: retitle -1 elk: FTBFS with libxaw 1.0.16: error: passing argument 2 of
‘XawListChange’ from incompatible pointer type
On 11/30/24 19:11, Santiago Vila wrote:
I've found that the attached patch would fix the ftbfs problem,
but I'd like a second opinion.
libxaw-1.0.16 has this API chan
Package: smifb2-dkms
Version: 2.4.0-2
Severity: serious
Tags: upstream
Since Linux v6.12-rc1 commit "drm: Remove struct
drm_mode_config_funcs.output_poll_changed"
https://github.com/torvalds/linux/commit/446d0f4849b101bfc35c0d00835c3e3a4804616d
the module fails to build.
Excerpt from make.log:
.
Package: sl-modem-dkms
Version: 2.9.11~20110321-19
Severity: serious
Tags: upstream
Since Linux v6.12-rc1 no_llseek is finally gone, causing the module build
to fail.
The corresponding Linux commit is "[tree-wide] finally take no_llseek out"
https://github.com/torvalds/linux/commit/cb787f4ac0c2e4
Package: rtpengine-kernel-dkms
Version: 12.5.1.15-1
Severity: serious
Tags: upstream
DKMS make.log for rtpengine/12.5.1.15 for kernel 6.12.3-rt-amd64 (x86_64)
Sat Dec 7 23:22:21 UTC 2024
make: Entering directory '/usr/src/linux-headers-6.12.3-rt-amd64'
CC [M] /var/lib/dkms/rtpengine/12.5.1.15/
Package: openvpn-dco-dkms
Version: 0.0+git20240712-1
Severity: serious
Tags: upstream fixed-upstream patch
Control: forwarded -1
https://github.com/OpenVPN/ovpn-dco/commit/0935edd8569b2a90eb5d66b83742f969e91a60f2
Since Linux commit: "netdev_features: convert NETIF_F_LLTX to dev->lltx"
https://git
Package: openafs-modules-dkms
Version: 1.8.13-1
Severity: serious
Tags: upstream
tail of dkms.log:
CC [M]
/var/lib/dkms/openafs/1.8.13/build/src/libafs/MODLOAD-6.12.3-amd64-SP/osi_vm.o
CC [M]
/var/lib/dkms/openafs/1.8.13/build/src/libafs/MODLOAD-6.12.3-amd64-SP/osi_export.o
CC [M]
/va
Package: langford-dkms
Version: 0.0.20130228-6.3
Severity: serious
Tags: upstream
Since Linux v6.12-rc1 no_llseek is finally gone, causing the module build
to fail.
The corresponding Linux commit is "[tree-wide] finally take no_llseek out"
https://github.com/torvalds/linux/commit/cb787f4ac0c2e439
Package: iptables-netflow-dkms
Version: 2.6-7
Severity: serious
Tags: upstream
Control: forwarded -1 https://github.com/aabc/ipt-netflow/issues/237
Since Linux v6.12-rc2 asm/unaligned.h has moved to linux/unaligned.h,
causing the module build to fail.
DKMS make.log for ipt-netflow/2.6 for kernel
Package: gost-crypto-dkms
Version: 0.3.5-1
Severity: serious
Tags: upstream
Since Linux v6.12-rc2 asm/unaligned.h has moved to linux/unaligned.h,
causing the module build to fail.
DKMS make.log for gost-crypto/0.3.5 for kernel 6.12.3-amd64 (x86_64)
Sat Dec 7 23:22:28 UTC 2024
make: Entering dire
Package: evdi-dkms
Version: 1.14.6+dfsg-1
Severity: serious
Tags: upstream fixed-upstream patch
Control: forwarded -1
https://github.com/DisplayLink/evdi/commit/934e31ec29ca7abcc8fcc1d6104214885c56acf0
DKMS make.log for evdi/1.14.6+dfsg for kernel 6.12.3-amd64 (x86_64)
Sat Dec 7 23:24:06 UTC 202
Package: digimend-dkms
Version: 13-1
Severity: serious
Tags: upstream
Control: forwarded -1
https://github.com/DIGImend/digimend-kernel-drivers/issues/706
Since Linux v6.12-rc2 asm/unaligned.h has moved to linux/unaligned.h,
causing the module build to fail.
DKMS make.log for digimend/13 for ker
On 12/2/24 23:07, Adrian Bunk wrote:
Package mpi-c was not found in the pkg-config search path.
This was changed in:
https://salsa.debian.org/science-team/mpich/-/commit/2f0d0190d12923c482df5ba7eacd8da721f8d0a3
mpich had stopped providing variants of mpi-c.pc etc. so I removed the
dangling
Control: severity -1 important
On 10/7/24 18:22, Louis-Philippe Véronneau wrote:
The following removed libraries were found in this package:
pipes: .upstream-tests/utils/libcudacxx/test/config.py:13
pipes: libcxx/utils/libcxx/test/config.py:13
This very much looks like it is in the parts that
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2024-0126
Cont
On Wed, 23 Oct 2024 20:53:14 +0200 Michael Biebl wrote:
I've made an NMU to DELAYED/3 fixing the two open RC bugs.
s390-tools is orphaned (#1084987), so you should rather do a QA upload
(and update the maintainer to QA) instead of a NMU.
Andreas
Control: severity -1 important
Control: retitle -1 lmod: FTBFS: testsuite fails if 'hostname -f' fails
On Tue, 26 Sep 2023 15:19:12 +0200 Lucas Nussbaum wrote:
Source: lmod
Version: 8.6.19-1
During a rebuild of all packages in sid, your package failed to build
on amd64.
This is a testsuite fa
Followup-For: Bug #1084356
Control: reopen -1
I can still reproduce the FTBFS reported by Santiago by rebuilding
1.15.1-3 in an up-to-date sid pbuilder environment.
Andreas
On 10/9/24 19:29, Bastian Blank wrote:
Package: nvidia-graphics-drivers
Version: 535.183.06-1
https://ci.debian.net/packages/n/nvidia-graphics-drivers/testing/arm64/52858087/#S6
https://ci.debian.net/packages/n/nvidia-graphics-drivers/testing/arm64/52858087/#L1941
302s In file included from
Followup-For: Bug #1077217
A patch can possibly be derived from xtrx-dkms which had a similar
problem:
https://bugs.debian.org/1077678
https://github.com/myriadrf/xtrx_linux_pcie_drv/issues/19
https://github.com/myriadrf/xtrx_linux_pcie_drv/pull/20
Andreas
On 9/15/24 23:11, Andreas Beckmann wrote:
not a regression in nvidia-nccl, the version in testing nowadays ftbfs
similarily
This is caused by glibc 2.38 which enhanced
/usr/include/aarch64-linux-gnu/bits/math-vector.h
with
...
#if __GNUC_PREREQ(9, 0)
# define __ADVSIMD_VEC_MATH_SUPPORTED
On 8/19/24 03:36, Andreas Beckmann wrote:
On 18/08/2024 21.24, Paul Gevers wrote:
arm64 FTBFS with
/usr/include/aarch64-linux-gnu/bits/math-vector.h(96): error: identifier
"__Float32x4_t" is undefined
typedef __Float32x4_t __f32x4_t;
not a regression in nvidia-nccl, the
Source: trickle
Version: 1.08+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
trickle FTBFS with 64-bit time_t on 32-bit platforms (e.g. armel, armhf,
but not i386 (keeps its 32-bit time_t):
...
gcc -DHAVE_CONFIG_H -I. -D_LA
On 9/13/24 10:12, Wolfgang Schnitker via pkg-nvidia-devel wrote:
please don't forget to apply this bpo path also to nvidia-tesla-470
driver package because this is still a part of the bookworm series.
good point ;-)
Andreas
On 9/9/24 22:23, Stuart Prescott wrote:
Another month has passed - is there something that others can help with
here?
That was a llvm-17 regresssion that got fixed today ;-)
pocl just got built successfully on arm64 ;-)
Andreas
Followup-For: Bug #1078750
still debugging ...
Control: tag -1 pending
src:nvidia-graphics-drivers for bookworm-backports is in BACKPORTS-NEW.
On 9/4/24 17:15, Stefano Zacchiroli wrote:
On Tue, Sep 03, 2024 at 06:35:06PM +0200, fr.hame...@gmail.com wrote:
To solve it have applied the patches given by nvidia the 21 of July
here :
https://fo
Package: devscripts
Version: 2.23.4+deb12u1
Severity: serious
Control: fixed -1 2.23.6
Control: found -1 2.23.4
bts in bookworm does not work with mail-submit.debian.org:587
This is a regression over 2.22.2~bpo11+1 which I used in bullseye
It is fixed in sid. (Commit dd2ac025db69bc78ca62391153ce4e
Package: ola,ola-rdm-tests
Version: 0.10.9.nojsmin-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your packages failed to install
because they try to overwrite each others files.
>From the attached log (scroll to the
Followup-For: Bug #1075310
Control: tag -1 patch pending
Hi,
I've pushed a fix to salsa and uploaded it as a NMU to DELAYED/10.
Please let me know if I should delay it longer.
Andreas
Followup-For: Bug #1078454
Control: reopen -1
Control: reassign -1 golang-tags.cncf-container-device-interface-dev 0.8.0-4
Control: retitle -1 golang-tags.cncf-container-device-interface-dev: missing
Breaks+Replaces:
golang-github-container-orchestrated-devices-container-device-interface-dev (<<
Package: golang-github-distribution-reference-dev
Version: 0.6.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' f
Package: libsfst-dev
Version: 1.5.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
On 18/08/2024 21.24, Paul Gevers wrote:
Source: nvidia-nccl
ppc64el uploaded
arm64 FTBFS with
/usr/include/aarch64-linux-gnu/bits/math-vector.h(96): error: identifier
"__Float32x4_t" is undefined
typedef __Float32x4_t __f32x4_t;
^
/usr/include/aarch64-linux-gnu/bits/math-vector.
Source: gcc-13-doc
Version: 13.2.0-1
Severity: serious
Control: block 1078158 with -1
Please create src:gcc-14-doc for documenting the current default
compiler src:gcc-14
Thanks
Andreas
Control: tag -1 help
Control: retitle -1 pocl: FTBFS on arm64: Clang link test FAILED.
On 15/08/2024 13.13, Sebastian Ramacher wrote:
/usr/lib/llvm-17/bin/llc: error: unable to get target for 'unknown', see
--version and --triple.
make[1]: [debian/rules:88: override_dh_auto_configure] Error 1
Package: libgenomicsdb1
Version: 1.5.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to ove
1 - 100 of 1379 matches
Mail list logo
