Your message dated Sun, 09 Feb 2014 23:12:44 +0800 with message-id <1657906.KuuVSRTtYM@brano> and subject line Re: Bug#738186: starpar hanging for dspam has caused the Debian Bug report #738186, regarding starpar hanging for dspam to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 738186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738186 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dspam Version: 3.10.1+dfsg-11 After doing a normal system startup, startpar is still listed in the process list: $ ps -eafZ|grep -i dspam system_u:system_r:dspam_t:s0 dspam 1990 1 0 10:44 ? 00:00:00 /usr/bin/dspam --daemon system_u:system_r:initrc_t:s0 root 1991 1 0 10:44 ? 00:00:00 startpar -f -- dspam I have read that this can happen if STDIN input in expected but I'm not sure how to correct this. I am using the latest Wheezy with amd64 kernel. NOTE: This was originally reported as bug 726713, but it was closed as resolved. It has not been resolved in debian stable.
--- End Message ---
--- Begin Message ---Le samedi 8 février 2014 14:27:47, vous avez écrit : > NOTE: This was originally reported as bug 726713, but it was closed as > resolved. It has not been resolved in debian stable. That's how the Debian bug tracking system works. A bug is closed if it's fixed in any version of a package found in one of the suite (which is the case here for the version in unstable and testing). With the version information the bug tracker is capable of knowing in which suite the bug is actually fixed. Look on the top right of the bug report #726713 you mentionned, you will see a dependency graph which lists version of the package affected by the bug and which suite it corresponds. So the bug tracker already knows the bug affects stable. As to the issue at stake, I don't plan to update the package in stable as I don't consider this bug important enough to do a backport of this patch. Best regards, Thomas
--- End Message ---
