Closed licamla closed 1 month ago
I don't think it's something I can fix. dev-python/pycparser-2.21::gentoo
is also being emerged unconditionally with every deep update. Could be a Portage bug.
My mistake, I lose the problem package name when post this issue.
I also thought it is a Portage bug at first. But I debug Portage and found that dev-python/pycparser-2.21
mark to rebuild when check dev-python/ply
.
so I mask =dev-python/ply-3.11-r200:python2/3.11::stefantalpalaru
,and the problem goes away.
I looked into it and I can't figure out how to avoid this unconditional rebuild, without giving up any functionality.
I test without dev-python/pycparser-2.20-r200
installed, 3 solutions found:
dev-python/ply-3.11-r0:python2/3.11
.(I guess in your environment you still need the next one, this need you to test. because it is effective for those who have not installed dev-python/pycparser-2.20-r200
, it is recommended to make this modification)dev-python/ply:0
to world also can avoid it in my environment.For me it is media-libs/lensfun-0.3.3-r1::stefantalpalaru that causes dev-python/pycparser-2.21-r1::gentoo to rebuild over and over again.
media-libs/lensfun-0.3.3-r1::stefantalpalaru that causes dev-python/pycparser-2.21-r1::gentoo to rebuild
How, if there is no dependency between them?
I was fooled by portage. It is not lensfun. And I can confirm masking =dev-python/ply-3.11-r200::stefantalpalaru helps even emerge does not want to update to that version because I have only python3_10 and python3_11 allowed. So as soon I disable the /::stefantalpalaru line in /etc/portage/package.mask/package.mask I am in the pycparser cycle on a world update until I mask =dev-python/ply-3.11-r200::stefantalpalaru.
dev-python/ply-3.11-r200:python2/3.11
causedev-python/pycparser-2.21
always need rebuild when update with--deep
python3 are now used by default. Maybe
dev-python/ply-3.11-r200:python2/3.11
is not not necessary.