[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Testing upgrade and consequences



On Wed, Mar 14, 2001 at 11:25:26PM +0000, Martin WHEELER wrote:
> On Wed, 14 Mar 2001, Joey Hess wrote:
...
> > And things broke. This is a suprise?
> 
> Yes.
> Shouldn't it be?  Please explain.
> (This is the method I have used to incrementally upgrade my installation
> for the past two years -- without problem.)
> Why should I expect things to break using this method?
> [This is a genuine query.  Don't understand your stance.  Really.]

If it isn't labelled "stable", things may break. If you try to updgrade
the whole distribution plus a bunch of 3rd party software to an unstable
snapshot of a not-yet-released distro... well, _I_ would expect things
to break. All of them. So yes, you should expect thing to break in
these circumstances.

I was fortunate: I had a clean box so I could load up minimal potato,
upgrade to testing and then install the stuff I need. That was painless.

> But I doubt whether any developer could reproduce this system exactly
> without an accurate image of my machine state; so I'll start with the
> big problem (apache) and try to send in a fuller description of all the
> problems encountered once I've sussed how to do 'proper' bug reports,
> and where to send them.

FWIW, purging apache-perl and installing apache and mod-perl fixed that 
for me.

Dima
-- 
E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home)
I'm going to exit now since you don't want me to replace the printcap. If you 
change your mind later, run
    -- magicfilter config script



Reply to: