-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev-python/ply-3.11-r200:python2/3.11
cause dev-python/pycparser-2.21
always need rebuild when update with --deep
#102
Comments
I don't think it's something I can fix. |
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 |
3.11-r200:python2/3.11
cause dev-python/pycparser-2.21
always need rebuild when update with --deep
dev-python/ply-3.11-r200:python2/3.11
cause dev-python/pycparser-2.21
always need rebuild when update with --deep
I looked into it and I can't figure out how to avoid this unconditional rebuild, without giving up any functionality. |
I test without
|
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. |
How, if there is no dependency between them? |
I was fooled by portage. It is not lensfun. |
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.The text was updated successfully, but these errors were encountered: