At Thu, 21 Aug 2003 00:17:27 +1000, Anthony Towns wrote: > [1 <text/plain; us-ascii (quoted-printable)>] > On Wed, Aug 20, 2003 at 08:49:33AM -0400, Matt Zimmerman wrote: > > On Tue, Aug 19, 2003 at 04:49:25PM +1000, Anthony Towns wrote: > > > Also make sure to include some leg room if you depend on packages that > > > have a tendency to be buggy (glibc, for example). > > The new glibc has already stalled the progress into testing of a large > > number of packages, and the number of RC bugs still seems to be going up. > > How are we going to manage to produce a release in 6 months the face of this > > obstacle? The last time there was this sort of breakage, it took many > > months just to get glibc itself it sorted out. > > Yup. The difference is that this time we have a Glibc maintenance team > that's able to work together effectively, has some experience with the > package, and has a better understanding how important it is to get it > fixed quickly.
AFAIK, the unresolved difficult bugs are: (1) hppa build (2) dpkg (setjmp/longjmp) on sparc (3) NIS (will be fixed?) (4) misterious apache on ia64 bug. Note that (3) becomes ok to revert patches, (4) may be non-glibc bug. Well, they are still something hard work. :-) My concern is (1) hppa build. If we can't get hppa glibc, we may need to drop it finally... Regards, -- gotom