Port Zabbix2 php53 dependency

[Horst Simon]

Hi Eric,

I tested the install and the install worked fine. I think there is a bug in zabbix2 itself with php56, that it does not recognises the change in the php.ini file for php flag "always_populate_raw_post_data = -1".

Kind Regards,
Horst Simon
Mobile: +61 414 303-433
Phone: +61 3 8555-2322
Email: horst.simon at optusnet.com.au <mailto:hsimon at optusnet.com.au>
______________________________________________________________________
Please consider your environmental
responsibility before printing this email.
  
This message (including any attachments) is intended only for the use of the individual or entity
to which it is addressed and may contain information that is non-public, proprietary, privileged,
confidential, and exempt from disclosure under applicable law or may constitute as attorney work
product. If you are not the intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile
or (ii) delete this message immediately if this is an electronic communication.



> On 19 Feb 2016, at 15:24, Eric A. Borisch <eborisch at ieee.org> wrote:
> 
> I've updated zabbix2 to depend upon php56; note the dependency only really makes sure they are on the file system; your httpd.conf really determines what gets used. (You could have installed the php56 flavors independently of zabbix2 and used them.)
> 
> I've also added a +php70 variant (again, only really makes sure they are installed) if you want to play with that, too.
> 
> On Tue, Feb 16, 2016 at 4:32 PM, Horst Simon <horst.simon at optusnet.com.au <mailto:horst.simon at optusnet.com.au>> wrote:
> I think we should bump up first zabbix2 to php56, this might probably fix my issue with the failing pre-req “always_populate_raw_post_data set to on”
> even it is set in the php.ini to -1.
> 
> Maybe zabbix3 could later be build with php70 when all the modules are working with php70 and it is more common used.
> 
> Horst
> 
> > On 17 Feb 2016, at 04:19, Eric A. Borisch <eborisch at ieee.org <mailto:eborisch at ieee.org>> wrote:
> >
> > I was thinking of having a zabbix3 (conflicts with zabbix2) port, as
> > this is the type of thing (monitoring software) where people may be
> > slow to upgrade. Thoughts / concerns?
> >
> > I can certainly bump the php deps in zabbix2, and perhaps add a note
> > to remind people to update their httpd.conf  and php56/php.ini files?
> >
> > Glad to see it is being used ;)
> >
> >  - Eric
> >
> > On Tue, Feb 16, 2016 at 12:56 AM, Mike Savory <msavory1 at nzbox.com <mailto:msavory1 at nzbox.com>> wrote:
> >> Hi, the upcoming Zabbix 3 (at RC3 now) requires 5.4.0 and above, so this would be a good chance to upgrade it all.
> >> maybe we need a Zabbix-devel with Zabbix3 and php 5.6 now to lay the groundwork. Definitely check with the current maintainer (it is also openmaintainer) for their plans.
> >>
> >> Mike
> >>
> >>
> >>> On 16/02/2016, at 6:59 PM, Ryan Schmidt <ryandesign at macports.org <mailto:ryandesign at macports.org>> wrote:
> >>>
> >>>
> >>> On Feb 15, 2016, at 10:35 PM, Horst Simon wrote:
> >>>
> >>>> I noticed that port zabbix2 hat php53 dependencies are there any plans to upgrade it to php56?
> >>>
> >>> You should probably ask the maintainer directly or file a ticket in the issue tracker.
> >>>
> >>> _______________________________________________
> >>> macports-users mailing list
> >>> macports-users at lists.macosforge.org <mailto:macports-users at lists.macosforge.org>
> >>> https://lists.macosforge.org/mailman/listinfo/macports-users <https://lists.macosforge.org/mailman/listinfo/macports-users>
> >>
> >> _______________________________________________
> >> macports-users mailing list
> >> macports-users at lists.macosforge.org <mailto:macports-users at lists.macosforge.org>
> >> https://lists.macosforge.org/mailman/listinfo/macports-users <https://lists.macosforge.org/mailman/listinfo/macports-users>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20160220/9e421a67/attachment.html>