Re: Upgrading from bo to hamm

1998-04-18 Thread Steve Greenland
On 13-Apr-98, 09:05 (CDT), Scott Ellis <[EMAIL PROTECTED]> wrote: > [re: bad symlinks for ldconfig] > > The messages are a symptom of not having the library and -dev package > versions in sync. The solution is to either bring them into sync, or > uninstall the -dev package. Either way will fix y

Re: Upgrading from bo to hamm

1998-04-13 Thread Scott Ellis
On Sun, 12 Apr 1998, Chris Fearnley wrote: > 'Guy Maor wrote:' > > > >"LeRoy D. Cressy" <[EMAIL PROTECTED]> writes: > > > >> I question the purpose of leaving broken symbolic links when > >> upgrading the libraries. For instance libreadline2 leaves > >> the following broken links reported by ldc

Re: Upgrading from bo to hamm

1998-04-13 Thread Chris Fearnley
'Guy Maor wrote:' > >"LeRoy D. Cressy" <[EMAIL PROTECTED]> writes: > >> I question the purpose of leaving broken symbolic links when >> upgrading the libraries. For instance libreadline2 leaves >> the following broken links reported by ldconfig: > >Those symlinks are part of libreadline2-dev. If

Re: Upgrading from bo to hamm

1998-04-11 Thread LeRoy D. Cressy
Steve Greenland wrote: > > On 09-Apr-98, 22:04 (CDT), Guy Maor <[EMAIL PROTECTED]> wrote: > > "LeRoy D. Cressy" <[EMAIL PROTECTED]> writes: > > > > > I question the purpose of leaving broken symbolic links when > > > upgrading the libraries. For instance libreadline2 leaves > > > the following br

Re: Upgrading from bo to hamm

1998-04-11 Thread LeRoy D. Cressy
Guy Maor wrote: > > "LeRoy D. Cressy" <[EMAIL PROTECTED]> writes: > > > I question the purpose of leaving broken symbolic links when > > upgrading the libraries. For instance libreadline2 leaves > > the following broken links reported by ldconfig: > > Those symlinks are part of libreadline2-dev

Re: Upgrading from bo to hamm

1998-04-10 Thread Steve Greenland
On 09-Apr-98, 22:04 (CDT), Guy Maor <[EMAIL PROTECTED]> wrote: > "LeRoy D. Cressy" <[EMAIL PROTECTED]> writes: > > > I question the purpose of leaving broken symbolic links when > > upgrading the libraries. For instance libreadline2 leaves > > the following broken links reported by ldconfig: >

Re: Upgrading from bo to hamm

1998-04-10 Thread Guy Maor
"LeRoy D. Cressy" <[EMAIL PROTECTED]> writes: > I question the purpose of leaving broken symbolic links when > upgrading the libraries. For instance libreadline2 leaves > the following broken links reported by ldconfig: Those symlinks are part of libreadline2-dev. If you upgrade to libreadline

Upgrading from bo to hamm

1998-04-09 Thread LeRoy D. Cressy
Hi All, I question the purpose of leaving broken symbolic links when upgrading the libraries. For instance libreadline2 leaves the following broken links reported by ldconfig: Setting up libreadline2 (2.1-8) ... ldconfig: warning: can't open /usr/lib/libpthread.so (No such file or directory), s