On Sat, Dec 07, 2002 at 06:38:16PM -0500, sean finney wrote:
> On Sat, Dec 07, 2002 at 11:15:30PM +, Colin Watson wrote:
> > Not at all. I've never used 'apt-get dist-upgrade' - always dselect. :)
>
> right, i don't think dselect was the cause of the problem. i think
> the problem was that he
On Sat, Dec 07, 2002 at 11:15:30PM +, Colin Watson wrote:
>
> Not at all. I've never used 'apt-get dist-upgrade' - always dselect. :)
right, i don't think dselect was the cause of the problem. i think
the problem was that he removed all his previous stable sources and
put in a bunch of testi
On Sat, Dec 07, 2002 at 01:19:50PM -0800, Lukas Latz wrote:
> Thanks for the responses, guys!
>
> The apt-get update and apt-get dist-upgrade took care of it.
> I guess it was pretty naive of me to just run dselect...
Not at all. I've never used 'apt-get dist-upgrade' - always dselect. :)
--
Co
Thanks for the responses, guys!
The apt-get update and apt-get dist-upgrade took care of it.
I guess it was pretty naive of me to just run dselect...
The error also does come up with apt-get update but there it doesn't hang the install
script.
Makes all the difference :-)
Lukas
___
On Sat, Dec 07, 2002 at 07:46:23AM -0800, Lukas Latz wrote:
> The download ran for quite a while and then a preconfigure script
> broke off the message that's below. I've seen config scripts fail
> before, but usually that doesn't stall the dselect, this one does -- I
> had to ctrl-c -- now my var/
heya,
to upgrade a system, i'd do apt-get update and then apt-get dist-upgrade
both before running dselect. actually, i wouldn't use dselect at all
but that's personal preference. either way, the only error that i'd
be concerned about from your post is:
On Sat, Dec 07, 2002 at 07:46:23AM -0800,
6 matches
Mail list logo
