The following mask changes are necessary to proceed: (see "package.unmask" in the portage(5) man page for more details) # required by gnome-base/gnome-control-center-3.16.2::gnome # required by net-libs/gnome-online-accounts-3.16.3-r1::gentoo[gnome] # required by @selected # required by @world (argument) # /usr/portage/profiles/package.mask: # Pacho Ramos <pacho@gentoo.org> (24 Jun 2015) # Replaced by app-admin/system-config-printer, to migrate # simply run: # emerge -C system-config-printer-common system-config-printer-gnome # emerge -1 system-config-printer # Removal in a month (#553128). =app-admin/system-config-printer-gnome-1.4.3-r1 # required by app-admin/system-config-printer-gnome-1.4.3-r1::gentoo # required by gnome-base/gnome-control-center-3.16.2::gnome # required by net-libs/gnome-online-accounts-3.16.3-r1::gentoo[gnome] # required by @selected # required by @world (argument) # /usr/portage/profiles/package.mask: # Pacho Ramos <pacho@gentoo.org> (24 Jun 2015) # Replaced by app-admin/system-config-printer, to migrate # simply run: # emerge -C system-config-printer-common system-config-printer-gnome # emerge -1 system-config-printer # Removal in a month (#553128). =app-admin/system-config-printer-common-1.4.3
In summary, all old ebuilds should be cleaned from overlay to get the updated ones from main tree being used instead
Actually, you can use targeted mask to force portage into rebuilding packages still coming from the overlay on your system by using "*/*::gnome" in package.mask. This issue (for 3.16) is long fixed, I will probably get around cleaning up the overlay again after Gnome 3.22 bumps.
