On Tue, Nov 28, 2006 at 06:11:58PM +0100, Christian Perrier wrote: > Quoting Santiago Garcia Mantinan ([EMAIL PROTECTED]):
> > If FAM was really not intended I think we should disable it on our config > > and upload with high urgency to get a version without FAM to testing ASAP. > A discussion we had yesterday on IRC with Steve, lead to the > conclusion that this bug is really worth being fixed for etch. > Disabling in the provided config file is of course not enough and we > should probably, at least for etch, disable the FAM support. > However, upstream did not provide a clean way to do it in its > configure script so I guees that fixing this is up to people in the > team that have a better knowledge than me on configure scripts. > Steve, Peter, Noèl, Eloy? > manty also, if you come up with a patch..:-) A build-conflict with the -dev package should be sufficient, shouldn't it? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/