On Mon, Aug 18, 2003 at 10:22:46PM -0400, Jim Bray wrote: > I did a reinstall of xbase-clients and it did create the > symlink. It appears possible that an 'event' involving > the 2.6.0-pre3 kernel might have led to some silent > Reiserfs deletions. That kernel is not ready for prime time.
Okay. I'm glad to hear my packages (probably) weren't at fault. > dpkg -S still shows no owner of the symlink in question: > > xkb/2#dpkg -S `pwd`/compiled* > dpkg: /usr/X11R6/lib/X11/xkb/compiled not found. They won't; dpkg -S reports only on a package's "payload"; that is, stuff in /var/lib/dpkg/info/$package.list, not stuff created by the package's maintainer scripts. > On Mon, 2003-08-18 at 15:45, Branden Robinson wrote: > > That's not the only way to look for it. Dpkg manages symlinks to > > directories poorly, so you'll find that the xbase-clients preinst and > > postinst scripts manage this symlink. > > OK, I'd been operating on the mistaken assumption that if > dpkg -S doesn't find a given file, the file is not managed > by Debian. It does mean that it's not installed or removed by dpkg as such. > Obviously that isn't right. If you can recommend > the procedure I should have followed to figure out which package was > responsible for this file, and thus which to try reinstalling, I can > avoid filing similar mistaken reports. I picked xlibs because > I could find no owner of ..../compiled, but the parent dir is owned > by xlibs: > > xkb/2#dpkg -S `pwd` > xlibs: /usr/X11R6/lib/X11/xkb Unfortunately there is no wonderful method for determining this; essentially, you have to grep the maintainer scripts in /var/lib/dpkg/info. Dpkg provides no mechanism at present for permitting packages to "register" additional filenames that a package doesn't unpack, but might be interested in. -- G. Branden Robinson | There's no trick to being a Debian GNU/Linux | humorist when you have the whole [EMAIL PROTECTED] | government working for you. http://people.debian.org/~branden/ | -- Will Rogers
pgp00000.pgp
Description: PGP signature
