[Pkg-octave-devel] Removal of octave3.2* packages

Sébastien Villemot sebastien.villemot at ens.fr
Wed Apr 18 08:53:44 UTC 2012


Rafael Laboissiere <rafael at laboissiere.net> writes:

> * Sébastien Villemot <sebastien.villemot at ens.fr> [2012-04-18 09:43]:
>
>> Rafael Laboissiere <rafael at laboissiere.net> writes:

>> > I think that, after the removal, the severity level of #666501, #666732,
>> > Bugs #666894, #666959, #667063, #667589, and #668830 will be raised to
>> > serious.
>> 
>> It is not clear to me that we can raise the severity ourselves. My
>> understanding is that it has to be decided by the Release Team
>> (and hopefully they will).
>
> My understanding is that the Debian Policy requires a severity level of
> serious for FTBFS cases.  It does not matter who will actually raise the
> severity level.  Once the octave3.2* will be removed, the listed bug
> reports will, de facto, become release critical.

But there is a loop in your reasoning: it is impossible to request the
removal of octave3.2* as long as some packages depend on it.

So this bugs have to be closed before the removal. And having a serious
severity would help, since it would allow NMUs. And I think (but I may
be wrong) that only the Release Team can make the decision to raise the
severity.

-- 
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20120418/20787ff2/attachment.pgp>


More information about the Pkg-octave-devel mailing list