On 22/05/2025 12:00, Colin Watson wrote:
On Thu, May 22, 2025 at 11:43:56AM +0100, Ahmad Khalifa wrote:
Do you really enjoy waiting 30 min for a bug to be created to get a
bug number?
I agree there are a number of problems with debbugs, but I don't think
it's helpful to exaggerate quite so wildly. The cron job that processes
incoming messages runs every three minutes, and it doesn't in practice
take long enough to end up with a backlog, so 30 minutes isn't plausible
unless there's some kind of temporary outage.
I've experimentally changed it to run every minute instead, since I
couldn't think of a reason not to.
Thanks for doing that. Much less confusing for people like me who don't
use it every day.
And I agree, some replies arrive 3 minutes later. But 3 minutes is still
not normal, I'm afraid.
Just in cause you're curious why I mentioned 30mins, here are a couple
of examples:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105796;msg=36
Sent 20:01, acknowledgement Received 20:33
I can see the last Received is 20:31 and the first one is 20:01 - so
perhaps I'm complaining about the wrong thing.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105128;msg=7
Sent 18:15, acknowledgement Received 18:33
Again the email headers start from 18:15 and take until 18:31 to arrive.
Those 15/30 blocks look a lot like email queue retries to me, but let's
not go anywhere near investigating email headers and queues.
If I just had a button to click on, I wouldn't be writing this email :)
--
Regards,
Ahmad
