> If you can tell me the order in which to try build these packages, > I
could fire off some manual builds. However, I don't know how
> many of these are going to be able to go into testing yet, because >
of the libcupsys transition.
It looks like someone short-circuited the process today, allowing
a couple of the packages into testing even though they hadn't been
built on alpha.
glib2.0 went in according to the rules. pango1.0 and atk1.0 were
forced in without building on alpha, I think that those are
priority (I believe that each depends on glib2.0 but neither
depends on the other).
Based on the dependencies from bjorn.haxx.se, I would suggest
the following order. These packages have no other issues blocking
entry into testing other than that they haven't been built on
alpha and/or haven't reached 10 days old yet (unless marked).
If you go in this order (and I didn't mess up), the packages
should be able to go straight into testing.
pango1.0
atk1.0
gtk+2.0
orbit2
libxml2
libxslt
libbonobo
gconf2
gnome-vfs2
libglade2
libgnomecanvas
libwnck
libgtop2
libbonoboui (also not built on m68k)
libgnomeui (also not built on m68k)
gnome-themes (also not built on s390)
libgsf (also not built on s390)
librsvg2
gnome-desktop (also not built on m68k)
eel2 (also not built on m68k)