This bug will be the stabilization bug for GNOME-2.22. Filing it before the stabilization list, so that we can track the true blocker bugs for stabilization purposes, and have other maintainers be able to ask here beforehand packages to be included together with the rest for possible compatibility reasons
some packages in gnome 2.22 (sound-juicer iirc) requires gstreamer >= 0.10.17, hence adding dep on bug #232054
As promised, the gnome-mm list. All of these have been in tree for more than 30 days (except glibmm, but I've reviewed the changes and I've ACKed them). With those ebuilds stable, we should be able to clean up quite a few of the old cruft we currently carry (if reluctant arches are willing to cooperate...) dev-cpp/cairomm-1.6.0 dev-cpp/gconfmm-2.22.0 dev-cpp/glibmm-2.16.4 dev-cpp/gnome-vfsmm-2.22.0 dev-cpp/gtkglextmm-1.2.0-r1 dev-cpp/gtkmm-2.12.7 dev-cpp/gtksourceviewmm-2.2.0 dev-cpp/libglademm-2.6.6 dev-cpp/libgnomecanvasmm-2.22.0 dev-cpp/libgnomemm-2.22.0 dev-cpp/libgnomeuimm-2.22.0 dev-cpp/libxmlpp-2.22.0 dev-libs/libsigc++-2.2.2
Created attachment 161432 [details] gnome-2.22.2-bump.list After cross checking leio's and my work, here is a hopefully complete list of things to stabilize for gnome 2.22
Created attachment 161433 [details] gnome-2.22.2-keyword.list and things that still need keywords on various arches.
hello arches, please find attached to this bug the list of packages to stabilize for gnome 2.22. Some packages might need keywording first for your arch too. Please also find the list of gnome-mm bindings to stabilize in comment #2
Created attachment 161478 [details] gnome-2.22.2-bump.list update of the bump list after tester's review.
To be added to the list are: dev-dotnet/mono-addins-0.3.0 (for tomboy) .. and don't forgot the dependant bugs on beagle and evolution-sharp amd64 is done
gnome-extra/nautilus-open-terminal-0.9 must be stabilized also, as current stable version (0.8) doesn't work with nautilus-2.22 Works ok for me under amd64. Thanks
You also need a newer mail-notification stable. mail-client/mail-notification-5.0 doesn't work with evolution-2.22*. 5.4 does, haven't tried anything in between.
Ok, ppc should be good to go but I am not going to remove the arch alias until some more of the depends bugs are shot.
Readding amd64
We can't stabilize mail-client/mail-notification because it depends on net-mail/fetchyahoo which the maintainer doesnt not which to stabilize, see bug #214301
Well do as graaff says, drop yahoo support and then stabilize, or fix 5.3.
I've used the gnome-2.22.2-keyword.list on x86 (I have gnome-light applets and evolution) and it compiled fine except a circular dependency (gnome-applets with the weather applet I think but I'm not 100% sure). For the moment it works like a charm.
(In reply to comment #14) > I've used the gnome-2.22.2-keyword.list on x86 (I have gnome-light applets and > evolution) and it compiled fine except a circular dependency (gnome-applets > with the weather applet I think but I'm not 100% sure). > > For the moment it works like a charm. > I'm sorry I meant gnome-2.22.2-bump.list
Any reason ppc64 is not on the arch list here but is listed as an arch in the attachments? I'd be happy to work on ppc64 if this simply an error.
mail-notification has been done on amd64
looks good so far on x86 (I'll mark it stable today/tomorrow). please note these minor things: x11-libs/gtksourceview-2.2.1: dodoc: TODO does not exist x11-terms/gnome-terminal-2.22.3: dodoc: TODO does not exist x11-libs/gtk+-2.12.10-r1: rm: cannot remove `/var/tmp/portage/x11-libs/gtk+-2.12.10-r1/image//etc/gtk-2.0/gtk.immodules': No such file or directory x11-libs/pango-1.20.5: rm: cannot remove `/var/tmp/portage/x11-libs/pango-1.20.5/image//etc/pango/pango.modules': No such file or directory
(In reply to comment #18) > looks good so far on x86 (I'll mark it stable today/tomorrow). Only half of the ebuilds is marked stable at the moment. Portage is in a pretty unconsistent state at the moment yielding unsolvable blockers and stuff.
(In reply to comment #19) > (In reply to comment #18) > > looks good so far on x86 (I'll mark it stable today/tomorrow). > > Only half of the ebuilds is marked stable at the moment. Portage is in a pretty > unconsistent state at the moment yielding unsolvable blockers and stuff. > I agree - in my install, gnome-settings-daemon is blocking gnome-control-center and I have not been able to resolve this.: [blocks B] <gnome-base/gnome-control-center-2.22 (is blocking gnome-base/gnome-settings-daemon-2.22.2.1) and: [ebuild R ] gnome-base/gnome-settings-daemon-2.22.2.1 USE="alsa -debug -esd -gstreamer" 0 kB how can something be blocking something that is already installed?
Sven, Paul, please read upgrade notes at http://www.gentoo.org/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml and be patient we our arch teams, thanks. If you have issues with gnome 2.22, please open a separate bug for them.
(In reply to comment #21) > Sven, Paul, please read upgrade notes at > http://www.gentoo.org/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml and > be patient we our arch teams, thanks. If you have issues with gnome 2.22, > please open a separate bug for them. I don't have any problem with gnome itself. The problem is, that gnome-settings-daemon-2.22 has gone stable while gnome-base/gnome-control-center-2.22 is not yet stable. So portage complains: "<gnome-base/gnome-control-center-2.22 (is blocking gnome-base/gnome-settings-daemon-2.22.2.1)" It seems, like the x86 maintainer committed to CVS after doing only half the job. It's been like that for hours now.
short term fix: echo "=gnome-base/gnome-control-center-2.22.2.1" >>/etc/portage/package.keywords actually solution would be of course to stabilize that package.
x86 should be done already, please report if not after you've synced in an hour or so
(In reply to comment #24) > x86 should be done already, please report if not after you've synced in an hour > or so gnome-extra/nautilus-cd-burner app-accessibility/gnome-speech gnome-base/gnome-volume-manager app-text/evince These are still missing on x86. I doublechecked by looking at http://viewcvs.gentoo.org
x86 stable (thanks armin76 =))
(In reply to comment #21) > Sven, Paul, please read upgrade notes at > http://www.gentoo.org/proj/en/desktop/gnome/howtos/gnome-2.22-upgrade.xml and > be patient we our arch teams, thanks. If you have issues with gnome 2.22, > please open a separate bug for them. A sync last night resulted in a successfull 2.22 build - thanks and apologize for being impatient...! Paul
alpha/ia64/sparc stable
If GNOME-2.22 is (going) stable, why is it still masked in profiles/base/package.mask which all 2008 profiles use?
Is this still broken? I just did an emerge --sync, and am still getting: [blocks B ] <gnome-base/gnome-control-center-2.22 (is blocking gnome-base/gnome-settings-daemon-2.22.2.1) The "fix" echo "=gnome-base/gnome-control-center-2.22.2.1" >>/etc/portage/package.keywords, doesn't change the result.
I think this should go in first: Index: gnome-settings-daemon-2.22.2.1.ebuild =================================================================== RCS file: /var/cvsroot/gentoo-x86/gnome-base/gnome-settings-daemon/gnome-settings-daemon-2.22.2.1.ebuild,v retrieving revision 1.8 diff -u -B -r1.8 gnome-settings-daemon-2.22.2.1.ebuild --- gnome-settings-daemon-2.22.2.1.ebuild 14 Aug 2008 00:35:50 -0000 1.8 +++ gnome-settings-daemon-2.22.2.1.ebuild 23 Aug 2008 04:12:42 -0000 @@ -37,7 +37,7 @@ >=media-libs/gstreamer-0.10.1.2 >=media-libs/gst-plugins-base-0.10.1.2 ) - !<gnome-base/gnome-control-center-2.22" + >=gnome-base/gnome-control-center-2.22" DEPEND="${RDEPEND} sys-devel/gettext >=dev-util/intltool-0.35.0
Or is there a reason for the blocker?
gnome-settings-daemon used to be shipped with gnome-control-center, but was split out for Gnome 2.22, hence the current blocker. g-s-d does not depend in anyway on g-c-c. It's actually the opposite :) Users should just remove the old gnome-control-center and carry on with the installation. Newer portages in ~arch should handle this blocker correctly without user intervention. Thanks
Obsoleted by bug #260063, see you there.
