On Thu, Jul 28, 2016 at 02:27:36PM +0200, Miroslav Lachman wrote: > Baptiste Daroussin wrote on 07/28/2016 13:19: > > On Thu, Jul 28, 2016 at 12:38:09PM +0200, Miroslav Lachman wrote: > > > > > > Baptiste Daroussin wrote on 07/28/2016 12:15: > > > > On Tue, Jul 26, 2016 at 07:19:51PM +0200, Miroslav Lachman wrote: > > > > > Can this ports expiration be modified? Upstream released 5.5.38 on > > > > > 21st July > > > > > 2016 so I don't think it will not need to be removed so fast. > > > > > > > > > As far as I understand, they made that release to mark the end of the > > > > support: > > > > http://php.net/eol.php > > > > > > > > The end of the support was July 21st > > > 5.5.38 fixes 15 bugs so i think it was regular release. > > > What i propose is to extend this expiration date to two or three months. > > > It > > > is wildly used port and will remains in quaterly branch too. I don't think > > > we need to maintain it longer as was with 5.3. > > > > Make sense > > Filed PR 211420 I have already committed :) sorry I haven't replied here > > > > While I am here, the pkg message have some weird escaping of spaces: > > > > > > ----------- > > > This port is deprecated; you may wish to reconsider installing it: > > > > > > EOL\ upstream\ since\ 10\ Jul\ 2016. > > > > > > It is scheduled to be removed on or after 2016-08-20. > > > ----------- > > > > > > Is it intended or is it a bug in ports / pkg? > > > > It is a bug in ports > > Is it known bug or should I open PR for it?
This one it not a known bug, and should be reported as I have no time to fix it yet. So yes a PR would be nice thanks, Best regards, Bapt
signature.asc
Description: PGP signature
