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

[Rafael Laboissiere]

* Sébastien Villemot <sebastien.villemot at ens.fr> [2012-04-18 10:53]:

> 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.

I thought that it was possible to ask for removal of packages in
unstable, even in the case where reverse dependencies exist, but you
are perhaps.

> 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.

In this case, it may be a good idea to ping the Release Team on the
issue.
 
Rafael