On Thu, Jun 09, 2005 at 06:25:48PM -0400, Angelina Carlton wrote:
> On Wed, Jun 08, 2005 at 10:23:21PM -0400, Carl Fink wrote:
>
> > Also, no new installer this time, which eliminates what I perceive to have
> > been the biggest bottleneck.
>
> How was the installer a bottleneck? AFAIK it was rea
On Thu, 9 Jun 2005, Angelina Carlton wrote:
How was the installer a bottleneck? AFAIK it was ready to go weeks
before sarge was released. Just curious.
The only problem I had with the network installer is that it was not able
to find the sites to download the necessary files from. Then again
On Thursday 09 Jun 2005 23:25, Angelina Carlton wrote:
> How was the installer a bottleneck? AFAIK it was ready to go weeks
> before sarge was released. Just curious.
Not sure myself, but I'm guessing the installer held things back for a long
time, and while that was happening, people decided to
On Wed, Jun 08, 2005 at 10:23:21PM -0400, Carl Fink wrote:
> Also, no new installer this time, which eliminates what I perceive to have
> been the biggest bottleneck.
How was the installer a bottleneck? AFAIK it was ready to go weeks
before sarge was released. Just curious.
--
Angelina Carlton
On Wed, Jun 08, 2005 at 08:40:30PM -0400, Colin wrote:
> Matthijs wrote:
> > How long will Etch be in testing?
>
> When are the next summer olympics? ;-)
>
> But seriously, the next release shouldn't take nearly as long as sarge
> because the number of supported architectures are being reduced f
Hello *,
On Wed, Jun 08, 2005 at 08:40:30PM -0400, Colin wrote:
> Matthijs wrote:
> > When, and for what reasons, will Etch become frozen?
> >
>
> See above for when but it's the project leader that ultimately determines
> when etch is good enough to be released.
Uhm, no, it's the release manag
On Wed, Jun 08, 2005 at 08:40:30PM -0400, Colin wrote:
> But seriously, the next release shouldn't take nearly as long as sarge
> because the number of supported architectures are being reduced from eleven
> to four. They are aiming for a 12 to 18 month release cycle.
Also, no new installer this
Matthijs wrote:
> How long will Etch be in testing?
When are the next summer olympics? ;-)
But seriously, the next release shouldn't take nearly as long as sarge
because the number of supported architectures are being reduced from eleven
to four. They are aiming for a 12 to 18 month release cyc
On Mon, 06 Jun 2005 02:40:11 +0200, Steve Block <[EMAIL PROTECTED]>
wrote:
> On Sun, Jun 05, 2005 at 06:22:38PM -0400, Rick Friedman wrote:
> >For me, also being rather new to Debian, this raises another question.
> >Currently, I am running an "unstable" machine (I have unstable in
> >sources.list
According to Steve Block,
> On Sun, Jun 05, 2005 at 06:22:38PM -0400, Rick Friedman wrote:
> >For me, also being rather new to Debian, this raises another question.
> >Currently, I am running an "unstable" machine (I have unstable in
> >sources.list). I will probably keep that. I'm just curious: If
On Sun, Jun 05, 2005 at 06:22:38PM -0400, Rick Friedman wrote:
For me, also being rather new to Debian, this raises another question.
Currently, I am running an "unstable" machine (I have unstable in
sources.list). I will probably keep that. I'm just curious: If someone
has "sid" in sources.list,
On Sun, 05 Jun 2005 18:22:38 -0400
Rick Friedman <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Roberto C. Sanchez wrote:
> > I'll have to disagree on this. I think it is always better to
> > specifically name the ditribution you want to track in sources.list.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roberto C. Sanchez wrote:
> I'll have to disagree on this. I think it is always better to
> specifically name the ditribution you want to track in sources.list.
> For example, woody, sarge, sid, etc.
>
> It is much more apparent, that way, what the i
On Sun, 05 Jun 2005 the mental interface of
Roberto C. Sanchez told:
> On Sun, Jun 05, 2005 at 11:58:52AM +0200, Elimar Riesebieter wrote:
> > On Sun, 05 Jun 2005 the mental interface of
> > Robert Cates told:
> >
> > > Hi all,
> > >
> > > not being with Debian long enough to have gone through t
On Sun, Jun 05, 2005 at 11:58:52AM +0200, Elimar Riesebieter wrote:
> On Sun, 05 Jun 2005 the mental interface of
> Robert Cates told:
>
> > Hi all,
> >
> > not being with Debian long enough to have gone through this before, I'm
> > wanting
> > to know what I need to do to my current Woody inst
On Sun, 2005-06-05 at 11:09 +0100, Wulfy wrote:
> Wouldn't that cause an upgrade to Sarge?
Change your sources.list file:
For your woody installed machine use woody not stable, and for your
sarge installed machine use sarge not testing...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
Elimar Riesebieter wrote:
On Sun, 05 Jun 2005 the mental interface of
Robert Cates told:
Hi all,
not being with Debian long enough to have gone through this before, I'm wanting
to know what I need to do to my current Woody installation (ie, source.list
file) to keep using apt-get update/
On Sun, 05 Jun 2005 the mental interface of
Robert Cates told:
> Hi all,
>
> not being with Debian long enough to have gone through this before, I'm
> wanting
> to know what I need to do to my current Woody installation (ie, source.list
> file) to keep using apt-get update/upgrade.(?)
Just pu
18 matches
Mail list logo
