On 4/9/19 8:44 PM, Sinan Kaya wrote:
> On 4/9/2019 7:49 AM, akuster wrote:
>> After closer look, I don't the "Upstream-Status:" nor a signoff in the
>> patch being added in the bb file.
>>
>> Does this issue affect later branches ?
>
> I can fix this. The issue was introduced while backporting
On 4/9/2019 7:49 AM, akuster wrote:
After closer look, I don't the "Upstream-Status:" nor a signoff in the
patch being added in the bb file.
Does this issue affect later branches ?
I can fix this. The issue was introduced while backporting a CVE patch
from debian.
So, we are fixing a problem
On 4/9/19 5:45 AM, Sinan Kaya wrote:
> On 3/29/2019 10:42 AM, Sinan Kaya wrote:
>> musl compilation has been broken since systemd: fix CVE-2018-6954.
>> Fixing this
>> by placing #ifdef for glob definition.
>>
>> Signed-off-by: Sinan Kaya
>
> I didn't see any comments here but I wanted to let
On 4/9/19 5:45 AM, Sinan Kaya wrote:
> On 3/29/2019 10:42 AM, Sinan Kaya wrote:
>> musl compilation has been broken since systemd: fix CVE-2018-6954.
>> Fixing this
>> by placing #ifdef for glob definition.
>>
>> Signed-off-by: Sinan Kaya
>
> I didn't see any comments here but I wanted to let
On 3/29/2019 10:42 AM, Sinan Kaya wrote:
musl compilation has been broken since systemd: fix CVE-2018-6954. Fixing this
by placing #ifdef for glob definition.
Signed-off-by: Sinan Kaya
I didn't see any comments here but I wanted to let everyone know that
sumo-next branch is currently broken
