Re: Bug report lost with reportbug
In article <[🔎] 55F19F12C7F1B24BB429BA7F6305353E2D105F@exchange.polarcom.intern>
arve.seljebu@polarcom.no writes:
>This is a multi-part message in MIME format.
Please don't do that. It makes your messages bigger and harder to read.
>I tried to report some bugs for the package freeradius-dialupadmin with
>reportbug, but I'm unsure if my bug report has been sent. Is it supposed
>to show up on bugs.debian.org with once, or does it need to be confirmed
>by someone?=20
>
>=20
>
>The manual for reportbug says "...and makes a carbon copy of the report
>for you as well". In other words; if I've didn't receive this carbon
>copy, the bug report has never been sent?
Not receiving the copy means either reportbug was misconfigured or the
mail was not sent (yet). (It may be stuck in your outgoing mail queue.)
Bugs are normally processesed within an hour, however it can take
longer when large batches of spam are being proccessed. A
confermation is sent with the bug number after the bug has been
created.
Check http://bugs.debian.org/ to see if the bug has been created.
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
Reply to: