On 01/07/2016 07:52 PM, Marc Schiffbauer wrote:
>>
>> 3. I could try to hack some magic into eselect-php to detect whether or
>>not you have -DPHP5 set. Something simple, like grepping /etc/conf.d
>>/apache2 for "PHP5". In that case we could omit a notice.
>>This one simultaneously make
* Michael Orlitzky schrieb am 06.01.16 um 20:53 Uhr:
> On 01/06/2016 02:36 PM, Sebastian Pipping wrote:
> > On 05.01.2016 20:35, Michael Orlitzky wrote:
> >> I just pushed a new revision with this fix. In eselect-php-0.8.2-r1,
> >> we ship both the new 70_mod_php.conf and the old 70_mod_php5.conf.
On 01/06/2016 02:36 PM, Sebastian Pipping wrote:
> On 05.01.2016 20:35, Michael Orlitzky wrote:
>> I just pushed a new revision with this fix. In eselect-php-0.8.2-r1,
>> we ship both the new 70_mod_php.conf and the old 70_mod_php5.conf. The
>> latter comes with a big warning at the top of it, stat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.01.2016 11:45, Lars Wendler wrote:
> Hi Sebastian,
>
> to be honest I was very upset when I first stumbled upon this
> problem. And yes I only found about it when my apache webserver
> started to deliver php source code instead of the real sites
On 05.01.2016 20:35, Michael Orlitzky wrote:
> I just pushed a new revision with this fix. In eselect-php-0.8.2-r1,
> we ship both the new 70_mod_php.conf and the old 70_mod_php5.conf. The
> latter comes with a big warning at the top of it, stating that it is for
> backwards compatibility only.
Co
On 01/04/2016 02:27 PM, Michael Orlitzky wrote:
>
> I may be able to fix that by simply including the old 70_mod_php5.conf
> for backwards compatibility.
>
I just pushed a new revision with this fix. In eselect-php-0.8.2-r1,
we ship both the new 70_mod_php.conf and the old 70_mod_php5.conf. The
On 01/04/2016 12:49 PM, Rich Freeman wrote:
>
> My understanding (which could be wrong) is that this update will break
> things even if the user never runs eselect php afterwards. I can't
> tell you the last time I touched the php eselect module, because major
> updates to php are rare.
>
I was
On Mon, Jan 4, 2016 at 12:21 PM, Brian Evans wrote:
>
> On 1/4/2016 11:43 AM, Michael Orlitzky wrote:
>> On 01/04/2016 11:11 AM, Peter Stuge wrote:
>>>
>>> So pkg_postinst for >=eselect-php-0.8.1 should say something,
>>> but ideally also the invocation - but I don't know if eselect-php
>>> is als
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/4/2016 11:43 AM, Michael Orlitzky wrote:
> On 01/04/2016 11:11 AM, Peter Stuge wrote:
>>
>> So pkg_postinst for >=eselect-php-0.8.1 should say something,
>> but ideally also the invocation - but I don't know if eselect-php
>> is also code or only
On 01/04/2016 12:11 AM, Jeroen Roovers wrote:
>
>> Without updating APACHE2_OPTS, websites could end up serving
>> PHP code (include configuration files with passwords)
>> unprocessed to website visitors!
>
> That would mean there is an additional (local) security problem.
>
All PHP application
On 01/04/2016 11:11 AM, Peter Stuge wrote:
>
> So pkg_postinst for >=eselect-php-0.8.1 should say something, but
> ideally also the invocation - but I don't know if eselect-php is also
> code or only data managed by eselect?
The pkg_postinst is already there. The eselect-php routines are bash
code
Michael Orlitzky wrote:
> >> If anyone has a concrete idea that works better, it's not too late to
> >> change it.
> >
> > Add code to init script and service file to check the config before
> > starting the program, and react if PHP5 is still set.
>
> Which init script?
For Apache.
> It's only
On 01/04/2016 10:42 AM, Peter Stuge wrote:
> Michael Orlitzky wrote:
>> If anyone has a concrete idea that works better, it's not too late to
>> change it.
>
> Add code to init script and service file to check the config before
> starting the program, and react if PHP5 is still set.
>
Which init
Michael Orlitzky wrote:
> If anyone has a concrete idea that works better, it's not too late to
> change it.
Add code to init script and service file to check the config before
starting the program, and react if PHP5 is still set.
//Peter
On 01/04/2016 08:40 AM, Michał Górny wrote:
>
> Therefore, I think you should really work on some kind of backwards
> compatibility for people using '-D PHP5' that would prevent those kind
> of issues at least for some migration period. With big fat warnings for
> people who run it.
>
I wasn't a
On Mon, 4 Jan 2016 01:26:28 +0100
Sebastian Pipping wrote:
> Better late then never. Posting 72 hours from now the earliest as
> advised by GLEP 42. Feedback welcome as usual.
afaics this only affects users using the mod_php variant of PHP and not
any fcgid or fpm solution. I think this should
On Mon, 4 Jan 2016 11:45:37 +0100
Lars Wendler wrote:
> to be honest I was very upset when I first stumbled upon this problem.
> And yes I only found about it when my apache webserver started to
> deliver php source code instead of the real sites.
> Doing such a change without getting in contact
Hi Sebastian,
to be honest I was very upset when I first stumbled upon this problem.
And yes I only found about it when my apache webserver started to
deliver php source code instead of the real sites.
Doing such a change without getting in contact with me as apache
maintainer before the change wa
On Mon, 4 Jan 2016 01:26:28 +0100
Sebastian Pipping wrote:
> Hi!
>
>
> Better late then never. Posting 72 hours from now the earliest as
> advised by GLEP 42. Feedback welcome as usual.
>
>
> ===
> Title: Apache "-D PHP5" needs update
19 matches
Mail list logo
