Processing control commands:
> tags -1 upstream
Bug #1103009 [src:genomicsdb] genomicsdb: FTBFS in testing/arm64: tests failed
Added tag(s) upstream.
> forwarded -1 https://github.com/GenomicsDB/GenomicsDB/issues/355
Bug #1103009 [src:genomicsdb] genomicsdb: FTBFS in testing/arm64: tests failed
Se
Control: tags -1 upstream
Control: forwarded -1 https://github.com/GenomicsDB/GenomicsDB/issues/355
Thanks
Control: found -1 2.0.3-1
I too have been watching this. This patch has both resolved the reproducer
and some other real-world cases (in fact, I'm unaware of anyone experiencing
the corruption after using the patch).
However, in the (draft) pull request, there is discussion over how the
(clearl
Processing control commands:
> found -1 2.0.3-1
Bug #1106035 [zfs-dkms] zfs: Upstream patch for old encryption data corruption
bug
Marked as found in versions zfs-linux/2.0.3-1.
--
1106035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106035
Debian Bug Tracking System
Contact ow...@bugs.d
Package: zfs-dkms
Version: 2.3.2-1
Severity: grave
Tags: upstream patch
Dear Maintainer,
since the release of ZFS 2.0.0 back in 2020, ZFS contains a corruption
bug where snapshots and/or a dataset can get corrupted when using ZFS
encryption, if you're performing a "zfs send" at the same time a
Processing commands for cont...@bugs.debian.org:
> found 1078635 7.9.5-2+deb12u1
Bug #1078635 {Done: Jérôme Charaoui } [src:puppetserver]
puppetserver: FTBFS due to expired certificates used in tests
Bug #1092396 {Done: Jérôme Charaoui } [src:puppetserver]
puppetserver: FTBFS due to expired cert
Processing commands for cont...@bugs.debian.org:
> found 1078635 7.9.5-2+deb12u1
Bug #1078635 {Done: Jérôme Charaoui } [src:puppetserver]
puppetserver: FTBFS due to expired certificates used in tests
Bug #1092396 {Done: Jérôme Charaoui } [src:puppetserver]
puppetserver: FTBFS due to expired cert
Package: keyd-application-mapper
Version: 2.5.0-2
Severity: grave
Tags: a11y patch
Justification: renders package unusable
X-Debbugs-Cc: l...@martinmarshall.com
Dear Maintainer,
* What led up to the situation?
Installed the keyd-application-mapper package, which depends on the keyd
package an
found 1078635 7.9.5-2+deb12u1
thanks
Hi. I've unarchived this one because it's currently happening in bookworm,
the current stable release.
Thanks.
Processing commands for cont...@bugs.debian.org:
> unarchive 1078635
Bug #1078635 {Done: Jérôme Charaoui } [src:puppetserver]
puppetserver: will FTBFS during trixie support period
Bug #1092396 {Done: Jérôme Charaoui } [src:puppetserver]
puppetserver: FTBFS: make[1]: *** [debian/rules:64: overrid
tags 1091504 bookworm
thanks
Hi. This is still happening in bookworm.
Thanks.
Processing commands for cont...@bugs.debian.org:
> tags 1091504 bookworm
Bug #1091504 {Done: Jérôme Charaoui } [src:puppetdb]
puppetdb: FTBFS in bookworm and trixie because of expired certificate
Added tag(s) bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Your message dated Sun, 18 May 2025 23:20:16 +
with message-id
and subject line Bug#1105191: fixed in screen 4.9.1-3
has caused the Debian Bug report #1105191,
regarding screen: TTY Hijacking while Attaching to a Multi-User Session
(CVE-2025-46802)
to be marked as done.
This means that you c
Your message dated Sun, 18 May 2025 20:40:24 +
with message-id
and subject line Bug#1105806: fixed in net-tools 2.10-0.1+deb12u1
has caused the Debian Bug report #1105806,
regarding net-tools: CVE-2025-46836
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> tags 1037453 ftbfs
Bug #1037453 {Done: Noah Meyerhans } [libmail-dmarc-perl]
libmail-dmarc-perl: FTBFS with test failures when there's no network
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Greetings,
Alexandre Detiste, on 2025-05-14:
> The only reverse-dependency left is "intake" which won't be included in
> Trixie.
>
> After "intake" is fixed, this can be removed.
The package "intake" has become gradually more difficult to
maintain. Going further with newer "intake" upstream ve
Your message dated Sun, 18 May 2025 17:35:43 +
with message-id
and subject line Bug#1085976: fixed in nvidia-open-gpu-kernel-modules
550.127.05-1
has caused the Debian Bug report #1085976,
regarding nvidia-open-gpu-kernel-modules: CVE-2024-0126
to be marked as done.
This means that you claim
Hi,
On 5/18/25 4:14 PM, Philipp Kern wrote:
> On 5/18/25 12:50 PM, Sebastian Ramacher wrote:
>>> 1. is now implemented and deployed. I am cloning the bug for the archive
>>> and buildd sides.
>
> As for wanna-build itself:
>
>> wanna-build=> select * from distribution_architectures where distrib
Your message dated Sun, 18 May 2025 17:35:14 +
with message-id
and subject line Bug#1085968: fixed in nvidia-graphics-drivers 550.127.05-1
has caused the Debian Bug report #1085968,
regarding nvidia-graphics-drivers: CVE-2024-0126
to be marked as done.
This means that you claim that the probl
Your message dated Sun, 18 May 2025 17:00:49 +
with message-id
and subject line Bug#1092673: fixed in nvidia-cuda-toolkit 12.4.0-1
has caused the Debian Bug report #1092673,
regarding nvidia-cuda-toolkit-gcc: depends on g++-12
to be marked as done.
This means that you claim that the problem h
Your message dated Sun, 18 May 2025 16:37:36 +
with message-id
and subject line Bug#1105983: fixed in uncertainties 3.2.3-2
has caused the Debian Bug report #1105983,
regarding uncertainties: FTBFS on buildds: timing-dependant test
to be marked as done.
This means that you claim that the prob
Your message dated Sun, 18 May 2025 16:06:30 +
with message-id
and subject line Bug#1105886: fixed in python-tornado 6.4.2-2
has caused the Debian Bug report #1105886,
regarding python-tornado: CVE-2025-47287
to be marked as done.
This means that you claim that the problem has been dealt with
Processing commands for cont...@bugs.debian.org:
> severity 1104961 important
Bug #1104961 [src:actiona] FTBFS on mips64el: collect2: error: ld returned 1
exit status
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
11049
Processing commands for cont...@bugs.debian.org:
> owner 1105983 !
Bug #1105983 [src:uncertainties] uncertainties: FTBFS on buildds:
timing-dependant test
Owner recorded as Santiago Vila .
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1105983: https://bugs.debi
owner 1105983 !
thanks
Hi. Thanks for the report. I'm going to disable
test_repeated_summation_complexity().
Thanks.
Processing control commands:
> tag -1 pending
Bug #1105886 [src:python-tornado] python-tornado: CVE-2025-47287
Added tag(s) pending.
--
1105886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1105886 in python-tornado 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/python-team/packages/python-tornado/-/commit/efc05
Processing commands for cont...@bugs.debian.org:
> tags 1105210 + patch
Bug #1105210 [auctex] auctex: 'update-auctex-elisp.eperl' creates a tmpfile in
the root of filesystem in a dangerous way with $(mktemp ./-el)
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me i
Processing control commands:
> tags -1 trixie-ignore
Bug #1104632 {Done: Paul Gevers } [src:imagemagick]
src:imagemagick: fails to migrate to testing for too long
Added tag(s) trixie-ignore.
--
1104632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104632
Debian Bug Tracking System
Contact
Hi,
On 5/18/25 12:50 PM, Sebastian Ramacher wrote:
>> 1. is now implemented and deployed. I am cloning the bug for the archive
>> and buildd sides.
As for wanna-build itself:
> wanna-build=> select * from distribution_architectures where distribution
> like 'trixie%' and architecture = 'mips64e
Control: tags -1 trixie-ignore
On 18-05-2025 12:15, Bastien Roucaries wrote:
As we're now in the Hard Freeze, it seem to me best to use the testing
version (8:7.1.1.43+dfsg1-1) of imagemagick for trixie and trixie-ignore
this bug, 1105051 and 1103190. Do you agree? Let's hope we don't need to
to
Processing control commands:
> tags -1 trixie-ignore
Bug #1105051 [src:imagemagick, src:xplanet] imagemagick breaks xplanet
autopkgtest: test_compare_images() returned non-zero return code
Added tag(s) trixie-ignore.
--
1105051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105051
Debian B
Processing control commands:
> tags -1 trixie-ignore
Bug #1103190 [src:img2pdf] img2pdf: FTBFS: AssertionError: b'4.1089e-06
(8.53093e-08)'
Added tag(s) trixie-ignore.
--
1103190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103190
Debian Bug Tracking System
Contact ow...@bugs.debian.org
tags 1105210 + patch
thanks
Package: auctex
Version: 13.2-1
Dear Maintainer,
I have reproduced the bug and fixed it with the attached patch.
There is also a fix for an uninitialized variable used in the
case that the program block does not exit with an error code
set. This happens when the upd
Processing commands for cont...@bugs.debian.org:
> severity 1085036 serious
Bug #1085036 [libendless-bin] libendless-bin: requires gjs which is unavailable
on armel
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1085036
Source: python-fakeredis
Version: 2.29.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-fakeredis the autopkgtest of
python-fakeredis fails in testing when that autopkgtest is run with the
binary packages of python-f
Processing control commands:
> clone -1 -2
Bug #1105965 [release.debian.org] Remove mips64el from testing
Bug 1105965 cloned as bug 1105988
1105988 was blocked by: 1105972 1105973
1105988 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1105988 to the same blocks
previou
Control: clone -1 -2
Control: severity -2 normal
Control: reassign -2 cdimage.debian.org
Control: retitle -2 cdimage.debian.org: stop building images for mips64el
On 2025-05-18 12:50:44 +0200, Sebastian Ramacher wrote:
> Control: clone -1 -2 -3
> Control: reassign -2 ftp.debian.org
> Control: reti
Processing control commands:
> severity -1 serious
Bug #1105983 [src:uncertainties] uncertainties: FTBFS on buildds:
timing-dependant test
Severity set to 'serious' from 'important'
--
1105983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105983
Debian Bug Tracking System
Contact ow...@bu
Your message dated Sun, 18 May 2025 12:07:07 +
with message-id
and subject line Bug#1105832: fixed in nodejs 20.19.2+dfsg-1
has caused the Debian Bug report #1105832,
regarding CVE-2025-23165 CVE-2025-23166
to be marked as done.
This means that you claim that the problem has been dealt with.
On Montag, 14. April 2025 00:22:01 CEST Elliott Mitchell wrote:
> The analysis is the "(XEN) AMD-Vi: IO_PAGE_FAULT" message, and the
> software RAID data loss are distinct bugs. That patch/commit likely
> makes the correlated message disappear, but almost certainly leaves the
> software RAID data
Source: sensorpro-ble
Version: 0.7.0-1
Severity: serious
Hi,
sensorpro-ble 0.7.0-1 fails its autopktest on all archs in testing.
From the excuses page:
https://qa.debian.org/excuses.php?package=sensorpro-ble
Issues preventing migration:
autopkgtest for sensorpro-ble/0.7.0-1: amd64:
On Sat, May 10, 2025 at 03:18:26PM +0530, Vivek K J wrote:
Hey,
I've creatd an MR which will will update simplyhtml to 1.8.11 and will
be able to close RC #1104088 through it, bringing simplyhtml back to
working condition.
"43 files +816 −979" is not a suitable change during a freeze. If you
Hi,
On Sat, 10 May 2025 13:35:02 + Debian FTP Masters wrote:
rust-graphene-sys (0.20.7-2) unstable; urgency=medium
.
* Depend on libgraphene for regeneration (Closes: #1104982)
I'm slightly confused about the solution. I'm now seeing
libgraphene-1.0-dev twice, once in the Build-Depe
Processing control commands:
> clone -1 -2 -3
Bug #1105965 [release.debian.org] Remove mips64el from testing
Bug 1105965 cloned as bugs 1105972-1105973
> reassign -2 ftp.debian.org
Bug #1105972 [release.debian.org] Remove mips64el from testing
Bug reassigned from package 'release.debian.org' to 'f
Control: clone -1 -2 -3
Control: reassign -2 ftp.debian.org
Control: retitle -2 ftp.debian.org: remove mipsel64el from testing
Control: severity -2 normal
Control: reassign -3 buildd.debian.org
Control: retitle -3 buildd.debian.org: stop building mipsel64el for testing
Control: severity -3 normal
C
Control: clone -1 -2 ftp.debian.org
Control: retitle -2 ftp.debian.org: remove mipsel64el from testing
Control: severity -2 normal
Control: clone -1 -3 buildd.debian.org
Control: retitle -3 buildd.debian.org: stop building mipsel64el for testing
Control: severity -3 normal
Control: block -1 by -2 -
Le dimanche 18 mai 2025, 09:26:39 heure d’été d’Europe centrale Paul Gevers a
écrit :
> Hi ImageMagick Packaging Team, Bastien,
>
> [Release Team member hat on]
>
> On Sat, 3 May 2025 13:58:21 +0200 Paul Gevers wrote:
>
> > The Release Team considers packages that are out-of-sync between test
Your message dated Sun, 18 May 2025 10:06:28 +
with message-id
and subject line Bug#1092791: fixed in python-cobra 0.29.1-2
has caused the Debian Bug report #1092791,
regarding FTBFS: TypeError: GPR.__init__() takes from 1 to 2 positional
arguments but 3 were given
to be marked as done.
This
Control: tag -1 pending
Hello,
Bug #1092791 in python-cobra 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/python-cobra/-/commit/37fdc5cc85f064e4a0fcb
Processing control commands:
> tag -1 pending
Bug #1092791 [src:python-cobra] FTBFS: TypeError: GPR.__init__() takes from 1
to 2 positional arguments but 3 were given
Added tag(s) pending.
--
1092791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092791
Debian Bug Tracking System
Contact o
Hi all, Helmut,
On 18-05-2025 10:54, Sebastian Ramacher wrote:
Let use this bug to coordinate the removal of mips64el from testing. As
last time:
1. Get britney to ignore mips64el
2. Stop building for mips64el/{testing,unstable,experimental}
3. Remove mips64el/{testing,unstable,experimental} fr
Package: release.debian.org
Severity: serious
X-Debbugs-CC: sramac...@debian.org, debian-m...@lists.debian.org
On 2025-05-18 08:26:30 +, Paul Gevers wrote:
> mips64el and riscv64
>
>
> The Release Team has decided to drop mips64el as a release architecture
Let use this b
Processing commands for cont...@bugs.debian.org:
> # clarified
> tags 1094257 - moreinfo
Bug #1094257 [bluez] Do not start mpris-proxy for root user
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1094257: https://bugs.debian.org/cgi-bin/b
Processing commands for cont...@bugs.debian.org:
> notfound 1094984 python-meshplex/0.17.1-4
Bug #1094984 {Done: Drew Parsons } [src:python-meshplex]
python-meshplex: FTBFS with numpy 2.x
No longer marked as found in versions python-meshplex/0.17.1-4.
>
End of message, stopping processing here.
Hi Charles
On Tue, 13 May 2025 at 01:42, Charles Plessy wrote:
> Can you unblock r-cran-bigmemory? It absence from Trixie causes
> autopkgtest failures, with a possible cascade effect of more removal /
> failure / removal cycles.
Unblocked.
Please use the documented procedure 'Applying for an
Your message dated Sun, 18 May 2025 10:34:16 +0200
with message-id
and subject line Re: Bug#1093859: release.debian.org: status of mips64el for
trixie
has caused the Debian Bug report #1093859,
regarding release.debian.org: status of mips64el for trixie
to be marked as done.
This means that you
Hi Paul,
Quoting Paul Gevers (2025-05-18 09:26:39)
> Hi ImageMagick Packaging Team, Bastien,
>
> [Release Team member hat on]
>
> On Sat, 3 May 2025 13:58:21 +0200 Paul Gevers wrote:
> > The Release Team considers packages that are out-of-sync between testing
> > and unstable for more than 30
Processing commands for cont...@bugs.debian.org:
> block 1103568 with 1100891
Bug #1103568 {Done: Paul Gevers } [src:rsplib] src:rsplib:
fails to migrate to testing for too long
1103568 was not blocked by any bugs.
1103568 was not blocking any bugs.
Added blocking bug(s) of 1103568: 1100891
> tha
Control: tag -1 confirmed
On 18 May 2025 00:37:44 CEST, Ben Hutchings wrote:
>On Sun, 2025-04-27 at 16:18 +0200, Ben Hutchings wrote:
>[...]
>> - If I mask packagekit.service before booting (using a rescue shell),
>> then none of the files are updated automatically. Running 'apt
>> update'
Processing control commands:
> tag -1 confirmed
Bug #1078608 [apt] apt update silently leaves old index data
Added tag(s) confirmed.
--
1078608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi ImageMagick Packaging Team, Bastien,
[Release Team member hat on]
On Sat, 3 May 2025 13:58:21 +0200 Paul Gevers wrote:
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Critical bug in
testing [1]. Your package s
62 matches
Mail list logo
