On Sat, 18 Apr 1998, Luiz Otavio L. Zorzella wrote:
Marcus Brinkmann writes:
I think this is only linker confusion and has its cause by removing
libraries and symlinks and running ldconfig in the wrong order.
Policy about calling ldconfig in package scripts is changing at the moment,
W Paul Mills writes:
nr# ldconfig
ldconfig: warning: can't open /usr/lib/i486-linuxaout/libdb.so.1 (No such
file or directory), skipping
ldconfig: warning: can't open /usr/lib/libext2fs.so (No such file or
directory), skipping
ldconfig: warning: can't open /usr/lib/libe2p.so (No such file
Joerg Plate writes:
I guess I'll just delete them and just forget about it :^
man symlinks
I believe you mean man symlink, and you are talking about:
NOTES
No checking of oldpath is done.
Deleting the name referred to by a symlink will actually
delete the file
On Fri, Apr 17, 1998 at 11:18:38AM -0700, Luiz Otavio L. Zorzella wrote:
Since we're talking about leftovers, these messages are, AFAIK, due to
leftovers from some packages, and they are not directories.
Can you tell me how to get rid of them? They appear in some dpkg -i
commands...
Marcus Brinkmann writes:
I think this is only linker confusion and has its cause by removing
libraries and symlinks and running ldconfig in the wrong order.
Policy about calling ldconfig in package scripts is changing at the moment,
and we hope to have the proper solution implemented for
Marcus Brinkmann wrote:
Normally, all directories that are not needed anymore are removed.
In this special case, they are not.
Marcus
It's not a bug, it's a feature!
... but about a dozen bug reports are open against dpkg for this particular
feature at the moment, and I hope one day it
Marcus Brinkmann writes:
On Thu, Apr 16, 1998 at 02:31:40PM -0700, Luiz Otavio L. Zorzella wrote:
Marcus Brinkmann writes:
On Thu, Apr 16, 1998 at 02:13:51PM -0700, Luiz Otavio L. Zorzella wrote:
Marcus Brinkmann writes:
$ dpkg -S /etc/xemacs20/site-start.d
dpkg:
Many times, after upgrading/purging a package, the old/purged version
leaves some files behind it was not supposed to. Just to have an
example, after purging all the xemacs packages:
nr# dpkg -l xemacs*
Desired=Unknown/Install/Remove/Purge
|
On Thu, Apr 16, 1998 at 09:07:38AM -0700, Luiz Otavio L. Zorzella wrote:
Many times, after upgrading/purging a package, the old/purged version
leaves some files behind it was not supposed to. Just to have an
example, after purging all the xemacs packages:
mmmh. This shouldn't happen...
nr#
Marcus Brinkmann writes:
On Thu, Apr 16, 1998 at 09:07:38AM -0700, Luiz Otavio L. Zorzella wrote:
Many times, after upgrading/purging a package, the old/purged version
leaves some files behind it was not supposed to. Just to have an
example, after purging all the xemacs packages:
mmmh.
On Thu, Apr 16, 1998 at 02:13:51PM -0700, Luiz Otavio L. Zorzella wrote:
Marcus Brinkmann writes:
$ dpkg -S /etc/xemacs20/site-start.d
dpkg: /etc/xemacs20/site-start.d not found.
Note, though, that:
1) this is a directory, and not a file!
2) I already purged xemacs* !
Sure. The
Marcus Brinkmann writes:
On Thu, Apr 16, 1998 at 02:13:51PM -0700, Luiz Otavio L. Zorzella wrote:
Marcus Brinkmann writes:
$ dpkg -S /etc/xemacs20/site-start.d
dpkg: /etc/xemacs20/site-start.d not found.
Note, though, that:
1) this is a directory, and not a file!
2) I already purged
On Thu, Apr 16, 1998 at 02:31:40PM -0700, Luiz Otavio L. Zorzella wrote:
Marcus Brinkmann writes:
On Thu, Apr 16, 1998 at 02:13:51PM -0700, Luiz Otavio L. Zorzella wrote:
Marcus Brinkmann writes:
$ dpkg -S /etc/xemacs20/site-start.d
dpkg: /etc/xemacs20/site-start.d not found.
13 matches
Mail list logo
