On Wed, Feb 17, 2010 at 09:51:06PM +0000, Debian Bug Tracking System wrote:
> What's mean "break mantis"? Please, be more explicit when you report a Do You read in my second message about ereg() and date()? Is it not enough "explicit"? > problem, because it will be impossible to understand or reproduce it, or Do You try to reproduce? Do run mantis with php-5.3 at all? > I will thought that your computer it's on fire because you have > installed mantis? You should thought that mantis become unusable with php-5.3 > I'm so sorry that you are tired to repeat that is a "common problem for > most of php-based packages", but you have sent "just" "one" email > refering to "mantis". mantis is not only package I have reported the same problem. This mean it is common problem. > 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 what I mean when writing that "code should be totally rewritten". All developers understand this. > If you have detected that there's a problem with the source code, don't > you think that the best way to solve it it's to contact with mantis > developers? As usual the package maintainers contact upstream. Developers are contact by users who get from them unpackaged source code. But packaged software is the part of the system, that should work. What You do when package become unusable? I know now: You close the bug report. This is best way to rid off headache -- to cut off a head. One example. The one of I mentioned packages I have reported the same problem is acidabase. They don't ask me either "particular problem" nor to "contact upstream". They understand that there are too many such "particular problems" and already working to fix them. As result they will upload the new version soon. > "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. More over, all of them are automatically (that is non-interactively) upgraded every morning. In rare cases when I encounter a light problems reported by automated monitoring system, I have temporary downgrade them. And imagine: they are working fine. Because it is debian and debian developers has it's own style of work. -- ********************************* **** Vladimir Stavrinov ****** ******* v...@inist.ru ********* ********************************* -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
