* Adam Heath ([EMAIL PROTECTED]) [031026 19:55]: > For instance, if we delay this 'fix' until after sarge is release, we will > *still* have the problem then. There will be backed in sarge that *will not > build* when sarge+1 is released.
No. If you change this as soon as sarge is out, it's very likly that all failures of other packages are detected during the release-cycle. (And the reason for this is that it's likly that most packages are recompiled on sid between two releases. So, these bugs will be detected then, and not short before a release.) However, changes now do introduce hidden failures on packages just very short before release, and that could make it very hard to produce fixes e.g. for security problems. And it's very likly that these problems won't be fixed before sarge is out, because nobody is just now compiling all packages to check that all packages are compilable on sarge. Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C
