Re: probem going bash 1.14.7-2 to 2.0-3
I had the same experience, but on a headless machine. Once I shut it down
I could not log in again. The installation was just a test bed so I
reinstalled from scratch.
Lindsay
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lindsay Allen <allen@cleo.murdoch.edu.au> Perth, Western Australia
voice +61 8 9316 2486 modem +61 8 9364-9832 32S, 116E
http: http://rolf.ece.curtin.edu.au/~lindsay debian linux
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Sat, 12 Jul 1997, Douglas Stewart wrote:
> > Preparing to replace bash 1.14.7-2 (using .../base/bash_2.0-3.deb) ...
> > Unpacking replacement bash ...
> > Setting up bash (2.0-3) ...
> > sh: can't resolve symbol 'rl_filename_quoting_function'
> > dpkg: error processing bash (--install):
> > subprocess post-installation script killed by signal (Segmentation fault), core
> > dumped
> > Errors were encountered while processing:
> > bash
> > dpkg install failed.
> > What now [?,d,r,q,fd,fc,p] (defer):
>
> Anyone have an idea what caused this? I was upgrading to debian 1.3
> and I got this. It was quite a nightmare as you can probably
> imagine. :/
>
> I had to find the rex bash and then i couldn't install it because
> sh was broken. I ended up having to ftp the package to another
> machine (binutils wasn't completely set up yet, and was missing
> libbfd), use ar to extra the files, and gunziip and untar the data
> file and copy the binary over. Whew, at least I survived this.
>
> -douglas
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> debian-user-request@lists.debian.org .
> Trouble? e-mail to templin@bucknell.edu .
>
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: