Christian Marillat <[EMAIL PROTECTED]> writes: > Sven Luther <[EMAIL PROTECTED]> writes: > >> On Fri, Sep 12, 2003 at 03:43:29PM +0200, Christian Marillat wrote: > > [...] > >>> Months ? Who is talking about months ? If you really want to see 2.4 in >>> testing more quicly try to find whats wrong with glib/gcc bugs, but this >>> isn't so easy. >> >> So the only thing which is stopping gnome 2.2 from entering sarge is >> glibc/gcc, upload to testing-proposed-updates then, and everything is >> fine. (If the RM agrees, that is). > > I'll ask NM for that. We only need to move two packages in testing the > control-center and gnome-terminal.
With control-center, the issue isn't glibc but gnome-pilot, right? In sarge there is libgnome-pilot1 while sid has libgnome-pilot2. The old gnome-pilot in sarge depends on libcapplet0 which is part of the old control-center source package. I haven't investigated, why the new gnome-pilot isn't ready for sarge yet. Someone recently wrote that the problem involves a long dependency chain, including KDE. But http://bjorn.haxx.se/debian/ certainly has the answer. So to force gnome2 into sarge, the gnome-pilot package would have to be temporarily removed from testing (or deliberately broken). Do you think this is acceptable to the RM? Thanks, Johannes
