Hi Helmut,
Helmut Grohne wrote:
> On Wed, Jun 16, 2021 at 03:28:44PM +0200, Axel Beckert wrote:
> > I noticed that you didn't specify a severity — which implies just a
> > "normal" severity. So I assume this is nothing which needs to go in
> > for bullseye, right?
>
> This is all correct. I tend to drop the severity as unnecessary line
> noise.
Ok. I tend to only remove it if I don't care about the actual
severity, i.e. as a hint to the maintainer to decide on the severity
on its own and that I won't argue on severity changes.
> In general, when I file bugs at non-rc severity during (any kind
> of) freeze, I do point out when I think it should be fixed for a
> particular release. When there is any kind of urgency, I say so
> explicitly in the submission.
That's definitely a good practice.
I mostly asked because FTBFS is usually of RC-severity and from my
point of view, FTCBFS is not that far away from FTBFS.
> The question of whether normal bugs should be fixed during freeze
JFTR: I didn't ask that. I more or less asked if you forgot to set a
(RC-) severity, because it looked like the bug report was not written
with reportbug (or M-x debian-bug) as the typical reportbug footer was
missing as well. And it happens not seldom that the one or other
pseudo header gets forgotten when bug reports are written manually in
a mail client. BTDT. (Didn't check the mail headers back then. Did so
now and to my surprise the bug report was actually written with
reportbug. Oh well. :-)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
