From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: schroot: update to 1.6.10-12+deb11u1. CVE-2022-2787
Date: Sun, 21 Aug 2022 13:57:39 +0200 [thread overview]
Message-ID: <20220821115739.lY7Qta-dPvrMocud9Hzlk3mgPChJ79a7rvw13DdPOys@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38779@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 412 bytes --]
There's a merged pull request on the void-packages repository
schroot: update to 1.6.10-12+deb11u1. CVE-2022-2787
https://github.com/void-linux/void-packages/pull/38779
Description:
**Fix CVE-2022-2787 and update to Debian Bullseye package**
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
prev parent reply other threads:[~2022-08-21 11:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 8:12 [PR PATCH] schroot: update to 1.6.10-12+deb11u1 dataCobra
2022-08-19 8:20 ` schroot: update to 1.6.10-12+deb11u1. CVE-2022-2787 dataCobra
2022-08-19 8:22 ` dataCobra
2022-08-19 8:25 ` dataCobra
2022-08-19 14:17 ` [PR REVIEW] " classabbyamp
2022-08-19 14:17 ` classabbyamp
2022-08-19 17:36 ` sgn
2022-08-19 17:46 ` sgn
2022-08-19 17:47 ` dataCobra
2022-08-19 17:48 ` dataCobra
2022-08-19 17:50 ` dataCobra
2022-08-20 8:18 ` dataCobra
2022-08-20 8:20 ` thypon
2022-08-20 8:26 ` [PR PATCH] [Updated] " dataCobra
2022-08-20 8:31 ` dataCobra
2022-08-20 8:34 ` [PR REVIEW] " dataCobra
2022-08-20 8:38 ` dataCobra
2022-08-20 8:38 ` dataCobra
2022-08-20 8:40 ` sgn
2022-08-20 8:41 ` sgn
2022-08-20 8:47 ` [PR PATCH] [Updated] " dataCobra
2022-08-20 8:53 ` dataCobra
2022-08-20 8:54 ` sgn
2022-08-20 8:55 ` thypon
2022-08-20 8:58 ` sgn
2022-08-20 8:59 ` dataCobra
2022-08-20 8:59 ` dataCobra
2022-08-20 8:59 ` dataCobra
2022-08-20 9:00 ` thypon
2022-08-20 9:12 ` sgn
2022-08-21 11:31 ` dataCobra
2022-08-21 11:57 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220821115739.lY7Qta-dPvrMocud9Hzlk3mgPChJ79a7rvw13DdPOys@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).