On Thu, Jan 01, 2004 at 10:42:18AM +0000, Paul Worrall wrote: > Hi, > > During my latest updrade using aptitude, I get: > > Setting up foomatic-filters (3.0.0-2031207-1) > Configuration file `/etc/foomatic/filter.conf' > ==> File on system created by you or by a script. > ==> File also in package provided by package maintainer. > What would you like to do about it ? Your options are: > [list of options] > *** filter.conf (Y/I/N/O/D/Z) [default=N] ? > > but whatever I enter at the prompt (including nothing to accept the > default) followed by return, it just sits there doing nothing until I > kill it using <Control>-C. I would like to submit a bug report, but I Sometimes, the configuration procedure is quite overlong, with no tty output--how long did you wait before killing it, really? > am not sure which package to submit it against, can anyone please advise? Note, that unless you are using unstable, it's not really expectable for a package not to configure, and, moreover, to halt silently (unless you have the POSIXLY_CORRECT environment variable set--then it's just your daily bread). If you are using stable/testing, dig out first before blaiming it on a certain package. If it really is foomatic-filters, ``dpkg-reconfigure foomatic-filters'' will reproduce what you've described. If not, read on. Try to install the packages one-by-one, so you know which one to blame. In case of dependencies, you may resort to dpkg -i /var/cache/apt/archives/foo.deb if it's already downloaded succesfully (apt-get would tell you if it had failed to download it). ``apt-get install <package>'' is the way to go if you are not sure aptitude doesn't do something you don't know about. IIRC, aptitude logs the packages it installs in something like /var/log/aptitude. Or just do grep -drecurse aptitude /var/log as root, or any user having a read access to /var/log files. Cheers, Jan. -- Jan Minar "Please don't CC me, I'm subscribed." x 4
Attachment:
pgpj4YSk_nLMa.pgp
Description: PGP signature