On Tue, Sep 14, 2004 at 11:20:50PM +1000, Hamish Moffatt wrote: > On Tue, Sep 14, 2004 at 02:00:17PM +0200, Jeroen van Wolffelaar wrote: > > On Tue, Sep 14, 2004 at 09:55:10PM +1000, Hamish Moffatt wrote: > > > Thanks for the report. I've seen the build logs before. Care to tell me > > > why you think this isn't a bug in the fftw packages though? > > > > I don't know, but it's gmfsk that fails to build, so in a way, it's > > gmfsk's problem. > > Say what? So if libc6 is broken, it's every other package's problem?
Well, then nothing works anymore. But if some obscure bug in the toolchain causes only a few packages to break, that's actually still a problem for those packages, yes. They should be always buildable. The bug on the trouble-causer might not be considered RC, and without a bug on the packages failing to build, the lot might get released, which isn't good. In a way, this is a marker bug. It indicates something must be done to resolve a release-critical issue with this package, either by fixing the root cause so this package builds again, working around the issue in the package, simply drop any arm build from this package and don't build for arm anymore until it's fixed, or, extreme solution, drop this package altogether (no, I don't think the last 'solution' is a good solution). --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl
