On Tue, Dec 12, 2000 at 06:21:17PM -0800, Seth Arnold wrote: > * Drew Parsons <[EMAIL PROTECTED]> [001212 18:18]: > > > That's dpkg-reconfigure, actually... > > > > "dpkg-reconfigure xfree86-common" doesn't seem to do anything for me. It > > runs, exits, and Xwrapper.config is exactly the same as it was before. > > This would probably mean you set your debconf severity level to such a > state that it doesn't bother asking you the question. Reconfigure > debconf, and see if that changes matters. :) (And if you think Branden > screwed up the priority of the question, be sure to let the list know. > :) >
I found the problem. It's not done in xfree86-common, it's done by xserver-common! It's asking me the right questions now :) Incidentally, the /etc/X11/Xwrapper.config is not found by dpkg -S, which is technically fine, since, as I understand it, the file isn't "in" the package, it's only generated dynamically by it. But it might have been helpful for it to be listed, so that I could have verified earlier which package it is in. Are there reasonable grounds for the file to be explicitly placed in the X source, so it's registered as belonging? Or, more ambitiously, should debconf (or whatever is generating the file) be able to add the new file to the database of registered files when desired? Drew -- PGP public key available at http://dparsons.webjump.com/drewskey.txt Fingerprint: A110 EAE1 D7D2 8076 5FE0 EC0A B6CE 7041 6412 4E4A
