Control: tags -1 upstream
Control: forwarded -1 https://github.com/piskvorky/smart_open/issues/846
Processing control commands:
> tags -1 upstream
Bug #1089053 [src:smart-open] smart-open: autopkgtest failure with Python 3.13
Added tag(s) upstream.
> forwarded -1 https://github.com/piskvorky/smart_open/issues/846
Bug #1089053 [src:smart-open] smart-open: autopkgtest failure with Python 3.13
Set
Hello again,
On Thu, Dec 12, 2024 at 06:42:47PM +0100, Florian Ernst wrote:
> By its very nature (cf. the detailed description as linked above), this
> vulnerability cannot be fixed with a drop-in replacement while keeping
> the current user interface: if credentials have been entered on the
> com
Hi Adrian,
On Sun, 1 Dec 2024 10:16:31 +0100 Sebastian Markowski
wrote:
so when can we expect 1.8.1 to be uploaded in unstable or at least
experimental?
Your last reply to this and the other RC bugs was mid September. Can we
please have a response from you? Otherwise I'm inclined to try and
Your message dated Sun, 15 Dec 2024 06:49:11 +
with message-id
and subject line Bug#1088325: fixed in jinja2 3.1.3-1.1
has caused the Debian Bug report #1088325,
regarding jinja2: autopkgtest failure with Python 3.13
to be marked as done.
This means that you claim that the problem has been de
Fixed in ruby-terser | 1.2.4+dfsg-1
--abhijith
Processing control commands:
> block -1 by 1089916
Bug #1088239 [src:deepdiff] deepdiff: autopkgtest failure with Python 3.13
1088239 was not blocked by any bugs.
1088239 was not blocking any bugs.
Added blocking bug(s) of 1088239: 1089916
--
1088239: https://bugs.debian.org/cgi-bin/bugreport.cg
Control: block -1 by 1089916
Thanks
The latest upstream version of deepdiff (in Salsa) fixes this bug but it
needs the new dependency orderly-set which is in NEW. Once the ITP
#1089916 is closed this bug can be fixed.
--
https://fam-tille.de
Processing control commands:
> tags -1 upstream
Bug #1089115 [src:umis] umis: tracebacks normally fatal during autopkgtest runs
Added tag(s) upstream.
> forwarded -1 https://github.com/vals/umis/issues/68
Bug #1089115 [src:umis] umis: tracebacks normally fatal during autopkgtest runs
Set Bug forwa
Control: tags -1 upstream
Control: forwarded -1 https://github.com/vals/umis/issues/68
Thanks
The issues was reported upstream two years ago and I have pinged the issue.
(No response so far.)
--
https://fam-tille.de
Processing commands for cont...@bugs.debian.org:
> block 1089981 by 1088839
Bug #1089981 {Done: Paul Gevers } [src:swi-prolog]
src:swi-prolog: fails to migrate to testing for too long
1089981 was not blocked by any bugs.
1089981 was not blocking any bugs.
Added blocking bug(s) of 1089981: 1088839
Source: libxkbcommon
Version: 1.6.0-1
Severity: serious
Control: close -1 1.7.0-1
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 a
Source: arch-test
Version: 0.21-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Dear maintainer(s),
Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed fr
Processing control commands:
> close -1 1.7.0-1
Bug #1089982 [src:libxkbcommon] src:libxkbcommon: fails to migrate to testing
for too long
Marked as fixed in versions libxkbcommon/1.7.0-1.
Bug #1089982 [src:libxkbcommon] src:libxkbcommon: fails to migrate to testing
for too long
Marked Bug as do
Processing control commands:
> close -1 9.2.8+dfsg-3
Bug #1089981 [src:swi-prolog] src:swi-prolog: fails to migrate to testing for
too long
Marked as fixed in versions swi-prolog/9.2.8+dfsg-3.
Bug #1089981 [src:swi-prolog] src:swi-prolog: fails to migrate to testing for
too long
Marked Bug as do
Source: swi-prolog
Version: 9.0.4+dfsg-4
Severity: serious
Control: close -1 9.2.8+dfsg-3
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 3
Hi Santiago,
On Sun, 24 Nov 2024 00:21:59 +0100 Santiago Vila wrote:
# the bug is "not having a version high enough" so it's present in trixie and
sid
found 1027339 2.2.7-1.1
Care to elaborate? The package builds fine on r-b infrastructure, so it
isn't obvious what you mean here.
Did you
Your message dated Sun, 15 Dec 2024 05:04:45 +
with message-id
and subject line Bug#1089191: fixed in fcitx-rime 0.3.2+git20230425-4
has caused the Debian Bug report #1089191,
regarding fcitx-rime: FTBFS: error: implicit declaration of function
‘RimeProcessKey’
to be marked as done.
This mea
Control: tags 986801 + patch
Control: tags 986801 + pending
Dear maintainer,
I've prepared an NMU for gnuchess (versioned as 6.2.9-0.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
gnuchess.nmu.diff.gz
Description: GNU Zip compressed data
O
Processing control commands:
> tags 986801 + patch
Bug #986801 [gnuchess] CVE-2021-30184
Added tag(s) patch.
> tags 986801 + pending
Bug #986801 [gnuchess] CVE-2021-30184
Added tag(s) pending.
--
986801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986801
Debian Bug Tracking System
Contact
On Sat, Dec 14, 2024 at 07:38:50PM +0100, Ben Wiederhake wrote:
> Since wondershaper is orphaned, I suggest removing this package, but don't
> know
> how that process works.
You can use reportbug to file a bug against the (pseudo) package
"ftp.debian.org". reportbug will prompt your for the rest
Am Sat, Dec 14, 2024 at 10:36:33PM +0100 schrieb Jérémy Lal:
> Didn't you RM: ltx in https://bugs.debian.org/1088630 ?
Ups, yes, I did - thank you for the reminder
Andreas.
--
https://fam-tille.de
I think I understand now. I would like do what is needed for asterisk. My
current focus is the asterisk bug tracker, as you have mentioned.
Thanks again,
Martin
Processing commands for cont...@bugs.debian.org:
> fixed 1078295 2.1.0-1
Bug #1078295 {Done: Macy Lin } [src:lxqt-menu-data]
lxqt-menu-data: FTBFS: Could not find a package configuration file provided by
"lxqt2-build-tools"
Marked as fixed in versions lxqt-menu-data/2.1.0-1.
> thanks
Stopping pr
Your message dated Sat, 14 Dec 2024 22:38:08 +0100
with message-id
and subject line
has caused the Debian Bug report #1078295,
regarding lxqt-menu-data: FTBFS: Could not find a package configuration file
provided by "lxqt2-build-tools"
to be marked as done.
This means that you claim that the p
Le sam. 14 déc. 2024 à 22:33, Andreas Tille a écrit :
> Am Sat, Dec 14, 2024 at 04:26:33PM +0100 schrieb Jérémy Lal:
> > Le sam. 14 déc. 2024 à 15:09, Jérémy Lal a écrit :
> > > It's odd that it wasn't part of the last "auto-nodejs" ?
>
> I need to admit I have no deep knowledge about JS issues.
Package: sia
Severity: serious
Thanks for feedback Nilesh. I'm opening this bug to trigger removal
from testing of Sia so it doesn't end up in the release, see discussion
below. Of course, if anyone disagree and steps up to make the package
build again then just close this bug, but pending some
Am Sat, Dec 14, 2024 at 04:26:33PM +0100 schrieb Jérémy Lal:
> Le sam. 14 déc. 2024 à 15:09, Jérémy Lal a écrit :
> > It's odd that it wasn't part of the last "auto-nodejs" ?
I need to admit I have no deep knowledge about JS issues.
> Otherwise it might make sense to just remove that old and use
Processing commands for cont...@bugs.debian.org:
> # The transition didn't migrate to testing yet, so 0.17.4-1 can't be
> # "found"
> notfound 1085192 0.17.4-1
Bug #1085192 [src:wlroots] wlroots 0.18 transition
No longer marked as found in versions wlroots/0.17.4-1.
> found 1085192 0.18.0-1
Bug #1
Hi,
在 12/14/2024 2:50 PM, Sandro Tosi 写道:
On Sat, Dec 14, 2024 at 11:09 AM Boyuan Yang wrote:
Ping, is there any progress on it?
An email with a patch was sent just 7 hours prior to your message,
what kind of turn around are you expecting here?
Please let me know whether NMUs would work fo
Processing control commands:
> tags -1 patch
Bug #1086765 [src:kdiagram] kdiagram FTBFS with the nocheck build profile:
missing symbols
Added tag(s) patch.
--
1086765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Source: tryton-server
Version: 6.0.53-1
Severity: serious
Control: close -1 7.0.19-7
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 day
Control: tags -1 patch
This looks similar to kimap #1086766: nocheck turns off BUILD_TESTING,
and this package ships some items that are only built with that on.
(nocheck is not allowed to change the contents of a package.) The
upstream code even notes (at src/KGantt/CMakeLists.txt:15) that t
Processing control commands:
> close -1 7.0.19-7
Bug #1089934 [src:tryton-server] src:tryton-server: fails to migrate to testing
for too long
Marked as fixed in versions tryton-server/7.0.19-7.
Bug #1089934 [src:tryton-server] src:tryton-server: fails to migrate to testing
for too long
Marked Bu
Control: tags -1 patch
It needed ccb232e435ae3d83559486fce1fdb5866e07 as well, but now
builds and passes autopkgtests:
https://salsa.debian.org/qt-kde-team/extras/clazy/-/merge_requests/4
Alternatively, depending on llvm/clang 18 instead of unversioned, or
upgrading to an upstream git sna
Processing control commands:
> tags -1 patch
Bug #1084393 [src:clazy] clazy: FTBFS: error: 'void
ClazyPreprocessorCallbacks::[...]' marked 'override', but does not override
Bug #1085114 [src:clazy] clazy: Fails to build with llvm 19
Added tag(s) patch.
Added tag(s) patch.
--
1084393: https://bu
On 14/12/2024 at 20:41, Holger Wansing wrote:
Tests with multi-OS installations (up to 3 installations of bookworm,
trixie and sid all mixed together) on multi-disk (2 disks) worked fine here.
Thank you for testing.
I have noticed, that the first (temporarily) os-prober run, which is execute
On Sat, Dec 14, 2024 at 11:09 AM Boyuan Yang wrote:
> Ping, is there any progress on it?
An email with a patch was sent just 7 hours prior to your message,
what kind of turn around are you expecting here?
> Please let me know whether NMUs would work for you.
If you wanna work on something, here
Your message dated Sat, 14 Dec 2024 18:52:04 +
with message-id
and subject line Bug#1076233: fixed in liggghts 3.8.0+repack1-11
has caused the Debian Bug report #1076233,
regarding liggghts: FTBFS with mpich as default MPI provider on 32 bit
architectures: [mpiexec@arm-conova-03] main (mpiexe
Package: wondershaper
Version: 1.1a-12
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: ben.wiederh...@gmail.com
Dear Maintainer,
it seems that virtually any usage of wondershaper results in errors:
```
# wondershaper eno1 200 200
Unknown qdisc "cbq", hence op
Your message dated Sat, 14 Dec 2024 18:37:38 +
with message-id
and subject line Bug#1018673: fixed in yotta 0.20.5-7
has caused the Debian Bug report #1018673,
regarding yotta: build-depends on python3-nose or uses it for autopkgtest
to be marked as done.
This means that you claim that the pr
On 12/11/24 4:47 AM, Sunil Mohan Adapa wrote:
owner -1 !
thanks
On 10/12/24 12:59, Colin Watson wrote:
On Sat, Nov 30, 2024 at 10:21:32PM +0500, Andrey Rakhmatullin wrote:
https://ci.debian.net/packages/f/freedombox/testing/amd64/54950089/
288s plinth/modules/sso/privileged.py:78: in generate
Processing control commands:
> severity -1 grave
Bug #1089513 [nvidia-driver] nvidia-driver: crash in drm_open_helper on Linux
6.12.3
Severity set to 'grave' from 'normal'
--
1089513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089513
Debian Bug Tracking System
Contact ow...@bugs.debian.
X-Debbugs-CC: mo...@debian.org
On Sat, 2 Nov 2024 08:24:12 +0100 Paul Gevers wrote:
Source: python-cattrs
Version: 23.2.3-1
Severity: serious
X-Debbugs-CC: python-at...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-at
Processing control commands:
> severity -1 grave
Bug #1089513 [nvidia-driver] nvidia-driver: crash in drm_open_helper on Linux
6.12.3
Ignoring request to change severity of Bug 1089513 to the same value.
--
1089513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089513
Debian Bug Tracking S
Control: severity -1 grave
Can reproduce here, looks like older drivers are all incompatible with 6.12
I'm proposing this patch for ubuntu:
Description: Replace deprecated GIT_OBJ_XXX references
Author: Andreas Hasenack
Origin: vendor
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084258
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/git-ubuntu/+bug/2091778
Last-Update: 2024-
Your message dated Sat, 14 Dec 2024 16:40:45 +
with message-id
and subject line Bug#1089204: fixed in rust-lazy-regex 3.3.0+20241210-2
has caused the Debian Bug report #1089204,
regarding librust-lazy-regex-dev: Autopkgtest failure for --no-default-features
to be marked as done.
This means th
Your message dated Sat, 14 Dec 2024 16:40:45 +
with message-id
and subject line Bug#1089917: fixed in rust-lazy-regex 3.3.0+20241210-2
has caused the Debian Bug report #1089917,
regarding rust-lazy-regex - autopkgtest failure
to be marked as done.
This means that you claim that the problem ha
Processing commands for cont...@bugs.debian.org:
> close 1063408 2.1.1~dfsg2-4
Bug #1063408 [src:ontospy] ontospy's autopkg tests fail with Python 3.12
Marked as fixed in versions ontospy/2.1.1~dfsg2-4.
Bug #1063408 [src:ontospy] ontospy's autopkg tests fail with Python 3.12
Marked Bug as done
> t
Quoting Jérémy Lal (2024-12-14 16:26:33)
> Le sam. 14 déc. 2024 à 15:09, Jérémy Lal a écrit :
>
> >
> >
> > Le sam. 14 déc. 2024 à 14:24, Andreas Tille a écrit :
> >
> >> Package: node-node-expat
> >> Severity: grave
> >> Justification: renders package unusable
> >>
> >> Hi,
> >>
> >> I simply g
Processing control commands:
> unblock -1 by 1089204
Bug #1089894 [src:rust-ognibuild] rust-ognibuild: stuck in Unstable due to
broken dependencies
1089894 was blocked by: 1089204
1089894 was not blocking any bugs.
Removed blocking bug(s) of 1089894: 1089204
> block -1 by 1089917
Bug #1089894 [sr
Le sam. 14 déc. 2024 à 15:09, Jérémy Lal a écrit :
>
>
> Le sam. 14 déc. 2024 à 14:24, Andreas Tille a écrit :
>
>> Package: node-node-expat
>> Severity: grave
>> Justification: renders package unusable
>>
>> Hi,
>>
>> I simply get:
>>
>> $ sudo apt install node-node-expat
>> Some packages could
Package: librust-lazy-regex-dev
Followup-For: Bug #1089204
X-Debbugs-Cc: noisyc...@tutanota.com
Jonas,
Are you sure you are not mixing up bugs? This one is for an autopkgtest failure
that existed in v3.1, but currently (v3.3) there are other autopkgtest failures
which were just introduced upstrea
On Fri, 13 Dec 2024 15:18:50 +0100 Jan Binder
wrote:
> Thanks for looking into this, disabling the camera works as a stopgap
measure
Thanks for the replies and pointers to the fix.
I'll stay on 6.11 until the next 6.12 image is made available.
Antoine
Package: uci2wb
Version: 4.1+git200714-1
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for uci2wb (versioned as 4.1+git200714-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
This fixes both #1089904 and #1071727 (ftbfs).
Package: rust-lazy-regex
Version: 3.3.0+20241210-1
Severity: serious
rust-lazy-regex's autopkgtests are failing in most test
configurations due to lack of feature gates on tests.
The attatched debdiff adds said feature gates.
diff -Nru rust-lazy-regex-3.3.0+20241210/debian/changelog
rust-lazy-re
> Indeed I totally missed it. And your proposed patch (if working, which
> I am testing right now, restructered to instead extend existing feature
> fencing patch) is more elegant than giving up and skipping the test.
>
Thanks and I agree, it could be worth it not to disable the test. This is t
Processing commands for cont...@bugs.debian.org:
> block 1089894 with 1089204
Bug #1089894 [src:rust-ognibuild] rust-ognibuild: stuck in Unstable due to
broken dependencies
1089894 was not blocked by any bugs.
1089894 was not blocking any bugs.
Added blocking bug(s) of 1089894: 1089204
> thanks
S
Quoting NoisyCoil (2024-12-14 01:21:26)
> Package: librust-lazy-regex-dev
> Followup-For: Bug #1089204
> X-Debbugs-Cc: noisyc...@tutanota.com, d...@jones.dk
>
> Hi Jonas,
>
> I think you missed this bug, which was filed before plugwash's #1089813. This
> is RC too, so it will prevent migration. F
Source: djoser
Version: 2.1.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/sunscrapers/djoser/issues/795
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for djoser.
Making it RC to be on safe side.
CVE-2024-21543[0]
Le sam. 14 déc. 2024 à 14:24, Andreas Tille a écrit :
> Package: node-node-expat
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> I simply get:
>
> $ sudo apt install node-node-expat
> Some packages could not be installed. This may mean that you have
> requested an impossib
Your message dated Sat, 14 Dec 2024 13:52:35 +
with message-id <5dab04fa-db28-41b7-a1ad-27ef09486...@p10link.net>
and subject line re: librust-lazy-regex-dev: Autopkgtest failure for
--no-default-features
has caused the Debian Bug report #1089204,
regarding librust-lazy-regex-dev: Autopkgtest
Your message dated Sat, 14 Dec 2024 13:49:06 +
with message-id
and subject line Bug#1089849: fixed in blockdiag 3.0.0+dfsg-3
has caused the Debian Bug report #1089849,
regarding src:blockdiag: unsatisfied build dependency in testing:
libmagickcore-6.q16-3-extra
to be marked as done.
This mea
Package: gpa
Version: 0.11.0-1
Severity: serious
Tags: upstream
Dear Maintainer,
Filing a bug to keep gpa out of Trixie - gpa isn't well maintained, I have
done the conversion to GTK3, but it has no real maintainer upstream, and the
current version needs more work. There are threading that locks
Package: node-node-expat
Severity: grave
Justification: renders package unusable
Hi,
I simply get:
$ sudo apt install node-node-expat
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some requir
Your message dated Sat, 14 Dec 2024 12:20:46 +
with message-id
and subject line Bug#1089872: fixed in rust-coreutils 0.0.27-3
has caused the Debian Bug report #1089872,
regarding rust-coreutils: Spurious build dependency on unmaintained upstream
rust-users
to be marked as done.
This means th
Your message dated Sat, 14 Dec 2024 12:07:49 +
with message-id
and subject line Bug#1088958: fixed in comedilib 0.11.0+5-1.3
has caused the Debian Bug report #1088958,
regarding libcomedi0t64: empty, aliased directory /lib/udev/rules.d
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 1056840 - patch
Bug #1056840 [src:pyhst2] pyhst2: ftbfs with cython 3.0.x
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10568
Processing commands for cont...@bugs.debian.org:
> tags 1056885 - patch
Bug #1056885 [src:sagemath] sagemath: ftbfs with cython 3.0.x
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1
Processing commands for cont...@bugs.debian.org:
> tags 1056870 - patch
Bug #1056870 [src:python-rocksdb] python-rocksdb: ftbfs with cython 3.0.x
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056870: https://bugs.debian.org/cgi-bin/bugrepo
Processing commands for cont...@bugs.debian.org:
> tags 1056887 - patch
Bug #1056887 [src:sfepy] sfepy: ftbfs with cython 3.0.x
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056887
Processing commands for cont...@bugs.debian.org:
> tags 1056878 - patch
Bug #1056878 [src:qiskit-terra] qiskit-terra: ftbfs with cython 3.0.x
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056878: https://bugs.debian.org/cgi-bin/bugreport.c
Processing commands for cont...@bugs.debian.org:
> severity 1063408 serious
Bug #1063408 [src:ontospy] ontospy's autopkg tests fail with Python 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1063408: https://bugs.de
Processing commands for cont...@bugs.debian.org:
> tags 1056832 - patch
Bug #1056832 [src:pplpy] pplpy: ftbfs with cython 3.0.x
Removed tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056832
Source: rust-coreutils
Severity: serious
Justification: RT
X-Debbugs-Cc: noisyc...@tutanota.com
Dear Maintainer,
As agreed with you in [1], I'm about to file a removal request for rust-users
(see security Bug#1051808). rust-coreutils is the only package in the archive
that still depends on rust-u
Source: qemu
Version: 1:9.1.2+ds-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=qemu&arch=mips64el
mipsel-osuosl-04:
133/133 qemu:block / io-qcow2-220 TIMEOUT
180.12s killed by signal 15 SIGTERM
other current buildds:
133/133 qemu
Processing control commands:
> tags -1 + patch
Bug #1086614 [src:python-cattrs] python-cattrs: autopkgtest needs update for
new version of python-attrs
Added tag(s) patch.
--
1086614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086614
Debian Bug Tracking System
Contact ow...@bugs.debian.
Control: tags -1 + patch
The attached patch was applied in Ubuntu.
From: Anshul Singh
Date: Wed, 11 Dec 2024 14:05:50 +0530
Subject: Patch to stop generating nan values in tests to work with latest attrs
Origin: upstream, https://github.com/python-attrs/cattrs/commit/96ed9a1c972814c379f9ea8faa34
c-14 (14.2.0-11) unstable; urgency=medium
.
* Update to git 20241214 from the gcc-14 branch.
- Fix PR driver/117942, PR c++/117880, PR c++/117845,
PR target/117926 (x86), PR target/64242 (AVR), PR ada/117996,
PR c++/117615, PR fortran/109105, PR fortran/117843,
PR fortran/117
ke 11.12.2024 klo 15.31 Martin-Éric Racine (martin-eric.rac...@iki.fi)
kirjoitti:
>
> ke 11.12.2024 klo 15.21 Chris Hofstaedtler (z...@debian.org) kirjoitti:
> >
> > On Mon, Dec 09, 2024 at 06:06:32PM +0100, Daniel Gröber wrote:
> > > dhcpcd-base does not send the system's hostname by default as
>
Your message dated Sat, 14 Dec 2024 09:08:00 +
with message-id
and subject line Bug#1075544: fixed in sumalibs 1.0.36-4
has caused the Debian Bug report #1075544,
regarding sumalibs: ftbfs with GCC-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Processing commands for cont...@bugs.debian.org:
> reassign 1088142 python3-argcomplete
Bug #1088142 [src:virt-manager] virt-manager: FTBFS: AttributeError:
'MonkeyPatchedIntrospectiveArgumentParser' object has no attribute
'_action_conflicts'
Bug reassigned from package 'src:virt-manager' to 'p
Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-14 04:19:03)
> > Why later? Whay not now?
>
> My efforts to close this bug have failed.
The goal of this bug is not to have it closed, but to establish routines
that makes it unlikely for this bug to need reopening.
> I have already said
Processing control commands:
> tag -1 pending
Bug #1075544 [src:sumalibs] sumalibs: ftbfs with GCC-14
Added tag(s) pending.
--
1075544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1075544 in sumalibs 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/sumalibs/-/commit/2c4c029b8b2a8e848c95cbf5e9a6f
86 matches
Mail list logo
