Re: Debian woody or sarge?
Frank Gevaerts wrote: > Bob Proulx wrote: > > Stable is not up to handling gforge at the moment. > > There are packages for stable available though. They seem to work well. There is a gforge backport for woody? You have my attention. Where can I find such a beast. I tried backporting this myself but backporting the cone of dependencies made me tired and I decided I would wait for sarge because I was lazy. Bob pgp0.pgp Description: PGP signature
Re: Debian woody or sarge?
On Sun, Nov 16, 2003 at 11:11:03AM -0700, Bob Proulx wrote: > Stable is not up to handling gforge at the moment. There are packages for stable available though. They seem to work well. Frank -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian woody or sarge?
David Z Maze wrote: > Philip Ross writes: > > I am looking to migrate a few Red Hat boxes to Debian in the next > > month or two and am currently wondering whether to install woody or > > sarge. You did not say but are those servers or desktops? Desktop users tend to be brutal. They want the latest bright object to swing by their field of view. They think a week is a long time to wait for something. They complain forever about something if it is broken. If you only have two desktop users then you will be able to convince them that stable is a good thing. I would have my mom run stable. But if you have a hundred (or several hundred) users then you won't be able to politic that successfully. Many of them are also very sharp hackers too. They will want the latest xine or something. I routinely have users that spin their desktop to unstable, and then complain that something is broken there! I just expect that. And laugh at them. Bwahawha... :-) Who are your users? Servers on the other hand are different. Debian stable is a perfect fit for them. Stable has everything they need. Rock solid. Security updates. It is a beautiful thing. (Yes, I admit that I took my servers to LaMont's latest bind9 and postfix backports. But I know those services very well personally too.) Servers to me mean DNS, NTP, NIS/YP, SMTP, etc. But servers might mean defect trackers, gforge/sourceforge style web environments, other things. Stable is not up to handling gforge at the moment. Just an example that one person's idea of server is different from another person's idea. What is yours? > If you're new to Debian, I'd strongly suggest starting with the stable > distribution (so, in this case, woody); if you decide it's too stale > for you, you can augment it with backports or decide to upgrade to > testing or unstable later. If you decide that testing is too broken > for you right now, it's very hard to go back to stable. And let me agree with everything David said. This is exactly my strategy for the machines I support. Bob pgp0.pgp Description: PGP signature
Re: Debian woody or sarge?
"Philip Ross" <[EMAIL PROTECTED]> writes:
> I am looking to migrate a few Red Hat boxes to Debian in the next
> month or two and am currently wondering whether to install woody or
> sarge.
If you're new to Debian, I'd strongly suggest starting with the stable
distribution (so, in this case, woody); if you decide it's too stale
for you, you can augment it with backports or decide to upgrade to
testing or unstable later. If you decide that testing is too broken
for you right now, it's very hard to go back to stable.
> I've seen posts that suggest sarge will become the stable
> distribution soon
> (http://lists.debian.org/debian-devel-announce/2003/debian-devel-announce-20
> 0308/msg00010.html). Can anyone point me to an up to date
> estimation of the release date?
There's a current thread on debian-devel discussing this. I don't
think I've seen an announcement yet naming a date for the sarge
freeze, so "several months out at the least" would be my statement.
> Given Red Hat updates will end at the end of the year, I want to get
> up and running with Debian before that. If sarge doesn't become
> stable until next year, would it be better to install woody now and
> upgrade to sarge in a few months, or install sarge now? How long
> will woody remain supported with security updates?
I think it's better to install woody now; upgrading should be pretty
straightforward, either before or after sarge releases. ("Install
woody and upgrade to sarge" is probably also the easiest way to wind
up with an installed sarge system, though there's a testing version of
the new Debian installer out.) Again, I don't have an official
statement on how long woody will be supported, but given the flak
people have taken before for trying to desupport things, it'll
hopefully be a while. :-) (I think potato was supported for six
months or so beyond the woody release, can't find the information
online right now.)
--
David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian woody or sarge?
On Sun, 2003-11-16 at 07:04, Philip Ross wrote: > Given Red Hat updates will end at the end of the year, I want to get up and > running with Debian before that. If sarge doesn't become stable until next > year, would it be better to install woody now and upgrade to sarge in a few > months, or install sarge now? How long will woody remain supported with > security updates? http://www.debian.org/security/faq#lifespan : Q: How long will security updates be provided? A: The security team tries to support a stable distribution for about one year after the next stable distribution has been released, except when another stable distribution is released within this year. It is not possible to support three distributions; supporting two simultaneously is already difficult enough. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
