On 28.06.2016 [16:07:20 -0000], NetVicious wrote:
> Hi Nish,
>
> So we had the solution near two months in front our face.
So it seems :)
> I saw your comment on php bugtracker. There we don't have any developer
> assigned so why you don't create a patch within the tool?
I will send a PR in github (what I've done in the past). I'm not really
a PHP developer, so I'm not sure if it will be accepted as-is (and don't
know the full consequences of the change, or if more fixes are needed),
which is why I'd prefer the PHP developers figure out the fix.
> It seems you're the maintainer of the php package for the Ubuntu
> distro, so. We will have a fixed php package in some days? or we need
> to wait for the upstream fix?
I'd like to wait to see if upstream responds, at least. If not, I'll see
what I can do.
On 28.06.2016 [16:07:20 -0000], NetVicious wrote:
> Hi Nish,
>
> So we had the solution near two months in front our face.
So it seems :)
> I saw your comment on php bugtracker. There we don't have any developer
> assigned so why you don't create a patch within the tool?
I will send a PR in github (what I've done in the past). I'm not really
a PHP developer, so I'm not sure if it will be accepted as-is (and don't
know the full consequences of the change, or if more fixes are needed),
which is why I'd prefer the PHP developers figure out the fix.
> It seems you're the maintainer of the php package for the Ubuntu
> distro, so. We will have a fixed php package in some days? or we need
> to wait for the upstream fix?
I'd like to wait to see if upstream responds, at least. If not, I'll see
what I can do.