On Tue, Dec 28, 2004 at 01:53:21PM +0200, David Baron wrote:
> Something I proposed a while back: A workable backtracking mechanism in apt.
I'll post version 2.0 of my script that does this, with some
documentation, here presently.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
Something I proposed a while back: A workable backtracking mechanism in apt.
There already is for single "off-site" packages--an option to explicitely
enable a "downgrade" back to the original.
Simplest would be the backtrack to the previous systems configuration.
Snapshots would be a larger an
On Mon, 2004-12-27 at 11:40 -0500, Greg Folkert wrote:
> On Mon, 2004-12-27 at 09:18 -0600, Alex Malinovich wrote:
--snip--
> > But I do absolutely agree that for mission critical systems, stable
> > should be the only real choice.
>
> With or without backports? Or hand compiled packages? or Third
On Mon, 2004-12-27 at 09:18 -0600, Alex Malinovich wrote:
> On Sun, 2004-12-26 at 22:39 -0600, Tim Kelley wrote:
> --snip--
> > If you think testing or unstable is suitable for production systems you are
> > one of
> >
> > 1. an idiot
> > 2. have very limited needs/no experience
> > 3. talking ou
On Sun, 2004-12-26 at 22:39 -0600, Tim Kelley wrote:
--snip--
> If you think testing or unstable is suitable for production systems you are
> one of
>
> 1. an idiot
> 2. have very limited needs/no experience
> 3. talking out of your ass
> 4. have no concept of what it means to be responsible for
On Monday 27 December 2004 03:58, Bob Alexander wrote:
> Kelley ? His opinions are valuable as any other and, sadly, expressed
> with a tone that surely does not make them sound more authoritative than
> the tantrums of a freckled face 14 yr old nerd.
He has freckles?
--
To UNSUBSCRIBE, email t
Greg Folkert wrote:
So what do you think of those of us that *DO* use Sid + Experimental for
Production?
Careful what you say... I do have experience with Debian. No I am not an
idiot, I have very UN-limited needs, I have been known to talk out
of /dev/ass, have built very elaborate systems to ensu
On Sun, Dec 26, 2004 at 02:42:31PM -0500, William Ballard wrote:
> > On Sat, 2004-12-25 at 10:05 -0600, Alex Malinovich wrote:
> > > Sid is probably not the right choice if you need to run a nuclear
> > > defense grid, but for day to day work on the desktop and even on
> > > servers, it's plenty st
On Sun, 2004-12-26 at 22:39 -0600, Tim Kelley wrote:
> On Saturday 25 December 2004 10:05, Alex Malinovich wrote:
>
> > Sid is probably not the right choice if you need to run a nuclear
> > defense grid, but for day to day work on the desktop and even on
> > servers, it's plenty stable enough in m
On Sun, Dec 26, 2004 at 10:39:47PM -0600, Tim Kelley wrote:
> I am getting really sick of people pushing sid for production use. Please
> stop
> doing it. I don't really care if it meets your needs. If it does, you are a
> tiny minority; your experience with it in this capacity is anecdotal, a
On Saturday 25 December 2004 10:05, Alex Malinovich wrote:
> Sid is probably not the right choice if you need to run a nuclear
> defense grid, but for day to day work on the desktop and even on
> servers, it's plenty stable enough in my experience.
You've got to be kidding me. I've run sid for ab
On Sun, Dec 26, 2004 at 11:08:17PM +0100, Marc Demlenne wrote:
> Seems to be a good way to operate, rather secure... But isn't there a
> way to manage this automatically ? It doesn't sounds impossible nor
> stupid, does it ?
It's really easy to set up your own "dists" directory with a tweaked
'Pa
> With that said, what I usually do for my servers is do an update every
> two weeks, storing the list of packages that WOULD be upgraded in a text
> file. Then when I do my next update, I compare that list vs the list of
> two weeks ago and only install the packages that HAVEN'T changed. This
> gi
On Sun, 2004-12-26 at 14:42 -0500, William Ballard wrote:
> > On Sat, 2004-12-25 at 10:05 -0600, Alex Malinovich wrote:
> > > Sid is probably not the right choice if you need to run a nuclear
> > > defense grid, but for day to day work on the desktop and even on
> > > servers, it's plenty stable en
> On Sat, 2004-12-25 at 10:05 -0600, Alex Malinovich wrote:
> > Sid is probably not the right choice if you need to run a nuclear
> > defense grid, but for day to day work on the desktop and even on
> > servers, it's plenty stable enough in my experience.
Running unstable on an outward-facing serv
On Sat, 2004-12-25 at 10:05 -0600, Alex Malinovich wrote:
> [snip]
>
> Sid is probably not the right choice if you need to run a nuclear
> defense grid, but for day to day work on the desktop and even on
> servers, it's plenty stable enough in my experience.
I agree with this, with the caveat tha
Rogério Brito wrote:
> Just hang on a second! If you are so afraid of breaking your system, you
should not be using sid, but using testing instead.
Did I really sound that afraid ?!
Natural language is such an imprecise tool. Especially when two
different mothertongue use a third language to comm
On Dec 25 2004, kurtz wrote:
> However, it's useful to have one's system wholy fu***d down at least once
> in one's live, just to know what sid's really about.
Yes, that is a good lesson. The hard way to learn, but also a good way to
see if you can get your act together when big troubles come haun
On Dec 25 2004, Bob Alexander wrote:
> Of course you should not "trust" packages which have just appeared since
> they will most probably never have crit bugs. Correct ? For instance the
> LVM2 and HAL examples I was making appeared a few hours agon on the
> mirror I use.
Just hang on a second!
Bob Alexander wrote:
> One solution for the "fundamental packages" (please do not call me
> coward but only cautious) would be, (like the medicine example on top)
> to wait a little time (say one week ten days) before installing any new
> packages and before that checking if/which serious bugs h
Bob Alexander escribe:
> Is that it ?
Is that it. However, it's useful to have one's system wholy fu***d
down at least once in one's live, just to know what sid's really
about.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Rob Bochan wrote:
I use it myself on my laptop that runs Sid, which I use for my business, to
check to see if there's anything major I need to know before I upgrade
anything. It runs automatically whenever I run apt-get upgrade. It's saved my
butt more than once.
Thank you very much Rob.
Of cou
On Saturday 25 December 2004 12:45 pm, Bob Alexander wrote:
> It will warn of critical bugs pending on each of the files to be
> downloaded.
>
> Is that it ?
According to
http://packages.debian.org/unstable/admin/apt-listbugs
"apt-listbugs is a tool which retrieves bug reports from the Debian Bu
Rob Bochan wrote:
On Saturday 25 December 2004 10:48 am, Bob Alexander wrote:
Is there an automatic way to check even only for the number of severe
bugs for a package from any of the package manager frontends ?
Install the apt-listbugs package.
Sounds GREAT. Tried reading or finding examples on G
Hugo Vanwoerkom wrote:
Or you could use William Ballard's system of keeping the upgrades
separate by differently labeled .deb directories and simply reverting to
a set of .debs that worked if you run into problems.
He has posted his scripts to this list at least twice that I know of.
Sounds nice
On Saturday 25 December 2004 10:48 am, Bob Alexander wrote:
> Is there an automatic way to check even only for the number of severe
> bugs for a package from any of the package manager frontends ?
Install the apt-listbugs package.
--
...Rob
Return address is obfuscated.
You can reach me via my
Bob Alexander wrote:
Background considerations, question follows:
When I was studying as a doctor (a lng time ago) my Pharmacology
professor told us:
"A good doctor is never the first to use a new medicine and never the
last to abandon an old one"
and later on my sailplane instructor told m
On Sat, 2004-12-25 at 16:48 +0100, Bob Alexander wrote:
--snip--
> While I love using sid because of the very current releases and I am
> willing to take the risk of having to debug "some" problems, being the
> system I WORK with the only I have, getting fundamental things wrong can
> seriously
28 matches
Mail list logo
