Attempted anaylsis of testing progression issues
libgc
-----
* oo2c has to wait 6 more days.
* w3m has an RC security bug (#200028) which has not been fixed
(apparently due to some stupid arguments).
* Then, joint hinting will presumably do the trick.
Summary:
w3m should not be setuid root. It needs to be setuid root because
/dev/MAKEDEV in nmakedev 2.3.1-63 creates the framebuffer devices
without read permission for the 'video' group. (!) (devfsd does give
read permission.) The need for read permission cannot be easily avoided
and there's no reason not to give it to users with write permission.
The bug has not been fixed in makedev, and apparently hasn't been
reported there in the BTS.
(There's also a confused argument about the correct use of the
groups, but for the time being, the 'video' group is the correct group.)
Conclusion:
The root of this is a bug in makedev. This should probably be
reported as a bug in makedev and fixed as soon as possible. Then this
can be fixed by the maintainer of w3c.
libsigc++
---------
Waiting for new yehia, which is waiting for libgc. Then, joint hinting
will presumably do the trick.
kde
---
Still waiting for fixed kdelibs and kdebase to be uploaded. (Aaargh...
if I were a DD I'd start to consider NMUing them....) Pretty much
nothing can progress here until those two get uploaded. Aaargh!
mozilla
-------
RC bugs! Dunno what's being done about them! Looks like nothing!
glibc
-----
Apparently new, spiffy glibc is well on its way to going in and should
go in smoothly.
perl
----
Test failures prevent build from finishing on mips, mipsel, m68k.
(Everything else seems to be fixed.) I don't know if anything is being
done about this; I don't see any evidence that anything is being done.
cyrus-sasl2, krb4, heimdal
--------------------------
Need to wait at least 8 more days. Then joint hinting will probably do
the trick.
gnome packages
--------------
Looking in good shape. atk1.0 should go in in a day or so, and take a
lot of stuff in with it.
Reply to: