> > I set severity to grave as debian documentation sais i should mark > > as grave when the package in question is unusable or mostly so. > > Does the package work *not_at_all* or does it break other packages? Or > is it just one functionality which is not working properly? > > If it's just the latter, then this bug report should not be marked as > "grave". Tagging a bug with severity "grave" has ramifications which > can include the removal of the package from the archives and I'm not > sure if that's what you intended. > > Please do not file a bug report with severity of "grave" until you > fully understand what the ramifications are and what the purpose of > tagging it as "grave" is. Tagging it as "normal" is enough for 99% of > the cases unless this issue is actually serious, e.g. a vulnerability > with a working exploit. > > Just tagging the bug as "grave" does not automatically make people fix > the issue faster. The severity is readjusted by the maintainers anyway > when doing triaging.
well. Actually I just read from https://www.debian.org/Bugs/Developer#severities grave makes the package in question unusable or mostly so,... and I think that caja-sendto is probably most of the time used to send files by mail, and since that feature does not work, i thought grave would be correct. sorry if I chose the wrong severity. erik
