Bug#607525: RM: minitube/1.1-1
On Sun, 2010-12-19 at 13:19 +0000, Jonathan Wiltshire wrote:
> Please remove minitube from testing pending a new upstream. The maintainer
> approves and will seek to get it into volatile instead, because of the
> unstable API - see #606670.
Apologies for not spotting the issue earlier, but those two requests are
incompatible. Starting with the squeeze release, what is currently the
separate volatile archive will be replaced with a new "${suite}-updates"
suite hosted on the standard ftp mirrors (see
20101005202925.GU4622@halon.org.uk , d-d-a, 2010-10-05). This will
expose a subset of the packages in proposed-updates so that users can
still choose to easily updates packages such as clamav or tzdata without
pulling in the rest of p-u and simplifies the process of ensuring that
any such updates make it in to stable proper.
As a side-effect, it will not be possible to include packages which are
not part of the corresponding stable release. If we remove minitube
from Squeeze now, further updates once Squeeze is stable would then need
to be made via backports, rather than volatile.
I have no particular preference which route is taken, but thought it was
worth spelling out the consequences.
Regards,
Adam
Reply to: