Siju George wrote:
I have downloaded sarge today and am going to install it so I'll let
you know the details soon.
I happened to see something strange though!
You should probably start a new thread with your new topic. You have a
better chance of getting a response from people other than
Paul Johnson wrote:
On Wednesday June 8 2005 12:17 pm, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' & 'upgrade'
to "stable", or leave Sarge as the target?
It depends. Do you want to track Sarge or stable? Stable is always
the current release, Sarge is always Sar
Paul Johnson wrote:
On Wednesday June 8 2005 1:32 pm, Jim Hall wrote:
Sounds good. Next link in the chain, will I have to use
'dist-upgrade'?
Yes, though you might find visual representation of what you're doing
helpful. You might want to do this instead:
apt-get install aptitude
Then,
On Wed, Jun 08, 2005 at 09:08:20PM -0600, Paul E Condon wrote:
> On Wed, Jun 08, 2005 at 08:27:55PM -0400, Tom Allison wrote:
> > Yesterday on the chat rooms it was claimed that using aptitude was more
> > successful and effective than using apt-get dist-upgrade. Apparently
> > aptitude is suppo
On Wednesday June 8 2005 5:27 pm, Tom Allison wrote:
> Yesterday on the chat rooms it was claimed that using aptitude was
> more successful and effective than using apt-get dist-upgrade.
> Apparently aptitude is supposed to do the conflict resolution
> better than dist-upgrade or apt-get.
apt is
On Wednesday June 8 2005 1:32 pm, Jim Hall wrote:
> Sounds good. Next link in the chain, will I have to use
> 'dist-upgrade'?
Yes, though you might find visual representation of what you're doing
helpful. You might want to do this instead:
apt-get install aptitude
Then, once that is installed,
On Wednesday June 8 2005 12:17 pm, Jim Hall wrote:
> Now that Sarge is released, do I need to point 'update' & 'upgrade'
> to "stable", or leave Sarge as the target?
It depends. Do you want to track Sarge or stable? Stable is always
the current release, Sarge is always Sarge.
--
Paul Johnson
On Wed, Jun 08, 2005 at 09:08:20PM -0600, Paul E Condon wrote:
>
> I strongly suspect that this is pure BS. I have never had a problem with
> conflict resolution with either flavors of dist-upgrade, namely
> apt-get dist-upgrade and
> aptitude dist-upgrage. Both work for me.
> Furthermore, the cod
On Wed, Jun 08, 2005 at 08:27:55PM -0400, Tom Allison wrote:
> Jim Hall wrote:
> >Lee Braiden wrote:
> >
> >>On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
> >>
> >>>Now that Sarge is released, do I need to point 'update' & 'upgrade' to
> >>>"stable", or leave Sarge as the target?
> >>
> >>
> >>
>
Jim Hall wrote:
Lee Braiden wrote:
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' & 'upgrade' to
"stable", or leave Sarge as the target?
No, you can do nothing, if you like.
Pointing it to "stable" would only do something once the
On Wed, Jun 08, 2005 at 03:32:31PM -0500, Jim Hall wrote:
> Sounds good. Next link in the chain, will I have to use 'dist-upgrade'?
> Those times I've used it have usually had bad results. If I can continue
> to manually repair what's 'held back', that seems safer to me.
A dist-upgrade should be
On Wed, Jun 08, 2005 at 08:45:45PM +0100, Lee Braiden wrote:
> On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
> > Now that Sarge is released, do I need to point 'update' & 'upgrade' to
> > "stable", or leave Sarge as the target?
>
> No, you can do nothing, if you like.
>
> Pointing it to "stable
Lee Braiden wrote:
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' & 'upgrade' to
"stable", or leave Sarge as the target?
No, you can do nothing, if you like.
Pointing it to "stable" would only do something once the next release happen
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
> Now that Sarge is released, do I need to point 'update' & 'upgrade' to
> "stable", or leave Sarge as the target?
No, you can do nothing, if you like.
Pointing it to "stable" would only do something once the next release happens.
Then, the new "s
Now that Sarge is released, do I need to point 'update' & 'upgrade' to
"stable", or leave Sarge as the target?
Jim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I forgot to mention that it also says...
"If you installed other than from a CD or DVD (for example, netboot, or
booting from floppy and installing the base system from the network),
you are not affected by this bug."
Christopher
Hal Vaughan wrote:
On Tuesday 07 June 2005 03:54 pm,
The note says
"If you have already installed a system using a 3.1r0 CD/DVD image, you
do not need to reinstall. Instead, simply edit /etc/apt/sources.list,
look for any lines mentioning security.debian.org, change "testing" to
"stable", and remove "# " from the start of the line."
So I
On Tuesday 07 June 2005 03:54 pm, Christopher Smiga wrote:
> I saw this on a mirror site earlier today.
>
> -
>
>
> Note: 3.1r0 CD image problem
>
> A bug has been discovered in the 3.1r0 CD/DVD images: new installs from
> these images will have a commented-out entry in /etc/apt/sources.l
I saw this on a mirror site earlier today.
-
Note: 3.1r0 CD image problem
A bug has been discovered in the 3.1r0 CD/DVD images: new installs from
these images will have a commented-out entry in /etc/apt/sources.list
for "http://security.debian.org/ testing/updates" rather than an active
e
On Mon, 2005-06-06 at 20:27 -0600, Paul E Condon wrote:
> I took the occasion of this release to review my sources.list and preferences.
> In the process I did some experiments and found a puzzle that I hope
> someone will explain.
>
> With sarge in my sources.list I have nothing to download beca
I took the occasion of this release to review my sources.list and preferences.
In the process I did some experiments and found a puzzle that I hope
someone will explain.
With sarge in my sources.list I have nothing to download because I have been
tracking sarge for almost a year. But I set source
On Mon, Jun 06, 2005 at 07:24:30PM -0400, Tom Allison wrote:
> Clive Menzies wrote:
> >A message to all those responsible for the sarge release:
> >http://www.debian.org/releases/stable/credits
> >Many thanks for all your brilliant work accomplished with generosity and
&g
On Mon, Jun 06, 2005 at 11:36:37PM +0100, Clive Menzies wrote:
> Hi
>
> A message to all those responsible for the sarge release:
>
> http://www.debian.org/releases/stable/credits
>
> Many thanks for all your brilliant work accomplished with generosity and
> patience.
&
Tom Allison wrote:
>
> Should I be concerned that my link to
>
> http://non-us.debian.org testing/non-US/non-free
> and other 'non-us.debian.org' URLs?
>
> It seems that a lot of things are not responding. Is this the result of
> 38000 users all trying to access the exact same server?
>
>
T
Clive Menzies wrote:
Hi
A message to all those responsible for the sarge release:
http://www.debian.org/releases/stable/credits
Many thanks for all your brilliant work accomplished with generosity and
patience.
A very grateful user ;)
Clive
Should I be concerned that my link to
http
Hi
A message to all those responsible for the sarge release:
http://www.debian.org/releases/stable/credits
Many thanks for all your brilliant work accomplished with generosity and
patience.
A very grateful user ;)
Clive
--
www.clivemenzies.co.uk ...
...strategies for business
--
To
I think it may just be a problem of adding the right PCI ID to sarge. I had
this problem with a broadcom chip in a laptop, and raised a bug against
debian-installer and they added the ID. b44 is certainly available as a
module, it just need to be recognised as the right module for this ID. So
r
Michael Patrick <[EMAIL PROTECTED]> writes:
> you have probably recieved this before but i would really appreciate
> it if you added support for the broadcom 440x nic in the upcoming
> release of sarge.
You need to modprobe kernel module b44 which is available as a module
in the default sarge ker
Michael Patrick wrote:
you have probably recieved this before but i would really appreciate
it if you added support for the broadcom 440x nic in the upcoming
release of sarge.
That's a kernel issue. Debian developers have no control
over the kernel.
--
To UNSUBSCRIBE, email to [EMAIL PROTE
you have probably recieved this before but i would really appreciate
it if you added support for the broadcom 440x nic in the upcoming
release of sarge.
On Wed, Sep 22, 2004 at 03:21:00PM -0500, John Fleming wrote:
> > because the final Sarge "will be ready when it will be ready", and it will
> be
> > _good_ and _stable_
> > That's what's really important, no?
>
> Really naive question - Could recently-released SpamAssassin 3.0 still make
> it int
On Wed, Sep 22, 2004 at 09:36:22AM -0700, Jianbo Wang wrote:
> Does anyone know the frozen, release data of sarge? Thanks!
http://lists.debian.org/debian-devel-announce/2004/09/msg5.html
--
Blast you and your estrogenical treachery!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
On Wednesday 22 September 2004 22:21, John Fleming wrote:
> > _good_ and _stable_
> > That's what's really important, no?
>
> Really naive question
It depends what "_good_" means, don't you think?
> - Could recently-released SpamAssassin 3.0 still make
> it into Sarge, or is that way too new and
> because the final Sarge "will be ready when it will be ready", and it will
be
> _good_ and _stable_
> That's what's really important, no?
Really naive question - Could recently-released SpamAssassin 3.0 still make
it into Sarge, or is that way too new and not enough time to make it into
Sarge? I
<#secure method=pgp mode=sign>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jianbo Wang <[EMAIL PROTECTED]> writes:
> Does anyone know the frozen, release data of sarge? Thanks!
If we did, it would be on Debian.org. That being said, this is open
source, it doesn't matter if it's released or no
On Wednesday 22 September 2004 18:36, Jianbo Wang wrote:
> Hi,
>
> Does anyone know the frozen, release data of sarge? Thanks!
>
> Regards!
>
> Jianbo
Hello Jianbo,
We can only make forecasts based on the following figures:
http://bugs.debian.org/release-critical/
because the final Sarge "wi
Hi,
Does anyone know the frozen, release data of sarge? Thanks!
Regards!
Jianbo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Aug 11, 2004 at 11:54:33AM -0600, Nate Duehr wrote:
> On Wed, August 11, 2004 5:58, James said:
>
> > Let's face it, most of linux's problems are a result on not being
> > about to recruit a sufficient talent pool of low level embedded
> > developers. Most of those that do convert (after a
On Wed, 11 Aug 2004 11:54:33 -0600 (MDT)
"Nate Duehr" <[EMAIL PROTECTED]> wrote:
> On Wed, August 11, 2004 5:58, James said:
>
> > Let's face it, most of linux's problems are a result on not being
> > about to recruit a sufficient talent pool of low level embedded
> > developers. Most of those th
On Wed, August 11, 2004 5:58, James said:
> Let's face it, most of linux's problems are a result on not being
> about to recruit a sufficient talent pool of low level embedded
> developers. Most of those that do convert (after a convoluted learning
> path) end up at a proprietary shop that puts li
On Tue, 10 Aug 2004 15:30:29 -0700, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Thus spake Paul Johnson ([EMAIL PROTECTED]):
>
> > James <[EMAIL PROTECTED]> writes:
> >
> > > I've googled around but can seem to find a date for the release of
> > > Sarge as stable. Anyone have any guesses?
> >
>
Thus spake Paul Johnson ([EMAIL PROTECTED]):
> James <[EMAIL PROTECTED]> writes:
>
> > I've googled around but can seem to find a date for the release of
> > Sarge as stable. Anyone have any guesses?
>
> Sometime around Christmas 2003.
So it's already nearly 8 months late...:-)
Didn't I see a
Incoming from Chris Metzler:
> On Sat, 3 Jul 2004 14:34:16 +0100 (BST)
> Thomas Adam <[EMAIL PROTECTED]> wrote:
> >
> > I'm sick to death of this "voting" business. Sarge will be released When
>
> Uh, WTF? This concerns a vote the developers were having on what
Marvelous. Excellent. Some of u
--- Chris Metzler <[EMAIL PROTECTED]> wrote:
> were voting on this topic. The developers decided they needed to
> address this issue (and I think they were right). Why does that
> trouble you so?
It doesn't trouble me, per se. I just wish all the red-tape, squabbling,
arguing would stop, so th
On Sat, 3 Jul 2004 14:34:16 +0100 (BST)
Thomas Adam <[EMAIL PROTECTED]> wrote:
>
> I'm sick to death of this "voting" business. Sarge will be released When
> It's Ready, and not a moment sooner. If that's too late for you, then
> tough. Either dist-upgrade to (the current) testing, or backport eve
On Sat, Jul 03, 2004 at 09:32:04AM -0600 or thereabouts, s. keeling wrote:
> I couldn't care less when sarge goes stable. Take your time guys. No
> rush! You did such a great job on woody, it would be a shame to give
> up on it now. :-)
Hear, Hear. I for one like the 'when it's ready" ap
Incoming from Thomas Adam:
>
> I'm sick to death of this "voting" business. Sarge will be released When
That's a very good point. For those who _just can't wait_ for sarge
to go stable, I say nuts to you! There are many options for you,
including sarge and sid, and Libranet, Xandros, Morphix, .
On Sat, Jul 03, 2004 at 02:34:16PM +0100, Thomas Adam wrote:
> I'm sick to death of this "voting" business. Sarge will be released When
> It's Ready, and not a moment sooner ...
The vote isn't about whether it's ready, it's about whether to
discard the current Sarge and start from scratch.
> ...
--- Kent Andersen <[EMAIL PROTECTED]> wrote:
> my vote if it doesnt blow up woody. (ducking) ;)
> - Original Message -
> From: "Travis Crump" <[EMAIL PROTECTED]>
> To: "Debian User List" <[EMAIL PROTECTED]>
> Sent: Saturday, July
my vote if it doesnt blow up woody. (ducking) ;)
- Original Message -
From: "Travis Crump" <[EMAIL PROTECTED]>
To: "Debian User List" <[EMAIL PROTECTED]>
Sent: Saturday, July 03, 2004 12:24 AM
Subject: sarge release vote
--
To UNSUBSCRIBE, email to [
For those that don't know, Option 2, postpone editorial changes to
Social Contract until after Sarge releases, won the vote so hopefully
Sarge's release can start to move forward again and happen in the not
too distant future. :)
signature.asc
Description: OpenPGP digital signature
On Tue, Mar 09, 2004 at 10:08:47AM +0200, Aryan Ameri wrote:
> Does anyone have any idea when Debian Sarge will be released as stable?
> I know, it will be released when it's ready, but I am setting up a
> schedule here for my tasks, and even if I could have an approximate
> date of it's release
Hi there:
Does anyone have any idea when Debian Sarge will be released as stable?
I know, it will be released when it's ready, but I am setting up a
schedule here for my tasks, and even if I could have an approximate
date of it's release, it would help alot.
Cheers
--
Aryan Ameri
--
To U
On Fri, Nov 07, 2003 at 05:10:56 -0800, Ralph Bacolod wrote:
> Hi! When is sarge release date?
When it is ready.
For more information, follow the debian-release list and
http://bugs.debian.org/release-critical/ .
This really ought to be in the FAQ.
Ray
--
"Perhaps they spent some of
Hi! When is sarge release date? Would I still be able to install to install
debian in a minimal spec system such as a pentium with only 32 mb ram?
Rafiks
__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
On Sun, Mar 30, 2003 at 10:28:07AM -0500, David Krider wrote:
> Please note that I'm NOT trolling or looking to start a flamewar. It's
> just that it took me three tries to get Woody installed. I've heard that
> Sarge will have a new installer and a new manual.
In that case, don't worry about it.
On Sunday 30 March 2003 10:28, David Krider wrote:
> Please note that I'm NOT trolling or looking to start a flamewar. It's
> just that it took me three tries to get Woody installed. I've heard that
> Sarge will have a new installer and a new manual. I'm looking to get a
> feel for the timeframe.
On Sun, 2003-03-30 at 10:28, David Krider wrote:
> I realize that there's no official release date for Sarge, but does
> anyone have a guesstimate of when it might actually be? I'm not looking
> for a day, per se, but 3 months? Six months? A year?
>
> Please note that I'm NOT trolling or looking t
I realize that there's no official release date for Sarge, but does
anyone have a guesstimate of when it might actually be? I'm not looking
for a day, per se, but 3 months? Six months? A year?
Please note that I'm NOT trolling or looking to start a flamewar. It's
just that it took me three tries t
59 matches
Mail list logo
