Your message dated Tue, 08 Apr 2025 06:50:22 +
with message-id
and subject line Bug#1100935: fixed in jline2 2.14.6-6
has caused the Debian Bug report #1100935,
regarding jython: interpreter stops with NoClassDefFoundError
to be marked as done.
This means that you claim that the problem has b
Your message dated Tue, 8 Apr 2025 07:16:52 +0100
with message-id <63875b69-d6f1-4d1c-824c-f6b2e25d2...@debian.org>
and subject line done
has caused the Debian Bug report #1101686,
regarding mpich: triggers test errors: MPII_init_gpu(51): gpu_init failed
to be marked as done.
This means that
Processing control commands:
> close -1 20250305.gitc1ecd02-1
Bug #1102347 [src:cl-nibbles] src:cl-nibbles: fails to migrate to testing for
too long
Marked as fixed in versions cl-nibbles/20250305.gitc1ecd02-1.
Bug #1102347 [src:cl-nibbles] src:cl-nibbles: fails to migrate to testing for
too lon
Source: cl-closer-mop
Version: 2:20241031.git875f4b7-1
Severity: serious
Control: close -1 2:20250303.git53221de-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between test
Source: cl-nibbles
Version: 20240607.gitc054c32-2
Severity: serious
Control: close -1 20250305.gitc1ecd02-1
Tags: sid trixie pending
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
an
Processing control commands:
> close -1 20250129.git18a5cfa-1
Bug #1102346 [src:trivial-features] src:trivial-features: fails to migrate to
testing for too long
Marked as fixed in versions trivial-features/20250129.git18a5cfa-1.
Bug #1102346 [src:trivial-features] src:trivial-features: fails to m
Your message dated Tue, 08 Apr 2025 05:21:36 +
with message-id
and subject line Bug#1074747: fixed in mate-panel 1.27.1-4.1
has caused the Debian Bug report #1074747,
regarding mate-panel: FTBFS: make[4]: *** [Makefile:1040:
org.mate.panel.TestApplet.mate-panel-applet] Error 1
to be marked as
> It looks like to me that the bug is because, with newer kernels, the
> correct path for the power supply plug should be:
> /sys/class/power_supply/ADP0
>
> At least, the above is what I have currently have in my laptop.
>
> The current code for psutil is expecting /AC0 or /AC, but not /ADP0. If
>
Your message dated Tue, 08 Apr 2025 04:54:54 +
with message-id
and subject line Bug#1102137: fixed in rust-openssl 0.10.72-1
has caused the Debian Bug report #1102137,
regarding rust-openssl: RUSTSEC-2025-0022: Use-After-Free in Md::fetch and
Cipher::fetch
to be marked as done.
This means th
On 2025-04-07 18:56:41 +0100, Colin Watson wrote:
> While I don't have any specific disagreement with anything you say here, I'm
> reluctant to unilaterally revert what was apparently a deliberate change in
> response to a user request (see https://bugs.debian.org/944469) so close to
> the trixie f
Package: python3-argcomplete
Version: 3.1.4-1
Severity: critical
Justification: breaks unrelated software
In bug 944469, Daniel Kahn Gillmor (in Cc) requested activation
of global bash completions. As a fix introduced in 3.1.4-1,
Stefano Rivera (in Cc) activated global completions for both
bash an
Your message dated Mon, 07 Apr 2025 23:50:47 +
with message-id
and subject line Bug#1078624: fixed in khal 1:0.11.3-6
has caused the Debian Bug report #1078624,
regarding khal: will FTBFS during trixie support period
to be marked as done.
This means that you claim that the problem has been de
Processing commands for cont...@bugs.debian.org:
> retitle 1099251 node-d3-timer: FTBFS: Error: should be strictly equal
Bug #1099251 [src:node-d3-timer] node-d3-timer: FTBFS: # fail 1
Changed Bug title to 'node-d3-timer: FTBFS: Error: should be strictly equal'
from 'node-d3-timer: FTBFS: # fail
Control: tag -1 pending
Hello,
Bug #1099251 in node-d3-timer 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/js-team/node-d3-timer/-/commit/d4e8d0d7015758667028
Your message dated Mon, 07 Apr 2025 22:31:35 +
with message-id
and subject line Bug#1079329: fixed in systemd 257.5-2
has caused the Debian Bug report #1079329,
regarding systemd(?) still creates /lib64 on arm64
to be marked as done.
This means that you claim that the problem has been dealt w
Hello Lucas,
> This is because pry 0.15.2-1 was uploaded a couple days ago.
>
> @Arlisson Jacques, Sameul Henrique: are you aware of this? Do you plan
> to work on it? (it will prevent pry from migrating to testing)
I wasn't aware of it, thank you for the heads up.
We have to package the latest
Processing commands for cont...@bugs.debian.org:
> severity 1098635 important
Bug #1098635 [src:ytcc] ytcc: FTBFS: E AssertionError: assert
'Unexpected value' in ''
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
-
On Tue, 4 Mar 2025 11:51:06 +0100 Emmanuel Bourg wrote:
On 04/03/2025 11:33, Jonas Smedegaard wrote:
> Thanks for the clarification.
>
> I have reassigned accordingly: If I understand you correctly, the bug
> (of changing without coordination with reverse dependencies) is in
> src:bouncycastl
Processing commands for cont...@bugs.debian.org:
> severity 1101600 normal
Bug #1101600 [src:crypto-equality-clojure] crypto-equality-clojure: FTBFS:
make[1]: *** [debian/rules:23: override_dh_auto_test] Error 1
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please co
severity 1101600 normal
thanks
I'm downgrading the severity of this bug, as I've not been able to
reproduce it, and I believe the issue documented here is in all
likeliness the result of a degraded build environment suffering from
abnormally high resource contention.
Thanks,
-- Jérôme
Your message dated Mon, 7 Apr 2025 21:29:34 +0100
with message-id <7e774df8-3fdd-4a61-966b-0a92f7627...@zoho.com>
and subject line Re: Bug#1102286: pagure: FTBFS: lots of failing tests
has caused the Debian Bug report #1102286,
regarding pagure: FTBFS: lots of failing tests
to be marked as done.
T
Processing commands for cont...@bugs.debian.org:
> reassign 1102286 python3-billiard
Bug #1102286 {Done: "Rebecca N. Palmer" } [src:pagure]
pagure: FTBFS: lots of failing tests
Bug reassigned from package 'src:pagure' to 'python3-billiard'.
No longer marked as found in versions pagure/5.14.1+dfsg
Package: r-cran-sparsevctrs
Version: 0.2.0-1
Severity: serious
Tags: patch
The autopkgtest is failing with
Error in `coerce_to_sparse_matrix(mtcars)`: The package "Matrix" is
required.
(I'm not sure why this is only now actually failing, when it's always
had that error message: possibly a re
Hi all,
I plan to NMU this package to fix this bug. As patch is already in
Ubuntu I just merged it.
I will upload it to the delay/3 queue.
The debdiff is as attachment.
Yours,
Paul
diff -Nru mrtdreader-0.1.6/debian/changelog mrtdreader-0.1.6/debian/changelog
--- mrtdreader-0.1.6/debian/c
Hi Lucas,
Thanks for the heads-up!
I wasn’t aware of the issue, but I’ll look into it and work on fixing it.
Arlisson Jaques
Em sáb., 5 de abr. de 2025 às 15:32, Lucas Nussbaum
escreveu:
> This now fails because of:
>
> The following packages have unmet dependencies:
> ruby-pry-byebug : Depe
On Sun, Mar 30, 2025 at 12:27:38AM +, Santiago Vila wrote:
During a rebuild of all packages in unstable, your package failed to build:
[ Note 1: I recommend that you add a debian/salsa-ci.yml file to check for
buildability ]
[ Note 2: The salsa project does not match the source package nam
On Wed, Mar 26, 2025 at 12:31:14PM +0100, Lorenzo wrote:
> Hello Mathieu,
>
> I see that the package seems ready for upload in git, is there any
> remaining blocker? Anything that I could do to help with this?
> Given the timeline for the freeze [1] packages that are not in testing
> by 2025-04-15
On Sat, Apr 05, 2025 at 07:47:50PM +0200, Julien Plissonneau Duquène wrote:
> Hi Pierre,
>
> Le 2025-04-05 15:10, Pierre Gruet a écrit :
> >
> > I have unfortunately no clue to fix it... or we could revert the
> > version of plexus-resources.
>
> In https://bugs.debian.org/cgi-bin/bugreport.cgi?b
Your message dated Mon, 07 Apr 2025 18:54:47 +
with message-id
and subject line Bug#1101856: fixed in mypy 1.15.0-5
has caused the Debian Bug report #1101856,
regarding mypy: FTBFS: AssertionError: error: test_module.Y.__closed__ variable
differs from runtime type None
to be marked as done.
Processing control commands:
> reassign -1 src:jline2
Bug #1100935 [jython] jython: interpreter stops with NoClassDefFoundError
Bug reassigned from package 'jython' to 'src:jline2'.
No longer marked as found in versions jython/2.7.3+repack1-1.
Ignoring request to alter fixed versions of bug #11009
On 2025-03-27, Vagrant Cascadian wrote:
> On 2025-03-27, Arnaud Ferraris wrote:
>> Le 26/03/2025 à 19:36, Adrian Bunk a écrit :
>>> On Tue, Mar 11, 2025 at 03:27:04PM -0700, Vagrant Cascadian wrote:
>>>
>>> This bug needs some fixing soon (in the worst case a partial revert to
>>> the bookworm cod
Your message dated Mon, 07 Apr 2025 18:19:40 +
with message-id
and subject line Bug#1067108: fixed in alien-arena 7.71.7+dfsg-1
has caused the Debian Bug report #1067108,
regarding alien-arena: FTBFS with -Werror=implicit-function-declaration
to be marked as done.
This means that you claim th
Processing commands for cont...@bugs.debian.org:
> tags 1099902 + fixed
Bug #1099902 {Done: Paul Gevers } [src:slurm-wlm-contrib]
src:slurm-wlm-contrib: fails to migrate to testing for too long
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1
Processing commands for cont...@bugs.debian.org:
> block 1099900 with 1097131
Bug #1099900 {Done: Paul Gevers } [src:gocryptfs]
src:gocryptfs: fails to migrate to testing for too long
1099900 was not blocked by any bugs.
1099900 was not blocking any bugs.
Added blocking bug(s) of 1099900: 1097131
> As well as the obvious missing build-dependencies, the tests seem to
> require a test.cfg with YouTube account credentials (judging by
> .github/workflows/coverage.yml, anyway).
>
> Salvo, should we just disable the tests? It's not clear to me that
> there are many other options here.
Hello,
On Thu, Apr 03, 2025 at 04:51:22PM +0200, Vincent Lefevre wrote:
I'm removing the "upstream" tag, because at
https://github.com/kislyuk/argcomplete/issues/491#issuecomment-2774459991
the upstream author says:
Argcomplete does not activate global completion by default and does
not recommend
Processing control commands:
> tags -1 patch
Bug #1034247 [src:mtree-netbsd] mtree-netbsd: Wrong BSD-4-clause
Added tag(s) patch.
> severity -1 serious
Bug #1034247 [src:mtree-netbsd] mtree-netbsd: Wrong BSD-4-clause
Severity set to 'serious' from 'important'
--
1034247: https://bugs.debian.org/
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package python-argcomplete
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.
Control: tag -1 pending
Hello,
Bug #1101856 in mypy 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/mypy/-/commit/34a6237ace6c102aac68f8fba
Your message dated Mon, 07 Apr 2025 16:24:05 +
with message-id
and subject line Bug#1034247: fixed in mtree-netbsd 20180822-9
has caused the Debian Bug report #1034247,
regarding mtree-netbsd: Wrong BSD-4-clause
to be marked as done.
This means that you claim that the problem has been dealt w
Hi Patrice et Petter
About:
--- a/src/showscore.c
+++ b/src/showscore.c
@@ -72,7 +72,7 @@
filename = strrchr(filename, '/') + 1;
ReadHighscores(filename);
-z = ctime(&p[4]);
+z = ctime((const time_t *) &p[4]);
if (strchr(z, '\n'))
We can't stuff 64 bits into a 32 bit variable.
On Mon, Apr 07, 2025 at 10:26:58AM +0200, Michel Dänzer wrote:
> Actually, I think I was referring to the name of the JSON file containing
> x86_64 instead of something x32 specific.
Right. And there we have the same problem as with ARM32. The filename
only encodes the CPU, but Debian supports mu
Processing commands for cont...@bugs.debian.org:
> tags 1095386 + patch
Bug #1095386 [src:ruby-sassc-rails] ruby-sassc-rails: FTBFS: ERROR: Test
"ruby3.3" failed. Exiting.
Added tag(s) patch.
> tags 1100308 + patch
Bug #1100308 [src:ruby-haml] ruby-haml: FTBFS: failing tests
Added tag(s) patch.
>
Package: android-udev-rules
Version: 0~20250314+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + google-android-platform-tools-installer
android-udev-rules has an undeclared file conflict. This may result in
an unpack error from dpkg.
The file /
Your message dated Mon, 07 Apr 2025 15:09:19 +
with message-id
and subject line Bug#1101599: fixed in qemu 1:10.0.0~rc2+ds-2
has caused the Debian Bug report #1101599,
regarding qemu-system-x86_64 segfaults running ipxe selftests
to be marked as done.
This means that you claim that the proble
Your message dated Mon, 07 Apr 2025 15:10:18 +
with message-id
and subject line Bug#1091286: fixed in xsok 1.02-23
has caused the Debian Bug report #1091286,
regarding xsok: FTBFS on armhf: showscore.c:75:15: error: passing argument 1 of
‘ctime’ from incompatible pointer type [-Wincompatible-
Processing control commands:
> affects -1 + android-sdk-platform-tools-common
Bug #1102322 [android-udev-rules] android-udev-rules ineffectively Replaces
android-sdk-platform-tools-common due to the /usr-move transition (DEP17 P1)
Added indication that 1102322 affects android-sdk-platform-tools-c
Package: android-udev-rules
Version: 0~20250314+ds-2
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: dep17p1
Control: affects -1 + android-sdk-platform-tools-common
android-udev-rules installs the file
/usr/lib/udev/rules.d/51-android.rules. Unfortunately,
android-sdk-platform-too
Package: simplemonitor
Version: 1.14.0a-2
Severity: serious
User: helm...@debian.org
Usertags: dep17m2
Hi Carles,
I'm taking this to a bug report for tracking purposes as I reported it
directly already.
The most recent simplemonitor upload is a binary upload. Therefore, it
cannot migrate to test
Control: tag -1 pending
Hello,
Bug #1101621 in billiard 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/billiard/-/commit/c7e8681eeecfa12c3
Processing control commands:
> tag -1 pending
Bug #1101621 [python3-billiard] '_Code' object has no attribute 'co_qualname'
Added tag(s) pending.
--
1101621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Fri, 4 Apr 2025 11:59:29 +0200 Helmut Grohne
wrote:
> I am looking forward to reaching a consensual solution on the next
> upstream PR and swapping it out then.
As agreed privately: the backport of the new patch is now queued in
Salsa for the next upload, waiting for the current version (with
Control: tag -1 pending
Hello,
Bug #1079329 in systemd 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/systemd-team/systemd/-/commit/709e474e5b236fc081569d2a07b
Processing control commands:
> tag -1 pending
Bug #1079329 [systemd] systemd(?) still creates /lib64 on arm64
Ignoring request to alter tags of bug #1079329 to the same tags previously set
--
1079329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079329
Debian Bug Tracking System
Contact ow
Hi Paul,
On Sun, Apr 06, 2025 at 04:00:41PM +0200, Paul Gevers wrote:
> I assume it is still valid to do this. At least without information this bug
> might remain RC and I understand is hardly actionable. I guess you only need
> to inspect the two nodes that were used for one of the failing
> llv
Processing control commands:
> tag -1 pending
Bug #1079329 [systemd] systemd(?) still creates /lib64 on arm64
Added tag(s) pending.
--
1079329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1079329 in systemd 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/systemd-team/systemd/-/commit/81fd0dfa15c3904a7537311743f
Processing commands for cont...@bugs.debian.org:
> forwarded 1101861 https://github.com/wiktor-k/pysequoia/issues/39
Bug #1101861 [src:pysequoia] pysequoia: FTBFS: error: failed to select a
version for the requirement `sequoia-openpgp = "^1"`
Set Bug forwarded-to-address to
'https://github.com/w
Your message dated Mon, 07 Apr 2025 14:03:15 +
with message-id
and subject line Bug#1075420: fixed in python-pyo 1.0.6-1
has caused the Debian Bug report #1075420,
regarding python-pyo: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 07 Apr 2025 14:03:15 +
with message-id
and subject line Bug#1084560: fixed in python-pyo 1.0.6-1
has caused the Debian Bug report #1084560,
regarding python-pyo: removal of Python standard libraries in Python 3.13
to be marked as done.
This means that you claim that th
Processing commands for cont...@bugs.debian.org:
> tags 1102172 + sid trixie
Bug #1102172 [o-saft] o-saft: Drop from trixie - Need to package latest release
and reasses whether we want to ship
Added tag(s) sid and trixie.
> found 1084075 6.1.2-3
Bug #1084075 [src:rocr-runtime] rocr-runtime: Pleas
Source: patchelf
User: debian-m...@lists.debian.org
Usertags: mips64el
X-Debbugs-Cc: debian-m...@lists.debian.org
X-Debbugs-Cc: Sergio Durigan Junior
Version: 0.18.0-1.2
Severity: serious
Tags: ftbfs
Hi Maintainer
The recent upload of patchelf 0.18.0-1.2 FTBFS on mips64el [1]. I've
copied what
07.04.2025 13:03, Miao Wang wrote:
I found the same bug in 1:10.0.0~rc2+ds-1. The symptom remains the same.
Indeed. I included the patch, but forgot to commit d/patches/series.
Lemme do another upload...
Thanks,
/mjt
forwarded 1092377 https://github.com/telegramdesktop/tdesktop/issues/29176
thanks
I reported to upstream, but I have no idea if they will look at it.
https://github.com/telegramdesktop/tdesktop/issues/29176
Other than that I tried to fix it by myself and to see if there were commits or
bugs th
Processing commands for cont...@bugs.debian.org:
> forwarded 1092377 https://github.com/telegramdesktop/tdesktop/issues/29176
Bug #1092377 [src:telegram-desktop] telegram-desktop: FTBFS:
dbusinterface.hpp:170:3: error: lookup of ‘_check_member_conflict_get_info’ in
‘base::Platform::SystemMediaCo
Source: wireguard
Version: 1.0.20210914-2
Severity: serious
Justification: stops other packages from migrating to testing
Dear Maintainer(s),
The wg-quick and netns-mini autopkgtest cannot work on i386, as the
wireguard-dkms or wireguard-modules packages cannot be installed, as
there's no i386 ke
I just noticed that I totally forgot to mention the relevant change. The
original d/control has:
Build-Depends: systemd, systemd-dev | libsystemd-dev
Which is missing after running fixcontrol and thus missing from the
.buildinfo file.
Cheers Jochen
signature.asc
Description: PGP signature
I'm working on a patch for this, that I have sent upstream for review:
https://github.com/KWARC/rust-libxml/pull/143
If anyone is able to confirm that it fixes the build on 32 bit
architectures, I'd add it to the debian package and resubmit.
Otherwise I'll try to get my hands on a 32 bit VM in
Hi.
A trick which usually works is to generate the desired file using
a different filename, then error if the files differ.
The attached diff will give you an idea, but it's untested.
(I failed to see how the code in GNUmakefile is reached from debian/rules)
Thanks.--- pcp-6.3.7/debian/GNUmakef
Processing commands for cont...@bugs.debian.org:
> fixed 1100210 1:20.0.0-1
Bug #1100210 {Done: Thomas Goirand } [src:designate]
designate: FTBFS: KeyError: 'reason'
Marked as fixed in versions designate/1:20.0.0-1.
> found 1100210 1:19.0.0-4
Bug #1100210 {Done: Thomas Goirand } [src:designate]
Control: tag -1 pending
Hello,
Bug #1102283 in pydantic 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/pydantic/-/commit/e0cae51c599ca6c57
Your message dated Mon, 07 Apr 2025 09:34:38 +
with message-id
and subject line Bug#1102283: fixed in pydantic 2.10.6-2
has caused the Debian Bug report #1102283,
regarding pydantic - autopkgtest fails with new pydantic-core.
to be marked as done.
This means that you claim that the problem ha
Control: tag -1 pending
Hello,
Bug #1078613 in dput-ng 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/debian/dput-ng/-/commit/4d61da5e6536fecb6930b60a0cbd366be
Processing commands for cont...@bugs.debian.org:
> forwarded 1101621 https://github.com/celery/billiard/pull/423
Bug #1101621 [python3-billiard] '_Code' object has no attribute 'co_qualname'
Set Bug forwarded-to-address to 'https://github.com/celery/billiard/pull/423'.
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> block 1101493 by 1101599
Bug #1101493 [ipxe-qemu] efi-*.rom fail to boot
1101493 was not blocked by any bugs.
1101493 was blocking: 1101488
Added blocking bug(s) of 1101493: 1101599
> block 1101412 by 1101599
Bug #1101412 [src:ipxe] debci tests fo
Source: pcp
Version: 6.3.7-1
Severity: serious
X-Debbugs-Cc: Helmut Grohne ,
reproducible-b...@lists.alioth.debian.org
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildinfo
Hi,
src:pcp modifies the debian/control file during the build:
=== debian ===
make[2]: Entering directory
Package: src:containerd
Version: 1.7.24~ds1-4
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
github.com/containerd/continu
Package: src:pagure
Version: 5.14.1+dfsg-7
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
-- Docs: https://docs.pytest.org
Package: src:ruby-integration
Version: 0.1.0-1.1
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
[...]
debian/rules clean
dh cle
Processing control commands:
> tag -1 pending
Bug #1078613 [src:dput-ng] dput-ng: will FTBFS during trixie support period
Added tag(s) pending.
--
1078613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #1102283 [pydantic] pydantic - autopkgtest fails with new pydantic-core.
Added tag(s) pending.
--
1102283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package:
libc++-20-dev,libc++1-20,libc++abi-20-dev,libc++abi1-20,libclang-rt-20-dev,libmlir-20,libmlir-20-dev,liboffload-20,libomp5-20,libpolly-20-dev,libunwind-20,libunwind-20-dev
Version: 1:20.1.1-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
The named package
Processing commands for cont...@bugs.debian.org:
> unarchive 1036806
> found 1036806 1.121.0-1
Bug #1036806 [src:matrix-synapse] matrix-synapse: not suitable for inclusion in
trixie
Marked as found in versions matrix-synapse/1.121.0-1.
> thanks
Stopping processing here.
Please contact me if you
Your message dated Mon, 07 Apr 2025 08:49:36 +
with message-id
and subject line Bug#1064696: fixed in node-node-rsa 1.1.1-5
has caused the Debian Bug report #1064696,
regarding node-node-rsa: FTBFS: make[1]: *** [debian/rules:19:
override_dh_auto_test] Error 14
to be marked as done.
This mea
Package: pydantic
Version: 2.10.6-1
Severity: serious
After the update of pydantic-core to build against the new rust-url,
pydantic's autopkgtests are failing.
https://ci.debian.net/packages/p/pydantic/testing/amd64/59623497/
63s E Differing items:
63s E {'msg': 'Input should
Control: tag -1 pending
Hello,
Bug #1099640 in node-node-rsa 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/js-team/node-node-rsa/-/commit/c5654f1504dc361af0fd
Processing control commands:
> tag -1 pending
Bug #1099640 [src:node-node-rsa] node-node-rsa: FTBFS: make[1]: ***
[debian/rules:19: override_dh_auto_test] Error 14
Added tag(s) pending.
--
1099640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099640
Debian Bug Tracking System
Contact ow..
On 2025-04-04 20:42, Helmut Grohne wrote:
> On Fri, Jan 15, 2021 at 12:06:14PM +0100, Michel Dänzer wrote:
>> On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
>>> Package: mesa-vulkan-drivers
>>> […]
>>> Multi-Arch: same
>>>
>>> The file /usr/share/vulkan/icd.d/intel_icd.x86_64.json differs.
>>>
>>
On 2025-04-04 20:42, Helmut Grohne wrote:
> On Fri, Jan 15, 2021 at 12:06:14PM +0100, Michel Dänzer wrote:
>> On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
>>> Package: mesa-vulkan-drivers
>>> […]
>>> Multi-Arch: same
>>>
>>> The file /usr/share/vulkan/icd.d/intel_icd.x86_64.json differs.
>>>
>>
Your message dated Mon, 7 Apr 2025 10:27:46 +0200
with message-id
and subject line Re: Bug#1102268: motion: Dependency problem: requires
libavdevice59 >=7:5.0 which is not available
has caused the Debian Bug report #1102268,
regarding motion: Dependency problem: requires libavdevice59 >=7:5.0 whi
Processing commands for cont...@bugs.debian.org:
> found 1102268 4.5.1-2
Bug #1102268 [motion] motion: Dependency problem: requires libavdevice59
>=7:5.0 which is not available
Marked as found in versions motion/4.5.1-2.
> severity 1102268 serious
Bug #1102268 [motion] motion: Dependency problem:
Package: librust-secret-service-dev
Version: 4.0.0-4
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Builds involving this package fails to build:
error[E0428]: the name `hkdf` is defined multiple times
-->
/build/rust-email-lib-0+20250111/debian/cargo_registry/secret-service
Processing commands for cont...@bugs.debian.org:
> unarchive 1036806
> reopen 1036806
Bug #1036806 {Done: Andrej Shadura }
[src:matrix-synapse] matrix-synapse: not suitable for inclusion in trixie
Bug reopened
Ignoring request to alter fixed versions of bug #1036806 to the same values
previously
Processing commands for cont...@bugs.debian.org:
> unarchive 1036806
Bug #1036806 {Done: Andrej Shadura }
[src:matrix-synapse] matrix-synapse: not suitable for inclusion in bookworm
Unarchived Bug 1036806
> retitle 1036806 matrix-synapse: not suitable for inclusion in trixie
Bug #1036806 {Done: A
Processing commands for cont...@bugs.debian.org:
> reassign 1094520 ruby-rack-protection 3.2.0-1
Bug #1094520 [src:ruby-omniauth-tumblr] ruby-omniauth-tumblr: FTBFS: ERROR:
Test "ruby3.3" failed: Failure/Error: require 'omniauth'
Bug reassigned from package 'src:ruby-omniauth-tumblr' to
'ruby-ra
Processing control commands:
> severity -1 serious
Bug #1030749 [request-tracker4] request-tracker4: Don't release with trixie
Severity set to 'serious' from 'normal'
--
1030749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030749
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Package: lib32atomic1,libn32atomic1
Version: 15-20250329-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Hi Matthias,
I observe that lib32atomic1 and libn32atomic1 both install
/usr/lib32/libatomic.so.1 and /usr/lib32/libatomic.so.1.2.0 without
declaring any suitable r
Quoting Jonas Smedegaard (2025-04-07 09:29:04)
> Package: librust-secret-service-dev
> Version: 4.0.0-4
> Severity: grave
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Builds involving this package fails to build:
>
> error[E0428]: the name `hkdf` is defined multiple times
>-->
Package: librust-test-log-dev
Version: 0.2.15-2
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The feature "trace" causes build failure:
error[E0599]: no method named `with_env_filter` found for struct
`SubscriberBuilder` in the current scope
--> time/src/timer.rs:599:5
99 matches
Mail list logo
