Package: elinks
Version: 0.13.2-1+b4
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: user@thishost.mailname
Dear Maintainer,
"double free or corruption (fasttop)" in Elinks bookmark manager: writes
infinite temporary file
Operating system and version:
user@debian:~$ unam
On 26-May-2025, Adrian Bunk wrote:
> The binary-all package built on the autobuilder 10 years ago, this is a
> recent (not in bookworm) breakage due to AFAIR a dpkg change.
Thank you for this explanation, and the minimal patch. This saves me a
bunch of time debugging.
--
\ “Courage is re
Processing commands for cont...@bugs.debian.org:
> affects 1106880 src:cif-tools src:dssp
Bug #1106880 [src:libmcfp] libmcfp: version 1.4.2-1 breaks cif-tools and dssp
Added indication that 1106880 affects src:cif-tools and src:dssp
> thanks
Stopping processing here.
Please contact me if you need
Package: src:libmcfp
Version: 1.4.2-1
Severity: grave
Tags: sid
Dear maintainer:
During a rebuild of all packages in unstable, packages "cif-tools"
and "dssp" no longer build from source because of the new libmcfp-dev.
cif-tools fails in this way:
--
El 30/5/25 a las 23:23, Santiago Vila escribió:
I'm going to mark this as "not happening in trixie" to be consistent with
the above. [...]
Note: I actually did that three days ago by dropping the trixie tag,
I just did not remember that it was precisely this bug... Sorry for my
confusion.
( It
On 2025-05-30 23:23, Santiago Vila wrote:
El 30/5/25 a las 23:10, Drew Parsons escribió:
Source: pymatgen
Followup-For: Bug #1106436
Ah true, in this case the test failure is more specific.
uncertainties/3.2.3-2 was uploaded in the middle of the package
freeze,
and seems to be triggering fai
tags 1106436 sid
thanks
El 30/5/25 a las 23:10, Drew Parsons escribió:
Source: pymatgen
Followup-For: Bug #1106436
Ah true, in this case the test failure is more specific.
uncertainties/3.2.3-2 was uploaded in the middle of the package freeze,
and seems to be triggering failure in pymatgen's
T
Processing commands for cont...@bugs.debian.org:
> tags 1106436 sid
Bug #1106436 [src:pymatgen] pymatgen: FTBFS:
TestInterfaceReaction.test_get_entry_energy fails
Ignoring request to alter tags of bug #1106436 to the same tags previously set
> thanks
Stopping processing here.
Please contact me i
Processing commands for cont...@bugs.debian.org:
> tags 1106436 - trixie
Bug #1106436 [src:pymatgen] pymatgen: FTBFS:
TestInterfaceReaction.test_get_entry_energy fails
Ignoring request to alter tags of bug #1106436 to the same tags previously set
> thanks
Stopping processing here.
Please contact
Source: pymatgen
Followup-For: Bug #1106436
Ah true, in this case the test failure is more specific.
uncertainties/3.2.3-2 was uploaded in the middle of the package freeze,
and seems to be triggering failure in pymatgen's
TestInterfaceReaction.test_get_entry_energy
Should uncertainties/3.2.3-2 b
Your message dated Fri, 30 May 2025 23:01:40 +0200
with message-id
and subject line
has caused the Debian Bug report #1104776,
regarding qt-style-kvantum has a file conflict
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now y
El 30/5/25 a las 22:35, Drew Parsons escribió:
Source: pymatgen
Followup-For: Bug #1106436
pymatgen tests are known to be broadly flakey.
If you run your build test again, it will likely pass.
That's not how it works.
By the time I get to the point of reporting a FTBFS bugs,
I've already tri
Source: pymatgen
Followup-For: Bug #1106436
pymatgen tests are known to be broadly flakey.
If you run your build test again, it will likely pass.
Your message dated Fri, 30 May 2025 19:51:22 +
with message-id
and subject line Bug#1106807: fixed in tini 0.19.0-3
has caused the Debian Bug report #1106807,
regarding tini: statically linked against glibc without a Built-Using: field
to be marked as done.
This means that you claim that the
Your message dated Fri, 30 May 2025 19:48:29 +
with message-id
and subject line Bug#1106689: fixed in libvpx 1.12.0-1+deb12u4
has caused the Debian Bug report #1106689,
regarding libvpx: double-free in vpx_codec_enc_init_multi
to be marked as done.
This means that you claim that the problem h
Your message dated Fri, 30 May 2025 19:48:22 +
with message-id
and subject line Bug#1105885: fixed in libavif 0.11.1-1+deb12u1
has caused the Debian Bug report #1105885,
regarding libavif: CVE-2025-48174
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 30 May 2025 19:48:22 +
with message-id
and subject line Bug#1105883: fixed in libavif 0.11.1-1+deb12u1
has caused the Debian Bug report #1105883,
regarding libavif: CVE-2025-48175
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> # make sure we get fixes in trixie in abundance of safety
> severity 1106737 grave
Bug #1106737 [src:isc-kea] isc-kea: CVE-2025-32801 CVE-2025-32802 CVE-2025-32803
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please
tags 1106822 + pending
thanks
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.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Processing commands for cont...@bugs.debian.org:
> tags 1106822 + pending
Bug #1106822 [src:redis] redis: CVE-2025-27151
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1106822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106822
Debian
Your message dated Fri, 30 May 2025 18:21:31 +
with message-id
and subject line Bug#1104872: fixed in python-django 3:5.2.1-1
has caused the Debian Bug report #1104872,
regarding python-django: CVE-2025-32873 -- Denial-of-service possibility in
strip_tags()
to be marked as done.
This means t
I didn't find a reason yet why it fails now, for this rebuild. I would
guess that the builder is somehow configured differently from all the
others, but that's pure speculation.
Hello. I can reproduce this error on a machine running arm64.
The arm64 machine is not configured differently.
If yo
Your message dated Fri, 30 May 2025 17:49:35 +
with message-id
and subject line Bug#1106796: fixed in busybox 1:1.37.0-5
has caused the Debian Bug report #1106796,
regarding busybox-static: statically linked against glibc without a
Built-Using: field
to be marked as done.
This means that you
On 2025-05-30 Aurelien Jarno wrote:
> control: tag -1 + patch
> Hi,
> On 2025-05-29 22:53, Aurelien Jarno wrote:
> > Package: gpgv-static
> > Version: 2.1.15-9
> > Severity: serious
> > Justification: Policy 7.8
> >
> > Dear maintainer,
> >
> > The gpgv-static package provides /usr/bin/gpgv-st
Hi Andreas,
On 2025-05-30 19:18, Andreas Metzler wrote:
> On 2025-05-30 Aurelien Jarno wrote:
> > control: tag -1 + patch
>
> > Hi,
>
> > On 2025-05-29 22:53, Aurelien Jarno wrote:
> > > Package: gpgv-static
> > > Version: 2.1.15-9
> > > Severity: serious
> > > Justification: Policy 7.8
> > >
tags 1106316 patch
thanks
Hello.
There was already a patch called
0001-Don-t-hard-fail-on-slow-systems.-624.patch
to fix a similar problem in another test. If you were to do the same
with "TestSignDetached", which is the failing test now, I suppose you
would do as in the attached patch.
This
Processing commands for cont...@bugs.debian.org:
> tags 1106316 patch
Bug #1106316 [src:gitsign] gitsign: FTBFS in testing/arm64: dh_auto_test fails
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1106316: https://bugs.debian.org/cgi-bin/bugrep
Processing commands for cont...@bugs.debian.org:
> fixed 1106785 254.26-1~bpo12+1
Bug #1106785 {Done: Luca Boccassi } [src:systemd] systemd:
CVE-2025-4598: Local information disclosure in systemd-coredump
The source 'systemd' and version '254.26-1~bpo12+1' do not appear to match any
binary packa
Processing commands for cont...@bugs.debian.org:
> found 1106785 254.22-1~bpo12+1
Bug #1106785 {Done: Luca Boccassi } [src:systemd] systemd:
CVE-2025-4598: Local information disclosure in systemd-coredump
Marked as found in versions systemd/254.22-1~bpo12+1.
>
End of message, stopping processing
Control: tag -1 pending
Hello,
Bug #1106796 in busybox 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/installer-team/busybox/-/commit/ceee9cf346a0b8ab4c90edb46
Processing control commands:
> tag -1 pending
Bug #1106796 [busybox-static] busybox-static: statically linked against glibc
without a Built-Using: field
Added tag(s) pending.
--
1106796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106796
Debian Bug Tracking System
Contact ow...@bugs.debi
Processing control commands:
> close -1 2.4.0
Bug #1106853 [src:mini-buildd] src:mini-buildd: fails to migrate to testing for
too long
Marked as fixed in versions mini-buildd/2.4.0.
Bug #1106853 [src:mini-buildd] src:mini-buildd: fails to migrate to testing for
too long
Marked Bug as done
--
1
Processing control commands:
> close -1 3.11.1-1
Bug #1106855 [src:actiona] src:actiona: fails to migrate to testing for too long
Marked as fixed in versions actiona/3.11.1-1.
Bug #1106855 [src:actiona] src:actiona: fails to migrate to testing for too long
Marked Bug as done
--
1106855: https://
Source: actiona
Version: 3.10.1-1
Severity: serious
Control: close -1 3.11.1-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 as h
Source: mini-buildd
Version: 2.2.8
Severity: serious
Control: close -1 2.4.0
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
On Fri, May 30, 2025 at 09:00:35AM +0200, Chris Hofstaedtler wrote:
> Here's an example I found using codesearch, from the grub package...
Thanks for the example. I tried doing a Google search, but I couldn't
find anything relevant, perhaps because of robot.txt constraints. In
particular there w
control: tag -1 + patch
Hi,
On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: snapd
> Version: 2.57.6-1
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The snapd package provides the following files which are statically
> linked against glibc:
> /usr/lib/snapd/snap-
Processing control commands:
> tag -1 + patch
Bug #1106808 [snapd] snapd: statically linked against glibc without a
Built-Using: field
Added tag(s) patch.
--
1106808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tag -1 + patch
Hi,
On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: sash
> Version: 3.8-5
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The sash packages provides /usr/bin/sash which is statically
> linked against glibc
>
> glibc is mostly is mostly lic
control: tag -1 + patch
Hi,
On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: busybox-static
> Version: 1:1.37.0-4
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The busybox-static package provides /usr/bin/busybox which is statically
> linked against glibc.
>
>
Processing control commands:
> tag -1 + patch
Bug #1106796 [busybox-static] busybox-static: statically linked against glibc
without a Built-Using: field
Added tag(s) patch.
--
1106796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106796
Debian Bug Tracking System
Contact ow...@bugs.debian
Your message dated Fri, 30 May 2025 13:19:31 +
with message-id
and subject line Bug#1106803: fixed in lxc 1:6.0.4-4
has caused the Debian Bug report #1106803,
regarding liblxc-common: statically linked against glibc without a Built-Using:
field
to be marked as done.
This means that you claim
Package: debvm
Version: 0.4.1
Tags: patch
Affects: src:systemd
Severity: serious
Justification: blocks another (key) package's migration
debefivm-create tries to copy over the systemd stub binary, but only
depends on the 'systemd-boot' integration package. The stub is in the
systemd-boot-efi packa
Processing control commands:
> reopen -1
Bug #1106807 {Done: ChangZhuo Chen (陳昌倬) } [tini] tini:
statically linked against glibc without a Built-Using: field
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add the
control: reopen -1
control: tag -1 + patch
Hi,
On 2025-05-30 10:07, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the tini package:
>
> #1106807: tini: statically linked against glibc without a Built-Using: field
>
> It
Your message dated Fri, 30 May 2025 11:34:43 +
with message-id
and subject line Bug#1106797: fixed in catatonit 0.2.1-2
has caused the Debian Bug report #1106797,
regarding catatonit: statically linked against glibc without a Built-Using:
field
to be marked as done.
This means that you claim
Works again now.
On Fri, 30 May 2025 at 12:55, Carl Winback wrote:
> Package: www.debian.org
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: c...@tunnel53.net
>
> Dear Maintainer,
>
> Package search is currently unavailable.
>
> See e.g. this URL:
>
> https://packages
Your message dated Fri, 30 May 2025 11:04:41 +
with message-id
and subject line Bug#1106795: fixed in bglibs 2.04+dfsg-8
has caused the Debian Bug report #1106795,
regarding libbg-dev: statically linked against glibc without a Built-Using:
field
to be marked as done.
This means that you clai
Processing control commands:
> tag -1 + pending
Bug #1106802 [libcap2] libcap2: statically linked against glibc without a
Built-Using: field
Added tag(s) pending.
--
1106802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
control: tag -1 + pending
On 2025-05-30 11:59, Aurelien Jarno wrote:
> control: tag -1 + patch
Thanks, Aurelien. I've prepared a new release with your fix for stable
and unstable, and will ask for an unblock over the weekend.
Best,
Christian
Package: www.debian.org
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: c...@tunnel53.net
Dear Maintainer,
Package search is currently unavailable.
See e.g. this URL:
https://packages.debian.org/search?searchon=contents&keywords=emacs&mode=path&suite=stable&arch=any
The re
Processing control commands:
> tag -1 + patch
Bug #1106799 [e2fsck-static] e2fsck-static: statically linked against glibc
without a Built-Using: field
Added tag(s) patch.
--
1106799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106799
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> tag -1 + patch
Bug #1106797 [catatonit] catatonit: statically linked against glibc without a
Built-Using: field
Added tag(s) patch.
--
1106797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
control: tag -1 + patch
Hi,
On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: catatonit
> Version: 0.1.7-1
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The catatonit package provides /usr/bin/catatonit which is statically
> linked against glibc.
>
> glibc is mos
Processing control commands:
> tag -1 + patch
Bug #1106793 [balboa-backend-common] balboa: statically linked against glibc
without a Built-Using: field
Added tag(s) patch.
--
1106793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106793
Debian Bug Tracking System
Contact ow...@bugs.debian.
control: tag -1 + patch
Hi,
On 2025-05-29 22:43, Aurelien Jarno wrote:
> Package: balboa-backend-common
> Version: 2.0.0+ds-5
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The balboa package provides /usr/bin/balboa-backend-console which is
> statically linked against
Processing control commands:
> tag -1 + patch
Bug #1106806 [sash] sash: statically linked against glibc without a
Built-Using: field
Added tag(s) patch.
--
1106806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hello,
On Fri 30 May 2025 at 01:50am -07, Xiyue Deng wrote:
> Ah I see, then yeah. (Though I would expect FTP masters to be more
> focused on the release, plus emacs-wfnames probably won't have a sponsor
> before Trixie :P)
They've nothing to do before the actual release day.
--
Sean Whitton
Sean Whitton writes:
> Hello,
>
> On Thu 29 May 2025 at 03:45pm -07, Xiyue Deng wrote:
>
>> Hi Sean,
>>
>> Sean Whitton writes:
>>
>>> Hello Xiyue,
>>>
>>> Thank you very much for considering taking on this package.
>>>
>>> One issue is that no NEW packages are allowed into testing during the
>>
Your message dated Fri, 30 May 2025 10:05:04 +
with message-id
and subject line Bug#1106807: fixed in tini 0.19.0-2
has caused the Debian Bug report #1106807,
regarding tini: statically linked against glibc without a Built-Using: field
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 + patch
Bug #1106803 [liblxc-common] liblxc-common: statically linked against glibc
without a Built-Using: field
Added tag(s) patch.
--
1106803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106803
Debian Bug Tracking System
Contact ow...@bugs.debian.o
Processing control commands:
> tag -1 + patch
Bug #1106802 [libcap2] libcap2: statically linked against glibc without a
Built-Using: field
Added tag(s) patch.
--
1106802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
control: tag -1 + patch
Hi,
On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: liblxc-common
> Version: 1:5.0.2-1
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The liblxc-common package provides /usr/sbin/init.lxc.static which is
> statically linked against glibc.
control: tag -1 + patch
Hi,
On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: libcap2
> Version: 1:2.75-6
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The libcap2 package provides the following files which are statically
> linked against glibc:
>
> /usr/lib/x86_
control: tag -1 + patch
Hi,
On 2025-05-29 22:53, Aurelien Jarno wrote:
> Package: gpgv-static
> Version: 2.1.15-9
> Severity: serious
> Justification: Policy 7.8
>
> Dear maintainer,
>
> The gpgv-static package provides /usr/bin/gpgv-static which is
> statically linked against glibc.
>
> glibc
Processing control commands:
> tag -1 + patch
Bug #1106800 [gpgv-static] gpgv-static: statically linked against glibc without
a Built-Using: field
Added tag(s) patch.
--
1106800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106800
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Your message dated Fri, 30 May 2025 09:51:03 +
with message-id
and subject line Bug#1106801: fixed in integrit 4.1-7
has caused the Debian Bug report #1106801,
regarding integrit: statically linked against glibc without a Built-Using: field
to be marked as done.
This means that you claim that
control: tag -1 + patch
Hi,
On 2025-05-30 09:00, Chris Hofstaedtler wrote:
> * Theodore Ts'o [250530 02:15]:
> > On Thu, May 29, 2025 at 10:53:20PM +0200, Aurelien Jarno wrote:
> > > Package: e2fsck-static
> > > Version: 1.40.4-1
> > > Severity: serious
> > > Justification: Policy 7.8
> > >
>
Package: python3-datalad
Followup-For: Bug #1099382
Control: reopen -1
still recommends python3-lzma package, which does not exist in debian.
Processing control commands:
> reopen -1
Bug #1099382 {Done: Yaroslav Halchenko }
[python3-datalad] python3-datalad: recommends unavailable packages
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug re
Hello,
On Thu 29 May 2025 at 03:45pm -07, Xiyue Deng wrote:
> Hi Sean,
>
> Sean Whitton writes:
>
>> Hello Xiyue,
>>
>> Thank you very much for considering taking on this package.
>>
>> One issue is that no NEW packages are allowed into testing during the
>> freeze. You would need a special exc
Processing commands for cont...@bugs.debian.org:
> # hmmm, just spotted that this reopens the bug too
> close 1106376
Bug #1106376 [src:python-redis] redis breaks python-redis autopkgtest on arm64,
ppc64el, riscv64 and s390x
Marked Bug as done
> thanks
Stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
> # fix meta data, otherwise the bts and britney make wrong assumptions
> reassign 1106376 src:python-redis
Bug #1106376 {Done: Chris Lamb } [src:redis,
src:python-redis] redis breaks python-redis autopkgtest on arm64, ppc64el,
riscv64 and s390x
B
* Theodore Ts'o [250530 02:15]:
On Thu, May 29, 2025 at 10:53:20PM +0200, Aurelien Jarno wrote:
Package: e2fsck-static
Version: 1.40.4-1
Severity: serious
Justification: Policy 7.8
Dear maintainer,
The e2fsck-static package provides /usr/sbin/e2fsck.static which is
statically linked against g
74 matches
Mail list logo
