[conspire] quiet , and mepis 6.5

Rick Moen rick at linuxmafia.com
Tue Apr 10 01:20:46 PDT 2007

Quoting David E. Fox (dfox at m206-157.dsl.tsoft.com):

> Have you (or anyone else) switched "etch" to "lenny" yet
> on /etc/apt/sources.lst?

My server box did, believe it or not -- automatically, because it says
"testing" in there.  I do not, in general, use branch names in
sources.list on Debian.

> Is it safe to do so, yet?

Sadly, experience suggests that this probably isn't going to be a
fruitful conversation -- as you're doing relying on bad assumptions, and
aren't likely to listen.  But I'll try:

I assume that, in the recent past, you've operated a box with
sources.list set to "etch".  I personally think that's dumb, but --
moving on -- that fact implies that you've recently operated the machine
for some unspecified period of time during the stretch when etch had the
"testing" track's symlink pointed to it.

That being the case, were you at that time period prepared to deal with
the kinds of relatively minor, occasionally breakage associated with
keeping a Debian box synced to the testing track?  If _not_, then you
should not have done that in the first place, should have stuck with the
stable track (at that time, set to 3.1 sarge), and for the same reason
should not now follow the testing symlink's relinking from "etch" to

If on the cotnrary you _were_ prepared to deal with the sorts of minor
breakage likely to occasionally happen, over the past 21 months, on
testing=etch, then you can consider yourself by the same token _still_
prepared to deal with those minor upheavels on testing=lenny.  Because
it'll just be more of the same.

Yes, they'll probably be a little more numerous as the pace of change
will increase and be rougher for a month or two, but experience with the
testing branch going all the way back to its beginning in (I think) 2.2
"potato" days suggests the bobbles won't be a serious problem.`

But if you're not prepared to deal with (say) occasional postinst
scripts or having to reinstall a desired package because a temporary
dependencies snarl has caused its removal, then stick to the "stable"
track, be bored, and be happy.

And, if you're going to do _that_, at least get the word "etch" the hell
out of your sources.list, and substitute "stable", since that's
apparently what you're attempting to follow.

More information about the conspire mailing list