Hi Boris,

I don't think there is anything to be discussed actually.

After closer studying of the latest upstream sources of QtCurve it
appears same exact bug was submitted a while back to them. Same exact
patch was committed to the upstream, see [1]. And here is an original
bug report [2].

So guess it's either matter downstreaming the fix or waiting for 1.9.0
to be out (it is at RC1 state atm).

[1] https://cgit.kde.org/qtcurve.git/commit/?id=f164a4b69
[2] https://bugs.kde.org/show_bug.cgi?id=374046

On Fri, Jul 21, 2017 at 2:19 PM, Boris Pek <tehnic...@yandex.ru> wrote:
> Hi Sergey,
>> Patch had some malformed header (was mixing information from previous
>> maintainer patch and residue of some older description). Here is an
>> updated patch with hopefully all headers filled correct.
>> Hopefully this one will work fine :)
> Please discuss this patch with QtCurve developers in upstream BTS.
> Best regards,
> Boris

With best regards, Sergey Sharybin

pkg-kde-extras mailing list

Reply via email to