Olivier Berger wrote:
> On Fri, Sep 03, 2010 at 05:26:32PM +0800, Thomas Goirand wrote:
>> libnusoap-php produces the following warning under Squeeze, due
>> to the changes in PHP 5.3.x:
>>
>> PHP Deprecated: Assigning the return value of new by reference is
>> deprecated in /usr/share/php/nusoap/nusoap.php on line 7384
>>
>
> I have tried and reproduce the problem, and can't seem to find a
> way to activate the warnings when run with default Debian php.ini
> settings.
> It's apparently not a problem most users will be facing AFAICT.
> Maybe another app's particular environment sets more strict
> error reporting and is to be changed for stable deployment ?
>
> Can you try and explain in which conditions the problem occurs ?
>
> What's the content of ini_get('error_reporting'); in your script
I run my cron job with error_reporting(E_ALL); as I don't like hiding
issues, but care about fixing them. It's my (developer) choice to do so,
and I don't want to change it.
> OK, but is this a use case that is standard for most users, or
> your own problem ?
> Remember that we have to take into account all users of the
> package, and
> some strong annoyances for some are not always applying to most. That
> said... it may be possible to execute your job with less talkative PHP
> options, i.e. something like error_reporting = E_ALL & ~E_DEPRECATED
> for the particular jobs that annoys you.
>
> Again, it's a warning, and I'm not sure it's safe to keep deprecation
> warnings activated by default in stable releases anyway, so
> your warning
> may as well go away.
I am not going to continue fighting with you about whether or not this
issue is serious. Please trust me, it's annoying me, and I don't want to
have to change the error_reporting. This is a warning about a deprecated
function of PHP, and should be fixed. Please understand that some
package that I maintain *are affected* and would produce a mail to root
each 10 minutes. The issue *is not* in these packages, but in yours.
So I will make it simple, because we have no time to spare before
Squeeze is released. Either you tell me that you are willing to fix it,
I can sponsor an upload of the corrected package and ask for a freeze
exception, either you refuse it and I'll do an NMU to fix this trivial
one character fix. I have no problems either way, but I got to know.
More over, I insist that the release manager *will* accept such a
trivial fix.
Thanks to let me know your intentions so that I know what to do.
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
