Hi,
Am 15. Juli 2025 21:45:10 MESZ schrieb Soren Stoutner :
>On Tuesday, July 15, 2025 4:47:45 AM Mountain Standard Time Rene Engelhard
>wrote:
>> Hi,
>>
>> yes, I also think at least nl_BE (if not all) definitely should be put back.
>>
>> There was no reason to remove them - in contrast...
Hi,
Thanks. fyi I reproduced the bug. Now trying to figure out it. Thanks
for the confirmation.
--
cheers,
Emmanuel Arias
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
⠈⠳⣄
signature.asc
Description: PGP signatu
Processing commands for cont...@bugs.debian.org:
> severity 1109039 wishlist
Bug #1109039 [tin] tin: after upgrade, some user configuration is removed
Severity set to 'wishlist' from 'grave'
> tags 1109039 + upstream
Bug #1109039 [tin] tin: after upgrade, some user configuration is removed
Added t
Your message dated Wed, 16 Jul 2025 00:48:55 +
with message-id
and subject line Bug#1109315: fixed in hunspell-bo 0.4.0-3
has caused the Debian Bug report #1109315,
regarding hunspell-bo: dictionary not working with LibreOffice
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 16 Jul 2025 00:18:59 +
with message-id
and subject line Bug#1109305: fixed in hunspell-ar 3.5.2014-11-08-4
has caused the Debian Bug report #1109305,
regarding hunspell-ar: dictionary not working with LibreOffice
to be marked as done.
This means that you claim that the
Your message dated Tue, 15 Jul 2025 22:48:56 +
with message-id
and subject line Bug#1101238: fixed in lua-lgi 0.9.2-4
has caused the Debian Bug report #1101238,
regarding lua-lgi: FTBFS: tests/pango.lua:43: failure
to be marked as done.
This means that you claim that the problem has been deal
On Tue, 2025-07-15 at 22:08 +0100, Rebecca N. Palmer wrote:
>
> > I could get test_nanny to never throw an error in the loop by
> > adding
> > await asyncio.sleep(0.1) into the function before it started trying
> > to
> > use the cluster
>
> That's plausibly a better idea, but I haven't tried it
Processing control commands:
> tags -1 + patch upstream
Bug #1101238 [src:lua-lgi] lua-lgi: FTBFS: tests/pango.lua:43: failure
Added tag(s) patch and upstream.
--
1101238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Control: tags -1 + patch upstream
Hi Reiner,
On Tue, Jul 15, 2025 at 11:39:23PM +0200, Chris Hofstaedtler wrote:
> https://gitlab.gnome.org/GNOME/pango/-/merge_requests/829
> looks like the "smoking gun". Especially the change in fwupd looks
> relevant: https://github.com/fwupd/fwupd/issues/8587
On Tue, Jul 15, 2025 at 11:33:30PM +0200, Chris Hofstaedtler wrote:
> Hi Reiner,
>
> On Tue, Jul 15, 2025 at 11:10:25PM +0200, Reiner Herrmann wrote:
> > Hi Chris,
> >
> > On Tue, Jul 15, 2025 at 11:04:00PM +0200, Chris Hofstaedtler wrote:
> > > On Tue, Mar 25, 2025 at 12:11:09AM +, Santiago
Hi Reiner,
On Tue, Jul 15, 2025 at 11:10:25PM +0200, Reiner Herrmann wrote:
> Hi Chris,
>
> On Tue, Jul 15, 2025 at 11:04:00PM +0200, Chris Hofstaedtler wrote:
> > On Tue, Mar 25, 2025 at 12:11:09AM +, Santiago Vila wrote:
> > > Package: src:lua-lgi
> >
> thanks for bisecting.
> But it seems
Also fails in Salsa CI if you enable that (implying that it *doesn't*
have to be the same chroot for build and autopkgtest):
https://salsa.debian.org/python-team/packages/python-nxtomomill/-/jobs/7829569
Hi Chris,
On Tue, Jul 15, 2025 at 11:04:00PM +0200, Chris Hofstaedtler wrote:
> On Tue, Mar 25, 2025 at 12:11:09AM +, Santiago Vila wrote:
> > Package: src:lua-lgi
>
> FTR, debbisect says:
>
> bisection finished successfully
> last good timestamp: 20240103T032204Z
> first bad timestamp:
This can be reverted once LibreOffice fixes the bug that this is working
around.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109253
--
Soren Stoutner
so...@debian.org
signature.asc
Description: This is a digitally signed message part.
On 15/07/2025 18:13, Diane Trout wrote:
, but I'm not sure that's necessary given all the pytest
and autopkgtest configuration to rerun flaky tests.
Should I push a new dask.distributed with the scipy fix and see if the
current flaky test handling is sufficient?
No, because this already shows
On Tue, Mar 25, 2025 at 12:11:09AM +, Santiago Vila wrote:
> Package: src:lua-lgi
FTR, debbisect says:
bisection finished successfully
last good timestamp: 20240103T032204Z
first bad timestamp: 20240103T211436Z
the following packages differ between the last good and first bad timestamp:
On 2025-06-25, Salvatore Bonaccorso wrote:
> CVE-2025-46415[0], CVE-2025-46416[1], CVE-2025-52991[2],
> CVE-2025-52992[3], CVE-2025-52993[4].
The upstream patchset to fix this is comingled with a lot of other
upstream changes, but there is some work and discussion about
backporting the needed fixe
Processing commands for cont...@bugs.debian.org:
> forwarded 1109335 https://issues.apache.org/jira/browse/JCR-5165
> https://github.com/apache/jackrabbit/pull/263
Bug #1109335 [jackrabbit] jackrabbit: CVE-2025-53689
Set Bug forwarded-to-address to 'https://issues.apache.org/jira/browse/JCR-5165
Processing commands for cont...@bugs.debian.org:
> found 1109335 2.20.11-1
Bug #1109335 [jackrabbit] jackrabbit: CVE-2025-53689
There is no source info for the package 'jackrabbit' at version '2.20.11-1'
with architecture ''
Unable to make a source version for version '2.20.11-1'
Marked as found
On Tuesday, July 15, 2025 4:47:45 AM Mountain Standard Time Rene Engelhard
wrote:
> Hi,
>
> yes, I also think at least nl_BE (if not all) definitely should be put back.
>
> There was no reason to remove them - in contrast...
I disagree.
Country or region specific dictionaries should only exist
Your message dated Tue, 15 Jul 2025 21:00:14 +0200
with message-id
and subject line Re: redis: CVE-2025-27151
has caused the Debian Bug report #1106822,
regarding redis: CVE-2025-27151
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Source: redis
Source-Version: 5:8.0.2-2
Hi
On Tue, Jul 15, 2025 at 05:27:38PM +0200, Paul Gevers wrote:
> Hi,
>
> On Fri, 30 May 2025 12:10:13 -0700 "Chris Lamb" wrote:
> > This is fixed in Git by updating to the 8.0.2 point release. I will
> > upload once I get clarity on the status of 8.0.x i
On Tue, 2025-07-15 at 12:54 +0100, Rebecca N. Palmer wrote:
> dask.distributed has both an explicit autopkgtest that is marked as
> flaky, and a pybuild-autopkgtest that isn't, that run mostly the same
> tests. (The git log says this is to have both a needs-internet and a
> non-needs-internet tes
Your message dated Tue, 15 Jul 2025 17:04:40 +
with message-id
and subject line Bug#1104927: fixed in ruby-rack 3.1.16-0.1
has caused the Debian Bug report #1104927,
regarding ruby-rack: CVE-2025-46727
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Tue, 15 Jul 2025 17:04:40 +
with message-id
and subject line Bug#1109027: fixed in ruby-rack 3.1.16-0.1
has caused the Debian Bug report #1109027,
regarding ruby-rack: autopkgtest depends on packages which have been removed
to be marked as done.
This means that you claim th
Your message dated Tue, 15 Jul 2025 09:34:03 -0700
with message-id
and subject line Re: Bug#1106822: redis: CVE-2025-27151
has caused the Debian Bug report #1106822,
regarding redis: CVE-2025-27151
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
Control: tags -1 patch
I am uploading a NMU to fix this.
Please find the debdiff attached.
diff -Nru ruby-rack-3.1.12/CHANGELOG.md ruby-rack-3.1.16/CHANGELOG.md
--- ruby-rack-3.1.12/CHANGELOG.md 2025-03-10 22:21:44.0 +0100
+++ ruby-rack-3.1.16/CHANGELOG.md 2025-06-05 00:27:50.0
Processing control commands:
> tags -1 patch
Bug #1104927 [src:ruby-rack] ruby-rack: CVE-2025-46727
Added tag(s) patch.
--
1104927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
On Fri, 30 May 2025 12:10:13 -0700 "Chris Lamb" wrote:
This is fixed in Git by updating to the 8.0.2 point release. I will
upload once I get clarity on the status of 8.0.x in trixie.
The upload of 8.0.2 already happened, but this bug isn't closed. I
assume that's just an oversight?
Wit
Processing commands for cont...@bugs.debian.org:
> tags 1109336 + upstream
Bug #1109336 [python-aiohttp] python-aiohttp: CVE-2025-53643
Added tag(s) upstream.
> tags 1109334 + upstream
Bug #1109334 [policykit-1] policykit-1: CVE-2025-7519
Added tag(s) upstream.
> tags 1109335 + upstream
Bug #11093
Hi Christian,
On Sun, Jul 13, 2025 at 08:45:02AM +0200, Christian Kastner wrote:
> Hi Salvatore,
>
> On 2025-07-13 07:49, Salvatore Bonaccorso wrote:
> > On Sat, Jul 12, 2025 at 12:04:34AM +0200, Christian Kastner wrote:
> >> Nevertheless, I really need to figure out a better way to deal with
> >
dask.distributed has both an explicit autopkgtest that is marked as
flaky, and a pybuild-autopkgtest that isn't, that run mostly the same
tests. (The git log says this is to have both a needs-internet and a
non-needs-internet test, but the set of tests also differs because they
have different
Package: rlottie
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for rlottie.
CVE-2025-0634[0]:
| Use After Free vulnerability in Samsung Open Source rLottie allows
| Remote Code Inclusion.This issue affects rLottie: V0.2.
h
Package: cpp-httplib
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for cpp-httplib.
CVE-2025-52887[0]:
| cpp-httplib is a C++11 single-file header-only cross platform
| HTTP/HTTPS library. In version 0.21.0, when many http
Package: imagemagick
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for imagemagick.
CVE-2025-53014[0]:
| ImageMagick is free and open-source software used for editing and
| manipulating digital images. Versions prior to 7.1
Your message dated Tue, 15 Jul 2025 12:36:13 +
with message-id
and subject line Bug#1104928: fixed in ruby-rack-session 2.1.1-0.1
has caused the Debian Bug report #1104928,
regarding ruby-rack-session: CVE-2025-46336
to be marked as done.
This means that you claim that the problem has been de
Package: jackrabbit
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for jackrabbit.
CVE-2025-53689[0]:
| Blind XXE Vulnerabilities in jackrabbit-spi-commons and jackrabbit-
| core in Apache Jackrabbit < 2.23.2 due to usage of an
Control: tags -1 patch
I am uploading a NMU to fix this.
Please find the debdiff attached.
diff -Nru ruby-rack-session-2.1.0/debian/changelog
ruby-rack-session-2.1.1/debian/changelog
--- ruby-rack-session-2.1.0/debian/changelog2025-03-08 16:10:24.0
+0100
+++ ruby-rack-session-2.1.1/d
Processing control commands:
> tags -1 patch
Bug #1104928 [src:ruby-rack-session] ruby-rack-session: CVE-2025-46336
Added tag(s) patch.
--
1104928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
yes, I also think at least nl_BE (if not all) definitely should be put back.
There was no reason to remove them - in contrast...
Regards,
Rene
Processing commands for cont...@bugs.debian.org:
> close 1109121
Bug #1109121 [src:rsyslog] rsyslog: tainted by “AI”
Marked Bug as done
> tags 1109121 + wontfix
Bug #1109121 {Done: Michael Biebl } [src:rsyslog] rsyslog:
tainted by “AI”
Added tag(s) wontfix.
> thanks
Stopping processing here.
Ple
Note that the verion in stable has:
lrwxrwxrwx 1 root root 6 Jan 12 2021 /usr/share/hunspell/nl_AW.dic -> nl.dic
lrwxrwxrwx 1 root root 6 Jan 12 2021 /usr/share/hunspell/nl_BE.dic -> nl.dic
lrwxrwxrwx 1 root root 6 Jan 12 2021 /usr/share/hunspell/nl_NL.dic -> nl.dic
lrwxrwxrwx 1 root root 6 Jan
Hi,
On 13-07-2025 17:35, Andrej Shadura wrote:
This is, obviously, not going to work, as bmake doesn’t support *any* long
(dash-dash) options, and does not support job servers at all. Which means the
debhelper integration module has to filter out all long options out of
MAKEFLAGS:
@@ -56,6 +
Hi,
Am 14.07.25 um 22:17 schrieb Rene Engelhard:
Check in a running LibreOffice what it detects in "Tools -> Options -> Writing Aids" and
what it sees. I'd bet it didn't see Dutch ("Whatever")
Sorry,
Tools->Languages and Locales->Writing Aids. (Choose Hunspell and click on Edit)
It _does_ s
44 matches
Mail list logo
