[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Security issue in groovy<2.5.0



Hello Natter,

Since it's just one commit, I suggest you put it as a patch in `debian/patches`. When someone is updating the package to 2.5.0, she can just remove it.


Felix Natter 於 2017/9/2 下午10:35 寫道:
> hello Emmanuel, 
>
> Felix Natter <fnatter@gmx.net> writes:
>>> Le 26/08/2017 à 18:14, Felix Natter a écrit :
>>>
>>>> The problem is that it may take weeks/months for groovy 2.5 to be
>>>> released, and weeks/months until it's packaged for Debian.
>>> How big is the fix for Groovy? Do you know which commits should be
>>> backported?
>> It's a single (but nontrivial) commit:
>> https://github.com/apache/groovy/commit/0305a38a0cc8f4190a1486c460ebc6f712ad1a07
>>
>> The groovy people decided not to backport to groovy 2.4.x, so I am not
>> sure whether we shall do it?
> Is there any update on this? What shall I do?
> I don't mean to be impatient, I was just not sure whether you've seen
> this.
>
> Thanks and Best Regards,


Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: