reopen 569686
tags 569686 + upstream
thanks

Hi.

May I try and remind you that Debian maintainers are volunteers and you
can't just be angry or rude, or vague in your reports, and expect
something to improve... also providing a detailed report is the best way
to help (even if it just says : same as #1234 on package whatever if it
looks the same as another report).

Btw, Mantis is also developped by volunteers... so it's up to you to be
constructive... and so far, it was not really that much obvious from you
mails.

Le jeudi 18 février 2010 à 11:48 +0300, Vladimir Stavrinov a écrit :

> mantis is not only package I have reported the same problem. This mean
> it is common problem.
> 

Then you may have been nice with the maintainer by providing bug numbers
maybe ?

> > Sorry, but if you are reporting a bug on a "particular" package, it have
> > A LOT OF SENSE to discuss the "particular" case.
> 
> The one "particular" problem is that all POSIX Regex functions should be
> replaced with PCRE. But the problem is not limited by this particular
> task. 
> 
> Here is some php based project that I am working on. What I am doing?
> I have set 
> 
> error_reporting  =  E_ALL
> 
> and look into error log. I take one string and rewrite code to rid off
> this error (or warning, or else) message. Then test again. I will
> repeat this cycle until error log become empty. This is necessary hard
> work to move from php-5.2 to php-5.3.

That is surely much more helpful now, and maybe you'd better provided
this on first time.

>  You close the bug report. This is
> best way to rid off headache -- to cut off a head.
> 

Maybe she should have not closed it and instead added a morehelp tag.

> One example. The one of I mentioned packages I have reported the same
> problem is acidabase. 

How is one supposed to know... maintainers don't subscribe to all PHP
app bug notifications, you know ;)

> > "production service", and you're running and unstable version?
> 
> Yes! I am administering the farm of many production servers for about a
> ten years. All this time all of them are running unstable debian because
> testing and stable are too old.

That's your choice, but don't blame others on your own decisions.

Anyway, I hope that now that the problem has been pushed upstream we'll
have good news when 1.2.0 is released... so far, Mantis in Debian is
probably going to have problems in unstable if php5.3 is the problem
there.

Best regards,   
-- 
Olivier BERGER <olivier.ber...@it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
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