Le Tue, Jan 16, 2007 at 07:14:22AM +0100, Christian Perrier a écrit :
Actually, it's equally frustrating for all of us that we *can't*
release a new D-I despite the team plan to release RC2 a few weeks
after RC1.
We can't do this because the 2.6.18 kernel is not in testing.
Hi all,
How
On Tue, Jan 16, 2007 at 07:14:22AM +0100, Christian Perrier wrote:
Actually, it's equally frustrating for all of us that we *can't*
release a new D-I despite the team plan to release RC2 a few weeks
after RC1.
We can't do this because the 2.6.18 kernel is not in testing.
To be precise,
Mathew Binkley wrote:
I have been downloading cd images from:
http://cdimage.debian.org/cdimage/weekly-builds/powerpc/
because that's where the Debian website says to get them. None of the
images have worked for me because the installer has not been fixed.
As I have already said in
Rick Thomas wrote:
The result is that now there's a very subtle release critical bug
(#404876) and no time to fix it.
Well, the release of etch is currently delayed due to the currently 95
open release critical bugs, of which #404876 is one. I don't see any
indication that the bug's not being
Charles Plessy wrote:
How about releasing a RC1.5, then, with a 2.6.18 as similar as possible
as the one forecasted in testing ?
Etch d-i installs etch; without forcing such a release to install
unstable, it would not be possible to use the 2.6.18 kernel currently in
unstable. If we point d-i
Hi there,
Forgive me if this has been covered before, there were some messages in
the archive which I couldn't seem to open.
I am new to Linux and have installed Debian Testing on a dual boot with
OSX. I have a powerbook5,8 (one of the last ones, with the high-res screen).
The powerbook
Le Tue, Jan 16, 2007 at 10:35:52AM -0500, Joey Hess a écrit :
Charles Plessy wrote:
How about releasing a RC1.5, then, with a 2.6.18 as similar as possible
as the one forecasted in testing ?
There are of course all kinds of ways to hack around this, but all of
them are suboptimal. For
From: Christian Perrier [EMAIL PROTECTED]
and certainly can't expect to have everything run like a charm,
especially with very special hardware like the one you described in
the mail that started this thread.
It's not very special hardware. It's a bunch of IBM JS20 blades
configured as a
On Jan 16, 2007, at 8:46 PM, Mathew Binkley wrote:
As I said earlier, there shouldn't be an arbitrary line between the
installer and the packages. People aren't installing Etch the
installer or Etch the packages, they're installing Etch the
release. Test both parts simultaneously, as a
9 matches
Mail list logo
