fixed 595346 0.9.5-1
thanks

Le samedi 04 septembre 2010 à 01:08 +0800, Thomas Goirand a écrit :
> Olivier Berger wrote:
> > 
> > This is just a warning... and how annoying it could be, doesn't mention
> > that the deprecation may happen during squeeze lifetime, so not so much
> > a problem IMHO.
> 
> Sorry, but I do not agree with the above. A simple warning can have
> grave consequences. For example, we include nusoap.php in a cron job
> that starts every 10 minutes. With this issue, I was spammed every 10
> minutes by this cron job because of this warning.

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.

> 
> Another example of bad issue with a warning would be a program that
> would generate a document like an XML. If there was a warning, then this
> would render the the XML document totally wrong.
> 
> There are many other examples...
> 

There are plenty of possibilities, theorically... OK, but let's just
discuss the ones that are realistic in normal use of Debian packages,
first ;)

> >>  Please consider either packaging the latest version from
> >> upstream (if it corrects the issue), or patching the currently
> >> existing package.
> >>
> > 
> > Have you seen http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577441#30
> > and tested anything on the version in experimental (which may be
> > uploaded to unstable I guess, now) ?
> 
> I didn't see it, no. A quick search on the archive shows that Squeeze
> and SID have the same old version:
> 
> http://packages.debian.org/search?keywords=nusoap&searchon=names&suite=all&section=all
> 

Yes indeed, but experimental is your friend here (until my sponsor
uploads it to unstable for me).

> > I'm basically preferring to have deprecation warnings instead of soap
> > breakages, until apps have been tested more.
> 
> I basically want something that works, without warnings, especially when
> the fix are quite simple. If you want to keep the old version (which I
> think is a good idea), you can patch it to fix the issues, this isn't so
> much of a problem. 

Sure, that's possible. But I'm afraid it's just a bit too much late for
that one, given the rules of the freeze now :-( too bad it wasn't
spotted weeks earlier.

> Please have a look at the extremely easy fix that we
> are talking about, and that I've attached to this email: we are talking
> about remove exactly *one character* in the source code... :)
> 

Thanks for having investigated this anyway.

Now, I think we should focus on testing 0.9.5 instead (which doesn't
have this issue, btw).

Best regards,
-- 
Olivier BERGER <olivier.ber...@it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to