From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: schroot: update to 1.6.10-12+deb11u1. CVE-2022-2787
Date: Sat, 20 Aug 2022 11:12:18 +0200 [thread overview]
Message-ID: <20220820091218.cLP9PrJgEhi_AznwWTroz1Fyf1tAP-CsmWnrFRrr5rc@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: 379 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/38779#issuecomment-1221264000
Comment:
> We could upgrade to match Debian unstable. But I assumed this would conflict with the "Stable rolling release" philosophy.
We aren't Debian, we want both stable and rolling release. But, our stable is different from Debian's stable.
next prev parent reply other threads:[~2022-08-20 9:12 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 [this message]
2022-08-21 11:31 ` dataCobra
2022-08-21 11:57 ` [PR PATCH] [Merged]: " sgn
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=20220820091218.cLP9PrJgEhi_AznwWTroz1Fyf1tAP-CsmWnrFRrr5rc@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).