[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Getting GNOME 2.10 in: roundup of remaining issues



On Fri, Sep 09, 2005 at 04:54:18PM -0400, Nathanael Nerode wrote:
> >Trying hint from vorlon: libxklavier/2.0-0.2 gnome-vfs2/2.10.1-5
> >libwnck/2.10.3-1 libgnomeui/2.10.1-1 libgtop2/2.10.2-1 libgsf/1.12.2-1
> >librsvg2/2.9.5-4 eel2/2.10.1-2 libexif/0.6.12-2 exif/0.6.9-5
> >evolution-data-server/1.2.3-2 gphoto2/2.1.6-2 gthumb/3:2.6.6-1
> >libexif-ruby/0.1.2-7 libgphoto2/2.1.6-3 openh323/1.15.3-4 pwlib/1.8.4-2
> >libdc1394/1.1.0-2 gnome-python/2.10.0-2 coriander/1.0.1-2
> >asterisk-oh323/0.6.6pre3-4 gnomemeeting/1.2.1-2 gnugk/2:2.2.2-3
> >aalib/1.4p5-28 gimp/2.2.8-9 gal2.4/2.4.3-1.1 nautilus/2.10.1-4
> >openoffice.org/1.1.4-7 openoffice.org-debian-files/1.1.4-6+1

> I notice you've already added:
> -evolution-data-server1.2/1.2.2-5.1 gstreamer0.8/0.8.11-1 evolution/2.2.3-4 nautilus-cd-burner/2.10.2-1.1
> (Does that '-' thing actually work in a hint?)

Apparently not, given that the hint failed today.

> Removals needed:
> remove perlpanel/1:0.9.1-1
> -- perlpanel depends on libgnome2-wnck-perl

Check, added.

> Builds needed:
> libimage-exif-perl/1.00.3-2 needs to be built everywhere

Right.

> ohphone needs to be built on m68k.
> openam/1.1.18+20050304-2 needs to be built on m68k.
> openmcu/2.1.0-2 needs to be built on m68k.
> pstngw/1.3.1-4 needs to be built on m68k.

I'm going to go ahead and bump these from testing, actually, since
they're still a way down in the m68k build queue.  They should get right
back in as soon as they're built.

> gcalctool has been built on arm and needs to be uploaded.
> poppler/0.4.2.1 needs to be built on arm.
> evince needs to be built on arm (after poppler), hppa, ia64, m68k, s390, sparc.

What do these have to do with getting GNOME 2.10 in?  The last two are
not in testing at all right now, and I haven't noticed any of these
three packages listed in the hint output.

> Serious problems:
> * gnome-system-tools has grave bug #309932.

Again, I haven't seen where this affects the GNOME 2.10 hint.

> * And then there's the real problem package: kamera.
> The version in testing depends directly on libexif10, which is of course not
> present in unstable.

> We don't want GNOME and KDE to have to go in at the same time.  So there's
> only one thing to do, which is to deliberately break kamera in testing.
> (Removing kdegraphics from testing is clearly a less desirable option, and
> I don't think we can remove kamera without removing all of kdegraphics.)
> I don't see a simple way to do this except changing the 'hint' to a
> 'force-hint', which should obviously only be done after everything else
> is ready.

Yes, this is already the plan.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


Reply to: