-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
> Hi!
>
>
> Better late then never. Posting 72 hours from now the earliest as
> advised by GLEP 42. Feedback welcome as usual.
Do you have any timeline in place for the change happening in tree (
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, Jan 4, 2016 at 3:41 AM, Kristian Fiskerstrand wrote:
>
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
>>
>>
>> Better late then never. Posting 72 hours from now the earliest as
>> advised by GLEP 42. Feedback welcome as usual.
>
> Do you have any timeline in place for the cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/04/2016 09:41 AM, Kristian Fiskerstrand wrote:
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
>
> Such a change should really be avoided if possible. Would it be
> possible to have a conditional approach where either one can be
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/04/2016 02:30 PM, Kristian Fiskerstrand wrote:
> On 01/04/2016 09:41 AM, Kristian Fiskerstrand wrote:
>> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>>> Hi!
>
>
>
>
>> Such a change should really be avoided if possible. Would it be
>>
Kristian Fiskerstrand wrote:
> Maybe I'm thinking things too difficult, why not just define both -D
> PHP and -D PHP5 in the transition period and suggest this config for
> any change?
Because it mostly just defers the problem.
If the desire is to move away from PHP5 then I would suggest to force
On Mon, Jan 4, 2016 at 9:20 AM, Kristian Fiskerstrand wrote:
>
> And while at it, in additional to news item, this should likely follow
> a few version upgrades as elog messages before actually being
> implemented anywhere
>
I don't want to be too prescriptive with the solutions. However,
clearl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/4/2016 3:41 AM, Kristian Fiskerstrand wrote:
> On 01/04/2016 01:26 AM, Sebastian Pipping wrote:
>> Hi!
>
>
>> Better late then never. Posting 72 hours from now the earliest
>> as advised by GLEP 42. Feedback welcome as usual.
>
> Do you have
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 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
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 Sat, 02 Jan 2016 16:54:31 +0100
Gilles Dartiguelongue wrote:
> Hello all,
>
> while working on bug #518422, I found out that while eclass calls the
> relevant cache updates it has no idea whether or not it is called in a
> multilib context or not.
Hmm... what's the problem here ?
What you se
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.
>
> Which init script?
For Apache.
> It's only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/01/16 10:54 AM, Gilles Dartiguelongue wrote:
> Hello all,
>
> while working on bug #518422, I found out that while eclass calls
> the relevant cache updates it has no idea whether or not it is
> called in a multilib context or not.
>
> Imho,
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
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
-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 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
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
I have had ClusterHQ's partial stable ABI in Gentoo's packaging since
December (which helped to shake out bugs) and have just done another
update of it with various bug fixes, including many from HEAD.
Some might notice that merging a pull request that isn't fully reviewed
is a fairly big departur
22 matches
Mail list logo
