On 2013/08/13 21:19, Christian Weisgerber wrote:
> Here are the build errors on amd64 from a ~24-hour old ports tree,
> BEFORE the 64-time_t switchover:
> 
> == Compile errors related to PHP
> 
> archivers/pecl-rar              php
> mail/pecl-mailparse             php
> www/pecl-proctitle              php
> www/pecl-uploadprogress         php

I've committed updates for these which fix the problems.

> graphics/pecl-imagick           php

Latest actual release is still broken, there is a release candidate though.

> www/pecl-phar                   php

Broken, no new release.

> multimedia/ffmpeg-php           php

can someone interested look at this please?
 http://sourceforge.net/p/ffmpeg-php/bugs/52/

> www/pecl-swish                  php

there is a newer version, diff below, but almost all the tests fail
(in a totally different way to how they fail with 5.3). anyone actually
using this, please help/test!

Index: Makefile
===================================================================
RCS file: /cvs/ports/www/pecl-swish/Makefile,v
retrieving revision 1.13
diff -u -p -r1.13 Makefile
--- Makefile    12 Aug 2013 04:11:21 -0000      1.13
+++ Makefile    14 Aug 2013 11:51:38 -0000
@@ -2,8 +2,7 @@
 
 COMMENT =      PHP interface to swish-e
 
-DISTNAME =     swish-0.4.0
-REVISION =     4
+DISTNAME =     swish-0.5.0
 
 # PHP
 PERMIT_PACKAGE_CDROM =         Yes
Index: distinfo
===================================================================
RCS file: /cvs/ports/www/pecl-swish/distinfo,v
retrieving revision 1.2
diff -u -p -r1.2 distinfo
--- distinfo    17 Nov 2011 12:44:21 -0000      1.2
+++ distinfo    14 Aug 2013 11:51:38 -0000
@@ -1,5 +1,2 @@
-MD5 (swish-0.4.0.tgz) = KJbFegiPaQ+eWbTESfC4DQ==
-RMD160 (swish-0.4.0.tgz) = P/aKvBkNDbl/bFLx7pcYJ1IV34M=
-SHA1 (swish-0.4.0.tgz) = jc8qWyrZieFjNYf72xR86jXM2/A=
-SHA256 (swish-0.4.0.tgz) = ZhhTwLWkHagcjDxi3BMoZEmXVqXiSMltSpIXra+JIvc=
-SIZE (swish-0.4.0.tgz) = 71427
+SHA256 (swish-0.5.0.tgz) = wDI8j9H0vKoAwEhsHVnoPj9Rmg+URlm3ct+xVaj0Ld0=
+SIZE (swish-0.5.0.tgz) = 71966

Reply via email to