On Mon, 8 Nov 1999, Hamish Moffatt wrote: > Too late, it's all done now. I definately saw a lot of packages > fail to configure because xpm4g was not yet configured; similar with > gcc and binutils, IIRC. dpkg is 1.4.1.19. The other way this can happen is if xpm4g was configured but failed for some reason, then dpkg will continue on and show these other confusing warnings. Could that be the problem? Jason