> Am 31.08.2016 um 15:03 schrieb Torsten Zuehlsdorff
> :
>
> On 26.08.2016 21:38, Kurt Jaeger wrote:
>> Hi!
>>
About resetting the maintainer, I'll ask around.
>>
>>> The rules are pretty clear:
>>>
On 26.08.2016 21:38, Kurt Jaeger wrote:
Hi!
About resetting the maintainer, I'll ask around.
The rules are pretty clear:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer.html
It's more about: Who's willing to do it ?
As talked in private: i could/will do, since
Hi!
> I'm testbuilding 5.6.25 right now.
A patch is at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212183
--
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing list
Hi!
> > About resetting the maintainer, I'll ask around.
> The rules are pretty clear:
> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-maintainer.html
It's more about: Who's willing to do it ?
--
p...@opsec.eu+49 171 3101372 4 years to go !
On Fri, Aug 26, 2016 at 09:08:44PM +0200, Kurt Jaeger wrote:
> Hi!
>
> > It's been a week since PHP 5.6.25 was released and it still has not hit the
> > ports system. This has been an ongoing problem for quite sometime now.
>
> tz@ has ambitions with php, as he's maintaining php70. Maybe
> he
Hi Kurt,
> On 26 Aug 2016, at 9:08 PM, Kurt Jaeger wrote:
>
> I'm testbuilding 5.6.25 right now.
Please please make sure to reset all the php56-* module's
port revisions to zero if you do commit. This was missed
in the php70 bump.
Cheers,
Franco
Hi!
> It's been a week since PHP 5.6.25 was released and it still has not hit the
> ports system. This has been an ongoing problem for quite sometime now.
tz@ has ambitions with php, as he's maintaining php70. Maybe
he finds the time...
feld@ also worked on some updates.
I'm testbuilding
Hey guys,
It's been a week since PHP 5.6.25 was released and it still has not hit the
ports system. This has been an ongoing problem for quite sometime now.
According to freshports commit log, the maintainer for PHP 5.6 hasn't made
a commit since November 2015.
What exactly is the status of