On May 13, 2025 5:08:42 AM GMT+02:00, Peter Green wrote:
>Package: rust-rustix
>Version: 0.38.37-2
>Severity: serious
>
>The autopkgtests for rust-rustix are failing on i386.
>
>> 1337s backend::vdso::test_vdso stdout
>> 1337s 1337s thread 'backend::vdso::test_vdso' panicked at
>> sr
Processing commands for cont...@bugs.debian.org:
> tags 1105191 + security
Bug #1105191 [screen] screen: TTY Hijacking while Attaching to a Multi-User
Session (CVE-2025-46802)
Added tag(s) security.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1105191: https:/
Source: xen
Version: 4.20.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for xen.
CVE-2024-28956[0]:
| x86: Indirect Target Selection
If you fix the vulnerability
Package: screen
Version: 4.9.1-1
Severity: grave
Justification: user security hole
X-Debbugs-Cc: dani.be...@ubuntu.com
Dear Maintainer,
Screen 5.0.1 is now published with the assortment of security fixes as well as
some other issues spotted and resolved:
- CVE-2025-46805: do NOT send signal
Package: rust-rustix
Version: 0.38.37-2
Severity: serious
The autopkgtests for rust-rustix are failing on i386.
1337s backend::vdso::test_vdso stdout
1337s
1337s thread 'backend::vdso::test_vdso' panicked at src/backend/linux_raw/vdso.rs:428:28:
1337s called `Option::unwrap()` on a
Your message dated Tue, 13 May 2025 02:45:10 +
with message-id
and subject line Bug#1103906: fixed in edk2 2025.02-8
has caused the Debian Bug report #1103906,
regarding qemu-efi-aarch64: Secure Boot regression for some arm64 VMs
to be marked as done.
This means that you claim that the proble
Cyril Brulebois (2025-05-12):
> Unless you tell me otherwise I'll stick to testing then uploading d-i
> with the ABI bumped to 35. (And it can still be rejected from pu-NEW
> anyway?)
Local testing looked good, so src:debian-installer is on its way.
Please let me know if and when I should move o
Dear Release team,
I finally managed to fix 1064135 (test failures on arm64 and other
architectures) by enforcing signed chars with the following patch.
+--- r-cran-bigmemory-4.6.4.orig/configure
r-cran-bigmemory-4.6.4/configure
+@@ -39,3 +39,4 @@ fi
+
+ echo "${FLAGS}" > src/Makevars
+ e
Source: jool
Severity: serious
Tags: ftbfs
Version: 4.1.14-2
Hi,
your package fails to build from source on arch:all. Please check
the logs, for example:
https://buildd.debian.org/status/fetch.php?pkg=jool&arch=all&ver=4.1.14-2&stamp=1746123609&raw=0
The last few lines of that log are:
dh
Source: libimage-imlib2-perl
Version: 2.03-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Hi,
your package's autopkgtest fails on all architectures. Please see
the excuses here: https://qa.debian.org/excuses.php?package=libimage-imlib2-perl
and the autopkgtest logs, f
Hi,
Jonathan Wiltshire (2025-05-12):
> We discussed briefly just now and decided that:
>
> - as it's "just" amd64 watchdog and w83977f_wdt modules, and
It's been a while since I last toyed with watchdogs (and those needed
explicit actions to be enabled anyway), but I'd expect those not to be
s
Package: pique
Version: 1.1-1
Severity: serious
X-Debbugs-CC: debian-rele...@lists.debian.org
Hi,
pique 1.1-1 cannot migrate to testing [1], because it depends on
plink1.9; and plink1.9 is not installable on arm64.
AFAIK britney's configuration currently requires packages to be
installable o
Processing commands for cont...@bugs.debian.org:
> fixed 1104010 5:8.0.0-1
Bug #1104010 {Done: Adrian Bunk } [src:redis] redis:
CVE-2025-21605
Marked as fixed in versions redis/5:8.0.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1104010: https://bugs.debia
On Mon, May 12, 2025 at 11:02:56PM +0200, Salvatore Bonaccorso wrote:
> On Mon, May 12, 2025 at 10:34:51PM +0200, Salvatore Bonaccorso wrote:
> > Control: severity -1 serious
> >
> > Hi Robert,
> >
> > On Mon, May 12, 2025 at 04:38:19PM +0100, Robert Shearman wrote:
> > > Package: src:linux
> > >
Your message dated Mon, 12 May 2025 21:05:12 +
with message-id
and subject line Bug#1104204: fixed in btm 0.10.2+20250107-5
has caused the Debian Bug report #1104204,
regarding btm FTBFS with the nocheck build profile
to be marked as done.
This means that you claim that the problem has been d
Your message dated Mon, 12 May 2025 21:05:30 +
with message-id
and subject line Bug#1105134: fixed in cyme 2.2.0+dfsg-2
has caused the Debian Bug report #1105134,
regarding cyme FTBFS with the nocheck build profile
to be marked as done.
This means that you claim that the problem has been deal
On Mon, May 12, 2025 at 10:34:51PM +0200, Salvatore Bonaccorso wrote:
> Control: severity -1 serious
>
> Hi Robert,
>
> On Mon, May 12, 2025 at 04:38:19PM +0100, Robert Shearman wrote:
> > Package: src:linux
> > Version: 6.1.137-1
> > Severity: important
> > X-Debbugs-Cc: r...@graphiant.com
> >
Your message dated Mon, 12 May 2025 20:44:29 +
with message-id
and subject line Bug#1105136: fixed in pbseqlib 5.3.5+dfsg-10
has caused the Debian Bug report #1105136,
regarding pbseqlib FTBFS with the nocheck build profile
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> retitle -1 dh-elpa: upgrade fails: cannot overwrite non-directory ... with
> directory
Bug #1104178 [dh-elpa] elpa-doom-themes: upgrade fails: cannot overwrite
non-directory ... with directory
Changed Bug title to 'dh-elpa: upgrade fails: cannot overwrite non-direc
Control: retitle -1 dh-elpa: upgrade fails: cannot overwrite non-directory ...
with directory
Xiyue Deng writes:
> Hi Sean,
>
> Sean Whitton writes:
>
>> Hello,
>>
>> On Sun 27 Apr 2025 at 03:25am -07, Xiyue Deng wrote:
>>
>>> Interestingly, I cannot reproduce this with "apt dist-upgrade" whic
Processing control commands:
> severity -1 serious
Bug #1105164 [src:linux] linux-image-6.1.0-35-amd64: watchdog kernel module
load errors with "Bad message"
Severity set to 'serious' from 'important'
--
1105164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105164
Debian Bug Tracking Syst
Processing control commands:
> tag -1 pending
Bug #1105136 [src:pbseqlib] pbseqlib FTBFS with the nocheck build profile
Added tag(s) pending.
--
1105136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1105136 in pbseqlib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/med-team/pbseqlib/-/commit/f6ad1f33cbf4acbf26ec12966683f
Processing control commands:
> close -1 0.8.0-4
Bug #1105174 [src:rkward] src:rkward: fails to migrate to testing for too long
Marked as fixed in versions rkward/0.8.0-4.
Bug #1105174 [src:rkward] src:rkward: fails to migrate to testing for too long
Marked Bug as done
--
1105174: https://bugs.de
Source: rkward
Version: 0.8.0-3
Severity: serious
Control: close -1 0.8.0-4
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as havi
Processing control commands:
> close -1 1.6.0-2
Bug #1105173 [src:ectrans] src:ectrans: fails to migrate to testing for too long
Marked as fixed in versions ectrans/1.6.0-2.
Bug #1105173 [src:ectrans] src:ectrans: fails to migrate to testing for too long
Marked Bug as done
--
1105173: https://bu
Source: ectrans
Version: 1.5.1-1
Severity: serious
Control: close -1 1.6.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as hav
.org/CVERecord?id=CVE-2025-24495
[2] https://security-tracker.debian.org/tracker/CVE-2025-20012
https://www.cve.org/CVERecord?id=CVE-2025-20012
[3]
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20250512
Please adjust the affected versions in the BT
Processing control commands:
> severity -1 important
Bug #1104753 [libxmlrpc-core-c3-dev] libxmlrpc-core-c3-dev: Wrong expat
dependencies
Severity set to 'important' from 'serious'
--
1104753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104753
Debian Bug Tracking System
Contact ow...@bug
Control: severity -1 important
Hi!
On Mon, 2025-05-12 at 15:24:30 +0200, Guillem Jover wrote:
> Control: severity -1 serious
> On Sat, 2025-05-10 at 13:16:33 +0200, Alexandre Detiste wrote:
> > severity 1104753 important
>
> I'm bumping the severity back to serious, because there was not
> expl
Your message dated Mon, 12 May 2025 18:34:35 +
with message-id
and subject line Bug#1072792: fixed in nvidia-graphics-drivers 550.90.07-1
has caused the Debian Bug report #1072792,
regarding nvidia-graphics-drivers: CVE-2024-0090, CVE-2024-0091, CVE-2024-0092
to be marked as done.
This means
Your message dated Mon, 12 May 2025 18:35:05 +
with message-id
and subject line Bug#1072800: fixed in nvidia-open-gpu-kernel-modules
550.90.07-1
has caused the Debian Bug report #1072800,
regarding nvidia-open-gpu-kernel-modules: CVE-2024-0090, CVE-2024-0091,
CVE-2024-0092
to be marked as do
Your message dated Mon, 12 May 2025 17:49:43 +
with message-id
and subject line Bug#1104846: fixed in txt2man 1.7.1-5
has caused the Debian Bug report #1104846,
regarding [:space:] instead of [[:space:]] annoys new gawk
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 12 May 2025 17:04:15 +
with message-id
and subject line Bug#1105163: fixed in zutils 1.14-5
has caused the Debian Bug report #1105163,
regarding zutils: -4 upload breaks piuparts
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
On 5/12/25 17:30, Helmut Grohne wrote:
I'm attaching updated test cases as well as another patch.
thanks - much appreciated, and uploaded.
Regards,
Daniel
On 12 May 2025 at 12:06, Charles Plessy wrote:
| Thanks a lot Dirk for putting me in the right direction!
|
| So I persevered a bit more with src/Makevars and ran R CMD INSTALL from
| outside Debian's build system first, which leads me to figure out that
| src/Makevars was unconditionally over
Package: zutils
Version: 1.14-4
Severity: serious
Justification: piuparts failure breaks testing migration
Tags: patch
X-Debbugs-Cc: jspri...@debian.org
User: helm...@debian.org
Usertags: dep17
Hi,
Jochen made me aware that zutils didn't pass piuparts. When I came up
with the previous patch, I fo
Your message dated Mon, 12 May 2025 14:35:13 +
with message-id
and subject line Bug#1105159: fixed in open-vm-tools 2:12.5.0-2
has caused the Debian Bug report #1105159,
regarding open-vm-tools: insecure file handling vulnerability (CVE-2025-22247)
to be marked as done.
This means that you cl
Processing commands for cont...@bugs.debian.org:
> found 1105159 2:12.5.0-1
Bug #1105159 [src:open-vm-tools] open-vm-tools: insecure file handling
vulnerability (CVE-2025-22247)
Marked as found in versions open-vm-tools/2:12.5.0-1.
> found 1105159 2:12.2.0-1+deb12u2
Bug #1105159 [src:open-vm-tool
Processing control commands:
> tags -1 ftbfs patch
Bug #1102068 [src:libfabric] libfabric: FTBFS on 32-bit arches: ofi_cma.h:
error: passing argument 2 of 'ofi_consume_iov' from incompatible pointer type
Added tag(s) patch.
--
1102068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102068
D
Source: libfabric
Followup-For: Bug #1102068
Control: tags -1 ftbfs patch
It looks like Gonzalo Silvalde Blanco's patch (salsa MR) at
https://salsa.debian.org/hpc-team/libfabric/-/merge_requests/4
should be able to fix the bug.
Processing control commands:
> severity -1 serious
Bug #1104753 [libxmlrpc-core-c3-dev] libxmlrpc-core-c3-dev: Wrong expat
dependencies
Severity set to 'serious' from 'important'
--
1104753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104753
Debian Bug Tracking System
Contact ow...@bugs.
Source: open-vm-tools
Version: 2:11.2.5-2+deb11u3
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole
X-Debbugs-Cc: t...@security.debian.org
Description
==
CVE-2025-22247: VMware Tools contains an inse
Source: flox
Version: 0.10.3-1
Severity: serious
Justification: debci
test_first_last from test_properties.py is regularly failing in debci
testing on riscv64, e.g.
https://ci.debian.net/data/autopkgtest/testing/riscv64/f/flox/60337814/log.gz
https://ci.debian.net/data/autopkgtest/testing/riscv64/
Looks good to me.
Antonio Russo 于2025年5月12日 周一20:10写道：
> On 2025-05-12 00:27, Yue Gui wrote:
> >
> > My solution to this issue:
> > The `test_lock_contention` test, which simulates high lock contention, is
> > timing out on RISC-V systems likely due to inherent performance
> differences
> > of th
Tracker says "Marked for autoremoval on 20 May: #1099900"
This is a ping to delay the autoremoval.
On 2025-05-12 00:27, Yue Gui wrote:
My solution to this issue:
The `test_lock_contention` test, which simulates high lock contention, is
timing out on RISC-V systems likely due to inherent performance differences
of the architecture compared to more established platforms like x86_64, for
which t
Control: tags -1 + pending
On Wed, 16 Apr 2025 at 19:50:46 +0100, Simon McVittie wrote:
https://github.com/doitsujin/dxvk/pull/4853 is an untested implementation
of the "generic CPU" code path that I suggested in the bug report.
This was applied in the packaging git repo as part of an updated
Processing control commands:
> tags -1 + pending
Bug #1103352 [src:dxvk] dxvk: FTBFS on armhf and other non-x86 non-aarch64
architectures: #error "Unknown CPU Architecture"
Added tag(s) pending.
--
1103352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103352
Debian Bug Tracking System
Con
Your message dated Mon, 12 May 2025 11:34:04 +
with message-id
and subject line Bug#1097131: fixed in gocryptfs 2.5.1-2
has caused the Debian Bug report #1097131,
regarding gocryptfs: FTBFS on i386: dh_auto_test: error: cd _build && go test
-vet=off -v -p 8 github.com/rfjakob/gocryptfs [...]
El 11/5/25 a las 15:16, Adrian Bunk escribió:
I've prepared an NMU for gocryptfs (versioned as 2.5.1-1.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
Thanks for your work. I have made a team upload from this, using a commit
per individual change before pushi
Your message dated Mon, 12 May 2025 11:19:05 +
with message-id
and subject line Bug#1104885: fixed in blazar 15.0.0-2
has caused the Debian Bug report #1104885,
regarding blazar: will FTBFS during trixie support period
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tag -1 pending
Bug #1097131 [src:gocryptfs] gocryptfs: FTBFS on i386: dh_auto_test: error: cd
_build && go test -vet=off -v -p 8 github.com/rfjakob/gocryptfs [...]
Ignoring request to alter tags of bug #1097131 to the same tags previously set
--
1097131: https://b
Control: tag -1 pending
Hello,
Bug #1097131 in gocryptfs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/gocryptfs/-/commit/599fbe9bf2e04c4
Processing control commands:
> tag -1 pending
Bug #1104885 [src:blazar] blazar: will FTBFS during trixie support period
Added tag(s) pending.
--
1104885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1104885 in blazar reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/openstack-team/services/blazar/-/commit/7977b16cfd0926a330
Hi,
> > > It turns out that current src:uwsgi-plugin-python has unsatisfiable
> > > dependencies on uwsgi-abi-fd03c85edfee33327ac760f246543e10 [0].
> > >
> > > Filing as serious because this bug causes migration stalls in sid for
> > > piuparts testing of reverse dependencies [1].
> >
> > I was a
Quoting Alexandre Rossi (2025-05-12 11:11:31)
> > I guess this could be related to #1104206, but filing as a separate bug
> > at your discretion.
>
> Yes it is.
>
> > It turns out that current src:uwsgi-plugin-python has unsatisfiable
> > dependencies on uwsgi-abi-fd03c85edfee33327ac760f246543e10
Hi,
> I guess this could be related to #1104206, but filing as a separate bug
> at your discretion.
Yes it is.
> It turns out that current src:uwsgi-plugin-python has unsatisfiable
> dependencies on uwsgi-abi-fd03c85edfee33327ac760f246543e10 [0].
>
> Filing as serious because this bug causes mig
HI Bastian Blank ,
We verified the below change on s390, the pytest is passing now. Can we close
this bug if everything is fine?
>
--- a/src/xiaomi_ble/parser.py
+++ b/src/xiaomi_ble/parser.py
@@ -1171,7 +1171,7 @@
xobj: bytes, device: XiaomiBluetoothDeviceData, device_type: str
) ->
Package: src:nvidia-toolkit-samples
Version: 12.3~dfsg-1
Severity: serious
Tags: sid trixie
seen with autopkg tests triggered by gcc-12:
https://ci.debian.net/packages/n/nvidia-cuda-samples/testing/amd64/60466757/
2003s compile-cuda-samples_cuda-g++ FAIL non-zero exit status 2
2003s compile-cuda
Your message dated Mon, 12 May 2025 07:49:14 +
with message-id
and subject line Bug#1104964: fixed in ironic 1:29.0.0-6
has caused the Debian Bug report #1104964,
regarding ironic: CVE-2025-44021
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> tag -1 pending
Bug #1104964 {Done: Thomas Goirand } [src:ironic] ironic:
CVE-2025-44021
Added tag(s) pending.
--
1104964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1104964 in ironic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/openstack-team/services/ironic/-/commit/5c57a4de20bf27abd5
Processing control commands:
> tag -1 pending
Bug #1104964 [src:ironic] ironic: CVE-2025-44021
Ignoring request to alter tags of bug #1104964 to the same tags previously set
--
1104964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104964
Debian Bug Tracking System
Contact ow...@bugs.debian
Control: tag -1 pending
Hello,
Bug #1104964 in ironic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/openstack-team/services/ironic/-/commit/959c8969a30e2b3899
Processing control commands:
> tag -1 pending
Bug #1104964 [src:ironic] ironic: CVE-2025-44021
Added tag(s) pending.
--
1104964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1104964 in ironic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/openstack-team/services/ironic/-/commit/26ad75d5121ae3c797
Package: uwsgi-plugin-python3
Version: 2.0.28+8+0.0.2+b1
Severity: serious
Justification: RT
Hi,
I guess this could be related to #1104206, but filing as a separate bug
at your discretion.
It turns out that current src:uwsgi-plugin-python has unsatisfiable
dependencies on uwsgi-abi-fd03c85edfee3
On Sun, Apr 13, 2025 at 06:42:32PM +0200, Lucas Nussbaum wrote:
> Source: zurl
> Version: 1.12.0-1.1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20250413 ftbfs-trixie
>
[...]
> > FAIL! : HttpRequestTest::requestGet() Compared valu
70 matches
Mail list logo
