Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63141 > unrolled thread
| Started by | Sergio Gelato <Sergio.Gelato@astro.su.se> |
|---|---|
| First post | 2019-01-21 09:00 +0100 |
| Last post | 2019-01-21 09:00 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#895381: Severity Sergio Gelato <Sergio.Gelato@astro.su.se> - 2019-01-21 09:00 +0100
| From | Sergio Gelato <Sergio.Gelato@astro.su.se> |
|---|---|
| Date | 2019-01-21 09:00 +0100 |
| Subject | Bug#895381: Severity |
| Message-ID | <xiCEW-62O-3@gated-at.bofh.it> |
* micah anderson [2019-01-20 21:03:53 +0100]: > I'm not disputing this bug exists, I'm just trying to determine why it > is you set the severity to "Serious". As you are probably aware, this > severity indicates that this is a sever violation of Debian policy > (violates a "must" or "required" directive), or in the package > maintainer's opinion, makes the package unsuitable for release. Oh. In the package maintainer's opinion. I had missed that part; my apologies. No, I don't claim a policy violation on this one and of course I'll defer to the package maintainer's assessment. I do find the bug scary, though, due to the possibility of silent corruption, and have been running a privately patched version of the package for that reason.
Back to top | Article view | linux.debian.kernel
csiph-web