Rolf Leggewie (22/01/2012):
> Then grave is the wrong severity, it should be critical. Are you now
> saying this bug is critical?
There might have been no other packages co-upgraded, so grave as “the
package is unusable” is enough.
> My frustration is about people who don't really know what's g
Thank you for your comment, Cyril. I'm not convinced but willing to
listen. I hope you are, too.
On 22.01.2012 18:30, Cyril Brulebois wrote:
> Erm. Breaking the dpkg configuration phase means you can break alot of
> other packages. On mine that was “just” glib*, gtk*, so the whole X
> session wa
Rolf Leggewie (22/01/2012):
> The current package is installable just fine. While no doubt
> resulting in a bit of an ugly state, the update from one particular
> unstable package to another breaks but also works at least to the
> point of not leaving the package unusable and according to Paul th
I've now come to the conclusion that this is in fact actually not an RC
bug, none of the criteria listed on
http://www.debian.org/Bugs/Developer#severities for severity grave
apply. The original setting of "important" turns out to have been spot on.
The current package is installable just fine.
4 matches
Mail list logo
