search

ethus3h / compiz-reloaded-overlay

GNU General Public License v2.0
17 stars 8 forks source link

Got this problem under gentoo #4

Open HornedReaper opened 5 years ago

HornedReaper commented 5 years ago

[ebuild R ] x11-base/xorg-drivers-1.20 [ebuild N ] x11-drivers/xf86-input-synaptics-1.9.1 [ebuild N ] dev-python/sip-4.19.13 [ebuild N ] dev-python/cython-0.25.2 [ebuild R ] x11-libs/libXfont2-2.0.3-r1 [ebuild N ] x11-libs/compiz-bcop-0.8.16 [ebuild N ] dev-python/dbus-python-1.2.4 [ebuild R ] x11-drivers/xf86-video-amdgpu-18.1.0 [ebuild R ] x11-drivers/xf86-video-ati-18.1.0 [ebuild N ] x11-apps/mesa-progs-8.3.0 [ebuild N ] dev-qt/qtbluetooth-5.11.3 [ebuild N ] dev-python/PyQt5-5.10.1-r1 [ebuild R ] x11-libs/libwnck-2.31.0 [ebuild N ] x11-wm/compiz-0.8.16 [ebuild N ] x11-libs/libcompizconfig-0.8.16 [ebuild N ] x11-plugins/compiz-plugins-main-0.8.16 [ebuild N ] x11-plugins/compiz-plugins-meta-0.8.16 [ebuild N ] dev-python/compizconfig-python-0.8.16 [ebuild N ] x11-misc/ccsm-0.8.16 [ebuild N ] x11-wm/emerald-0.8.16 [ebuild N ] x11-themes/emerald-themes-0.8.16 [ebuild N ] x11-wm/compiz-9999 [ebuild N ] x11-libs/libcompizconfig-9999 [ebuild N ] dev-python/compizconfig-python-9999 [ebuild N ] x11-apps/fusion-icon-9999 [ebuild N ] x11-wm/compiz-meta-0.8.16

x11-wm/compiz:0

(x11-wm/compiz-9999:0/0::compiz-reloaded, ebuild scheduled for merge) pulled in by

=x11-wm/compiz-9999 required by (x11-apps/fusion-icon-9999:0/0::compiz-reloaded, ebuild scheduled for merge) ^^ ^^^^
=x11-wm/compiz-9999 required by (x11-libs/libcompizconfig-9999:0/0::compiz-reloaded, ebuild scheduled for merge) ^^ ^^^^

(x11-wm/compiz-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) pulled in by <x11-wm/compiz-0.9 required by (x11-libs/libcompizconfig-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) ^ ^^^
<x11-wm/compiz-0.9 required by (x11-plugins/compiz-plugins-main-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) ^ ^^^
<=x11-wm/compiz-0.9 required by (x11-wm/emerald-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) ^^ ^^^

dev-python/compizconfig-python:0

(dev-python/compizconfig-python-9999:0/0::compiz-reloaded, ebuild scheduled for merge) pulled in by

=dev-python/compizconfig-python-9999[python_targets_python2_7(-)?,python_targets_python3_4(-)?,python_targets_python3_5(-)?,python_targets_python3_6(-)?,-python_single_target_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_7(-),python_single_target_python2_7(+)?,python_single_target_python3_4(+)?,python_single_target_python3_5(+)?,python_single_target_python3_6(+)?] required by (x11-apps/fusion-icon-9999:0/0::compiz-reloaded, ebuild scheduled for merge) ^^ ^^^^

(dev-python/compizconfig-python-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) pulled in by <dev-python/compizconfig-python-0.9 required by (x11-misc/ccsm-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) ^ ^^^

x11-libs/libcompizconfig:0

(x11-libs/libcompizconfig-9999:0/0::compiz-reloaded, ebuild scheduled for merge) pulled in by

=x11-libs/libcompizconfig-9999 required by (dev-python/compizconfig-python-9999:0/0::compiz-reloaded, ebuild scheduled for merge) ^^ ^^^^

(x11-libs/libcompizconfig-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) pulled in by <x11-libs/libcompizconfig-0.9 required by (dev-python/compizconfig-python-0.8.16:0/0::compiz-reloaded, ebuild scheduled for merge) ^ ^^^

r7l commented 5 years ago

Not sure what you did but any kind of 9999 package should be masked. That's the case on my system.

ethus3h commented 5 years ago

Hi, sorry I haven't responded on this sooner. (I should remember to look at the issue tracker more...)

I've tried adding explicit KEYWORDS="" statements to all the -9999 ebuilds, in case they're being treated as non-masked because they leave KEYWORDS unset (they've been that way for a long time, though).

If that fixes it for you, presumably there's been a change or bug in Portage so that it no longer considers unset KEYWORDS as masked.

If it doesn't fix it, that's weird; are you sure you haven't manually accepted any -9999 versions in your accept_keywords file(s)?

Not really sure what to do beyond this; they should all be blocked by default. (In theory, nothing from this overlay should install without manually allowing ~arch packages, and the -9999s shouldn't work without manually allowing **.)