severity 844572 important
thanks

Hello.

I'm setting the severity of this bug to "important" not because
I don't think it is not RC (as Release Policy still says that
packages must autobuild *without* failure), but because the
Release Managers are considering to decide about RC-ness
of this kind of bugs based on the probability of failure.

We don't know what kind of threshold there will be for stretch, so I
strongly recommend that you act as if this bug was serious and RC,
especially if the failures happen very often on any kind of
autobuilder which is not misconfigured.

Unfortunately this package was already autoremoved because of this bug.

This is probably not ok if we consider that other packages which FTBFS
a lot more often are still in stretch. I'm going to ask Release
Managers if it's possible to reallow this in stretch.

Thanks.

Reply via email to