On Wed, Aug 10, 2005 at 10:44:04PM +0200, Adeodato Simó wrote:
> * Graham Wilson [Wed, 10 Aug 2005 13:59:47 -0500]:
> > All of the serious and important bugs in allegro4.1 have now been fixed.
> > Can the remove hint for this package be removed now, so that it can flow
> > back into testing?
>
* Graham Wilson [Wed, 10 Aug 2005 13:59:47 -0500]:
> All of the serious and important bugs in allegro4.1 have now been fixed.
> Can the remove hint for this package be removed now, so that it can flow
> back into testing?
A removal hint includes the version of the package to remove, so new
ve
On Tue, Aug 09, 2005 at 01:23:39AM +0200, Frank Lichtenheld wrote:
> During the Bug Squashing Party happening last weekend the release team
> also hinted a lot of packages for removal from testing. Since this is
> something that can happen to all maintainers at any point of the release
> process, w
On Wed, Aug 10, 2005 at 02:00:36PM +0200, Richard Atterer wrote:
> I just noticed that Steve has scheduled jigdo for removal, so that
> gcc-defaults/gcc-3.4 can enter testing.
Yes. Sorry for this, there's nothing wrong with jigdo itself here, this is
merely a concession to the requirement that p
Hi,
I just noticed that Steve has scheduled jigdo for removal, so that
gcc-defaults/gcc-3.4 can enter testing.
This is a bit surprising, jigdo doesn't really fit the description of
packages which are removed _without_ advance warning:
http://lists.debian.org/debian-devel-announce/2005/08/msg
5 matches
Mail list logo
