On Mon, Mar 19, 2018 at 05:04:17PM +0100, Rene Engelhard wrote:
> I am not going over the .-release procedure for this, I'd have uploaded
> to security, though, but...
>
> I don't think we should special-case our oldest,
> soon-to-be-not-supported release.
Agreed, it doesn't make sense to fix thi
Hi,
On Mon, Mar 19, 2018 at 04:43:51PM +0100, Markus Koschany wrote:
> Am 19.03.2018 um 16:23 schrieb Rene Engelhard:
> > On Sun, Mar 18, 2018 at 11:39:57AM +0530, Abhijith PA wrote:
> >> I prepared LTS security update for graphite2[1]. Debdiff is attached.
> >> All tests ran successfully. Please
Hi,
Am 19.03.2018 um 16:23 schrieb Rene Engelhard:
> On Sun, Mar 18, 2018 at 11:39:57AM +0530, Abhijith PA wrote:
>> I prepared LTS security update for graphite2[1]. Debdiff is attached.
>> All tests ran successfully. Please review.
>
> Why would we need one given for jessie and stretch it is cle
On Sun, Mar 18, 2018 at 11:39:57AM +0530, Abhijith PA wrote:
> I prepared LTS security update for graphite2[1]. Debdiff is attached.
> All tests ran successfully. Please review.
Why would we need one given for jessie and stretch it is clearly marked
as no-DSA?
https://security-tracker.debian.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello.
I prepared LTS security update for graphite2[1]. Debdiff is attached.
All tests ran successfully. Please review.
- -abhijith
[1]
https://mentors.debian.net/debian/pool/main/g/graphite2/graphite2_1.3.10
- -1~deb7u2.dsc
-BEGIN PGP SIGNA
5 matches
Mail list logo