gtk+-3.22 update

[Princess Nell]

This is quite a mess. I haven't been able to figure it out. The least output about conflicts results when masking sound-juicer-3.22.1 and gtk-update-icon-cache > 3.20.9.

Code: Select all

Calculating dependencies... done!
[ebuild     U  ] net-wireless/gnome-bluetooth-3.20.1 [3.20.0]
[ebuild     U  ] gnome-extra/zenity-3.22.0 [3.20.0]
[ebuild     U  ] net-libs/glib-networking-2.50.0 [2.48.2]
[ebuild     U  ] net-libs/libsoup-2.56.0 [2.54.1-r1]
[ebuild     U  ] dev-libs/appstream-glib-0.6.8 [0.6.7]
[ebuild     U  ] gnome-extra/gnome-calculator-3.22.3 [3.20.2]
[ebuild     U  ] sys-apps/gnome-disk-utility-3.22.1 [3.20.2]
[ebuild     U  ] gnome-base/gvfs-1.30.3 [1.28.3-r1] USE="policykit%*" 

WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:

x11-libs/gtk+:3

  (x11-libs/gtk+-3.22.11:3/3::gentoo, ebuild scheduled for merge) conflicts with
    =x11-libs/gtk+-3.20*:3 required by (x11-themes/mate-themes-meta-3-r1:0/0::gentoo, installed)
    ^              ^^^^^  

Unmasking newer versions of mate-themes and mate-themes-meta doesn't seem to help either.

[ct85711]

Code: Select all

(
			=x11-libs/gtk+-3.22*:3
			=x11-themes/mate-themes-3.22${MATE_THEMES_V}:0/3.22
		)

From looking at the ebuilds you should be able to resolve that conflict with mate-themes-meta-3-r2, though may need to put both gtk+ and mate-themes-meta on the same compile line to help get portage to use the correct version... Now, if if you have gtk2-only USE flag set, then you can NOT have gtk+3.

[Princess Nell]

I removed the masks for soundjuicer and gtk-update-icon-cache and added both mate-themes-meta *and* mate-themes to package.accept_keywords, without versions. The result is

Code: Select all

# emerge -upDN world

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U  ] dev-util/gtk-update-icon-cache-3.22.2 [3.20.9]
[ebuild     U  ] x11-libs/gtk+-3.22.11 [3.20.9]
[blocks b      ] <x11-libs/gtk+-3.22:3 ("<x11-libs/gtk+-3.22:3" is blocking x11-themes/mate-themes-3.22.7)
[blocks b      ] <x11-libs/gtk+-3.22.2:3 ("<x11-libs/gtk+-3.22.2:3" is blocking dev-util/gtk-update-icon-cache-3.22.2)
[ebuild     U ~] x11-themes/mate-themes-3.22.7 [3.20.10]
[blocks b      ] >=x11-libs/gtk+-3.21:3 (">=x11-libs/gtk+-3.21:3" is blocking x11-themes/mate-themes-3.20.10)
[ebuild     U  ] media-sound/sound-juicer-3.22.1 [3.20.0]
# 

This works, and mate-themes-meta isn't even in the picture. Removing it from package.accept_keywords makes no difference now. So, in summary, all that was required was adding mate-themes to package.accept_keywords, and it was not very obvious. Thanks ct85711!

[Leio]

The needed mate-themes stuff is now stabled by the MATE team and you can probably remove all that accept_keywords stuff after next rsync. Sorry for the oversight during gtk3.22 stabling.
The new gtk-update-icon-cache stuff was an automatically resolved blocker (small b, not B) and should have worked without any issues as it was stabilized together with gtk+-3.22.

[Princess Nell]

Yep - removed all that I added and emerge -upDN world looks rather uneventful now. Thanks Leio!