Closed houseofsuns closed 8 years ago
Version of cython
?
cython-0.23.5 from the main tree.
You need to switch to the version in overlay.
Switching to the overlay version of cython solved the issue.
Is there a reason this isn't handled by the overlay, either through forced dependency on a specific cython version or USE flag, or simply masking dev-python::gentoo? I've manually done the latter for now, but it seems like something the overlay should handle.
In theory cython
from the overlay should mask the version from the main tree. I am guessing the issue is that you are ~arch to start with and you already had this particular version installed from the main tree.
Yes I probably should get a package.mask
, on the other hand I am expecting the people on ~arch to be a bit more pro-active when they break stuff in their install - it ain't arch.
I'm not ~arch in general, although there are a few specific packages I do keyword so I did look into my own setup first. However, until tonight, I had cython-0.23.4-r2
from sage-on-gentoo
installed. cython-0.23.5
was introduced to the gentoo
tree, keyworded ~arch, on 31st of March.
sage-on-gentoo
, in packages.keyword/sage
, lists
>=dev-python/cython-0.23.2-r1
and I'm pretty sure that's what caused my install to pull in cython-0.23.5
tonight. Wouldn't this unmask cython from any repo? Maybe this should be >=dev-python/cython-0.23.2-r1::gentoo
?
From my /etc/portage/
# pwd
/etc/portage
# grep -R cython .
./package.keywords/sage:>=dev-python/cython-0.23.2-r1
./package.use/sage:dev-python/cython -numpy
./package.mask/sage-temp:dev-python/cython::gentoo
Both package.keywords/sage
and package.use/sage
are symlinks to the sage-on-gentoo repo and package.mask/sage-temp
is my fix to mask cython from the gentoo
tree (so the sage-on-gentoo
version is pulled in). I can't see anything else which would keyword ~arch on cython in here.
OK. But why the main tree was installed instead of the overlay version is a bit of a mystery to me.
Main tree has a higher version number? 0.23.5 over 0.23.4-r2. I don't see anything that would make portage prefer the overlay version of cython if it has a lower version number.
That's because you should synchronize your overlay at the same time as the tree before running emerge -u
I had a matching 0.23.5 a few hours after the main tree - 18 days ago.
Oh, right, yeah, I'm an idiot, sorry. I assumed that my eix-sync had also pulled in overlay updates, but apparently it hadn't. Sorry for the confusion. Now to work out why eix-sync wasn't doing layman updates.
Not an idiot, that's a fair problem but out of my realm.
Maybe the overlay could simply stay one revision ahead of the main tree? That is bump to cython-0.23.5-r1 in the overlay. This will cause some rebuilds, but guarantee that at least my case would have been resolved automatically.
I try to avoid that. Also it would not have solved the problem of WPettersson since his sage-on-gentoo
overlay was not up to date.
On my hardened ~amd64 machine I see the following build error. I checked, that cysignals is installed with python2.7 enabled. Any ideas, what's wrong?