Heikki Vatiainen wrote:
>
> Hi all,
>
> I finally decided to jump from stable to unstable. I pointed dselect to
> unstable and as a result I was faced with an enormous number of new and
> updated packages.
>
> Among the updated packages were e.g. bash 2.0 that's known to break at least
> some of
Heikki Vatiainen <[EMAIL PROTECTED]> writes:
> Is there something I should know or keep my eye on during this jump? For
> example, is it wise to install the new bash straight ahead or should I put it
> on hold instead and install it after all the other packages?
I'd say put bash-2.0 on old for
Hi all,
I finally decided to jump from stable to unstable. I pointed dselect to
unstable and as a result I was faced with an enormous number of new and
updated packages.
Among the updated packages were e.g. bash 2.0 that's known to break at least
some of the scripts that work with the older 1.
3 matches
Mail list logo