Bug#205973: acknowledged by developer (Re: Bug#205973: xlibs: /usr/X11R6/lib/X11/xkb/compiled)
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.
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.
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. 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
Jim
Reply to: