Your message dated Wed, 21 Oct 2026 09:17:15 +0200
with message-id <[email protected]>
and subject line Re: Bug#1151495: new security release?
has caused the Debian Bug report #1151495,
regarding new security release?
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 your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1151495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151495
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-certifi
Version: 2026.7.22+ds-1
Severity: serious
Per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151413, package
should be updated quickly to latest release
https://github.com/certifi/python-certifi/tags
--- End Message ---
--- Begin Message ---
Hi,
On Wed, Oct 21, 2026 at 07:31:37AM +0200, VA wrote:
> Le 21/10/2026 à 06:09, Salvatore Bonaccorso a écrit :
> > Control: tags -1 + moreinfo
> >
> > On Tue, Oct 20, 2026 at 11:02:46PM +0200, VA wrote:
> > > Package: python3-certifi
> > > Version: 2026.7.22+ds-1
> > > Severity: serious
> > >
> > > Per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151413, package
> > > should be updated quickly to latest release
> > > https://github.com/certifi/python-certifi/tags
> >
> > Debian's python-certifi uses the system provided ca-certificates:
> >
> > Description-en: root certificates for validating SSL certs and verifying
> > TLS hosts (python3)
> > Certifi is a carefully curated collection of Root Certificates for
> > validating the trustworthiness of SSL certificates while verifying
> > the identity of TLS hosts. It has been extracted from the Requests
> > project.
> > .
> > The version of certifi in this Debian package is patched to return
> > the location of Debian-provided CA certificates, instead of those
> > packaged by upstream.
> > .
> > This is the python3 package.
> >
> > Is there anything we had an oversight and thus still requiring an
> > immediate action on python-certifi?
>
> Missed that, especially since it seemed to follow upstream version numbers.
> So I guess this can be closed.
Thanks for the quick feedback!
Regards,
Salvatore
--- End Message ---
