Here's a follow-up pass for GNOME 3.22 and other stuff. Basically stuff I've bumped after handing off 3.22 to stabilization and that are pure bug fixes that should be safe to stabilize relatively soon, but not immediately. Meanwhile please check over what else should be added here. I maintain the package list in a text file locally too, so it's ok to either comment for additions or edit the package list - I can diff and check over before CCing arches.
Adding libgdata-0.17.8 for important google calendar fixes, and potentially google task fixes. gnome-calendar and such might not work otherwise at all, so even if only just now added to tree, even weekend stabilization of that too should be good to restore functionality.
dev-libs/libmspack for better EWS support
please proceed with $package_list.
An automated check of this bug failed - the following atom is unknown: x11-themes/light-themes-17.04_p20161205-r1.ebuild Please verify the atom list.
An automated check of this bug failed - repoman reported dependency errors (7 lines truncated): > dependency.bad gnome-base/gvfs/gvfs-1.30.4.ebuild: DEPEND: ia64(default/linux/ia64/13.0) ['>=media-libs/libmtp-1.1.12'] > dependency.bad gnome-base/gvfs/gvfs-1.30.4.ebuild: RDEPEND: ia64(default/linux/ia64/13.0) ['>=media-libs/libmtp-1.1.12'] > dependency.bad gnome-base/gvfs/gvfs-1.30.4.ebuild: DEPEND: ia64(default/linux/ia64/13.0/desktop) ['>=media-libs/libmtp-1.1.12']
Stable on alpha.
Please consider this change in the package list, ebuild just added: --- x11-themes/light-themes-17.04_p20161205-r1 amd64 x86 +++ x11-themes/light-themes.17.04_p20170406 amd64 x86 https://github.com/gentoo/gentoo/commit/566112d7707e30d9f5c1ab462a3fc80505bd4f04
up to you if you feel it's important and safe to upgrade to stable
(In reply to Mart Raudsepp from comment #8) > up to you if you feel it's important and safe to upgrade to stable I'm afraid I cannot advise for or against either version. Please pick as you think fits best, either is fine with me.
Up to you, you are the primary on it; I just checked what was done in the -r1 and it looked OK and fixing some bug for some folks, so I included it just before you did the bump. So just decide yourself one of 1) Stabilize the -r1 with the cp -L stuff, thus keeping list as-is 2) Remove light-themes from the list to go straight to the new version later instead 3) Change it in package list to the new version
amd64 stable
Reducing list to what's left; adding x86 to libosinfo stuff as straight to stable (keywording is in bug 614170, but after confirming with ago, it should be fine to just request here as well for stabling, especially with amd64 already done)
x86 stable
Reducing list to what's left to do.
Reverting unauthorized package list change by non-maintainer. Stop messing with this, it is not OK and not allowed.
ppc stable
ppc64 stable
Stable for HPPA.
Reverting unauthorized package list edit AGAIN, and reducing list to what's left to do
arm stable
Updating libcroco to security fixed version from bug 618012 to not have to do that package twice by the already lagging arches left here.
updating gtk+ version from bug 618420
Everything's fine on ia64, including tests. Émeric
Stabilized on ia64, per testing by Émeric
sparc stable
Removing blocker, as there's only arm64 left here (and stablebot might not consider it properly as it's not a main arch right now)
Newer pango-1.40.6 for arm64 is now part of bug 624312 batch now (though still only pango for arm64 there, just one release newer now). Thus closing this bug as done.
