--- preliminary.list.old 2009-08-20 22:31:02.994266329 +0200 +++ preliminary.list 2009-08-20 22:30:46.861789557 +0200 @@ -12,8 +12,9 @@ dev-cpp/glibmm-2.20.1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 gnome-base/orbit-2.14.17 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 app-accessibility/gnome-speech-0.4.25 alpha amd64 hppa ia64 ppc ppc64 sparc x86 -gnome-base/gnome-menus-2.26.1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (is all the menu prefix ordeal done and stable?) -x11-libs/gtk+-2.16.5 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (this new version fine?) +gnome-base/gnome-menus-2.26.2 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (>=2.26.2 for location change, documented in migration guide and ebuild) +app-office/gnumeric-1.8.4-r2 alpha amd64 hppa ppc ppc64 sparc x86 (needed because of runtime fixes for gtk+-2.16.5) +x11-libs/gtk+-2.16.5 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 dev-python/gnome-python-base-2.26.1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 x11-themes/gtk-engines-2.18.2 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 dev-python/gnome-vfs-python-2.26.1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 @@ -31,10 +32,10 @@ dev-libs/libxml2-2.7.3-r2 alpha amd64 arm hppa m68k ia64 ppc ppc64 s390 sh sparc x86 (security bug 280617) -- x11-libs/cairo-1.8.8 (Check with cairo maintainers if to include) net-libs/libsoup-2.26.3-r1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (libsoup-gnome splitting is done later for newer webkit-gtk stabilization, until then we can do with a monolith [later splitting means migration though]) -x11-libs/libxklavier-3.9 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (chickening out on 4.0 in the first run...) +x11-libs/libxklavier-3.9 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (chickening out on 4.0 in the first run... eva: 4.0 is fine since everything got patched in order to work nicely with 3.x and 4.0) x11-libs/gtksourceview-2.6.2 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -x11-libs/pango-1.24.5 alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86 (this new version good to go?) --- media-libs/libcanberra-0.14 (skipping for now due to newer pulseaudio requirements and some weird ebuild changes) +x11-libs/pango-1.24.5 alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86 (this new version good to go? should be fine, no specific open bugs) +-- media-libs/libcanberra-0.14 (skipping for now due to newer pulseaudio requirements and some weird ebuild changes. eva: just changes related to a needed eautoreconf + removing useless schema installation stuff) net-libs/gtk-vnc-0.3.8-r1 -----------> arch teams slacking on #279511, make it a dependent bug dev-cpp/pangomm-2.24.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 dev-cpp/gtkmm-2.16.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 @@ -51,13 +52,13 @@ -- x11-libs/startup-notification-0.10 (problematic xcb stuff - no IUSE=xcb and therefore questionable benefits until USE=xcb is not default in profiles) x11-libs/libwnck-2.26.2-r2 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 x11-wm/metacity-2.26.0-r1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -gnome-base/gnome-session-2.26.2 alpha amd64 hppa ia64 ppc ppc64 sparc x86 (prefixed gnome-menus support) +gnome-base/gnome-session-2.26.2 alpha amd64 hppa ia64 ppc ppc64 sparc x86 (prefixed gnome-menus support. eva: not specific, simply re-installing the session file will get you the support for the new location) gnome-extra/yelp-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 x86 dev-python/libwnck-python-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 x11-misc/notification-daemon-0.4.0-r1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 dev-python/metacity-python-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 gnome-base/gnome-desktop-2.26.3 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -gnome-base/gnome-settings-daemon-2.26.1-r1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -- SHOWSTOPPER: >=pulseaudio-0.9.12 requirement! Do we arrange newer PA stable or drop the USE=pulseaudio on all GNOME-2.26 packages to be stabilized (keeping revisions having it in ~arch)? +gnome-base/gnome-settings-daemon-2.26.1-r1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -- SHOWSTOPPER: >=pulseaudio-0.9.12 requirement! Do we arrange newer PA stable or drop the USE=pulseaudio on all GNOME-2.26 packages to be stabilized (keeping revisions having it in ~arch)? eva: arranging newer (0.9.15ish) version stable will require less work for us. Plus pulseaudio-0.9.15 is a nice improvment over current stable. dev-python/gnome-desktop-python-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 x11-libs/vte-0.20.5 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 x11-terms/gnome-terminal-2.26.3.1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 @@ -68,8 +69,8 @@ gnome-extra/gnome-screensaver-2.26.1 alpha amd64 hppa ia64 ppc ppc64 sparc x86 gnome-base/libgnomeprint-2.18.6 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (arm/sh haven't done #260063 for earlier 2.18.5 either) app-crypt/seahorse-2.26.2 alpha amd64 hppa ia64 ppc ppc64 sparc x86 -gnome-base/gvfs-1.2.3 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -- SHOWSTOPPER: net-wireless/bluez migration missing -?? gnome-extra/gnome-power-manager-2.24.4-r2 -- SHOWSTOPPER: doesn't install HAL policy file anymore, and HAL is supposed to, but there is no stable HAL that does that (needs to be syncronized), plus there are no other 2.24.x versions in the tree anymore :( Are we just sticking to 2.22 or reintroducing a revision with policy file shipping? +gnome-base/gvfs-1.2.3 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -- SHOWSTOPPER: net-wireless/bluez migration missing. eva: hu ? not sure what you mean. +?? gnome-extra/gnome-power-manager-2.24.4-r2 -- SHOWSTOPPER: doesn't install HAL policy file anymore, and HAL is supposed to, but there is no stable HAL that does that (needs to be syncronized), plus there are no other 2.24.x versions in the tree anymore :( Are we just sticking to 2.22 or reintroducing a revision with policy file shipping? eva: is it an RDEPEND bug ? dev-python/pygobject-2.18.0 alpha amd64 arm hppa ia64 ppc ppc64 s390 sh sparc x86 (bug #277947, set as dependency) gnome-base/libgnomecanvas-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 gnome-extra/at-spi-1.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 @@ -95,11 +96,11 @@ app-arch/file-roller-2.26.3 alpha amd64 hppa ia64 ppc ppc64 sparc x86 app-editors/gedit-2.26.3 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 dev-python/gnome-media-python-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 -gnome-base/gnome-panel-2.26.3 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 +gnome-base/gnome-panel-2.26.3 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (needs networkmanager-0.7 too iirc) dev-python/libgnome-python-2.26.1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 dev-libs/totem-pl-parser-2.26.2 alpha amd64 arm ia64 ppc ppc64 sparc x86 gnome-extra/evolution-webcal-2.26.0 alpha amd64 hppa ia64 ppc ppc64 sparc x86 ---- gnome-base/gdm-2.20.10-r1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 <--- SHOWSTOPPER? Requires a newer pambase stable +--- gnome-base/gdm-2.20.10-r1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 <--- SHOWSTOPPER? Requires a newer pambase stable. eva: I should have asked stabilization of this months ago, it is high time it gets stable with the relevant pambase & possibly consolekit-0.3 gnome-extra/gnome-system-monitor-2.26.2 alpha amd64 hppa ia64 ppc ppc64 sparc x86 mail-client/evolution-2.26.2 alpha amd64 hppa ppc64 x86 gnome-extra/evolution-exchange-2.26.3 alpha amd64 hppa ppc64 x86 @@ -115,9 +116,9 @@ gnome-base/gnome-control-center-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 (needs gnome-media-2.26 stabled at the same time for sound preference pane move) x11-misc/alacarte-0.12.1 alpha amd64 hppa ia64 ppc ppc64 sparc x86 net-analyzer/gnome-netstatus-2.26.0 alpha amd64 arm hppa ia64 ppc ppc64 sparc x86 ---- dev-libs/libisofs-0.6.20-r1 c -- SHOWSTOPPER for alpha: no stable on alpha - needed for brasero-2.26[libburn]. media-optical could stabilize this newer version for everyone while at it. ---- dev-libs/libburn-0.6.8 alpha amd64 hppa ppc ppc64 x86 -- SHOWSTOPPER: Maintained by media-optical, >=0.6.0 not stable - needed for brasero-2.26 -app-cdr/brasero-2.26.3 alpha amd64 ia64 ppc ppc64 sparc x86 (fresh pull-in, make sure users don't end up with two nautilus extensions from nautilus-cd-burner - migration guide item already, can we do something at ebuild level?) -- SHOWSTOPPER: Needs >=dev-libs/libburn-0.6 stabilized by media-optical, and >=dev-libs/libisofs-0.6.12 stabled on alpha? +--- dev-libs/libisofs-0.6.20-r1 c -- SHOWSTOPPER for alpha: no stable on alpha - needed for brasero-2.26[libburn]. media-optical could stabilize this newer version for everyone while at it. eva: let's use.mask it and be done with it (with a proper bug report) +--- dev-libs/libburn-0.6.8 alpha amd64 hppa ppc ppc64 x86 -- SHOWSTOPPER: Maintained by media-optical, >=0.6.0 not stable - needed for brasero-2.26 eva: same as above +app-cdr/brasero-2.26.3 alpha amd64 ia64 ppc ppc64 sparc x86 (fresh pull-in, make sure users don't end up with two nautilus extensions from nautilus-cd-burner - migration guide item already, can we do something at ebuild level?) -- SHOWSTOPPER: Needs >=dev-libs/libburn-0.6 stabilized by media-optical, and >=dev-libs/libisofs-0.6.12 stabled on alpha? eva: can live with n-c-b just fine, no need to make them block each other even if that would force user into cleaning their system, python n-c-b bindings might still be in use for something else. dev-python/gnome-python-2.26.1 alpha amd64 arm hppa ia64 ppc ppc64 sh sparc x86 app-accessibility/gnome-mag-0.15.7 alpha amd64 hppa ia64 ppc ppc64 sparc x86 gnome-extra/deskbar-applet-2.26.2 alpha amd64 hppa ia64 ppc ppc64 sparc x86 @@ -157,6 +158,7 @@ net-analyzer/gnome-nettool/gnome-nettool-2.26.2.ebuild: x86-fbsd gnome-extra/yelp-2.26.0 <-- why -sparc +eva: because -sparc on xulrunner-1.9 at some point in time, probably sparc forgot to undo that Stabilize newer devtools - glade-3.6.x, check devhelp and gnome development guide, etc. We have time to do that later