Skip to content
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

Open
licamla opened this issue May 17, 2022 · 7 comments

Comments

@licamla
Copy link

licamla commented May 17, 2022

dev-python/ply-3.11-r200:python2/3.11 cause dev-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.

@stefantalpalaru
Copy link
Owner

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.

@licamla
Copy link
Author

licamla commented May 18, 2022

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.

@licamla licamla changed the title 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 May 18, 2022
@stefantalpalaru
Copy link
Owner

I looked into it and I can't figure out how to avoid this unconditional rebuild, without giving up any functionality.

@licamla
Copy link
Author

licamla commented May 25, 2022

I test without dev-python/pycparser-2.20-r200 installed, 3 solutions found:

  • A smaller version number than the official one like 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)
  • Adding dev-python/ply:0 to world also can avoid it in my environment.
  • mask =dev-python/ply-3.11-r200:python2/3.11::stefantalpalaru (this shouldn't be what you need, but is best for me now)

@jospezial
Copy link

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.

@stefantalpalaru
Copy link
Owner

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?

@jospezial
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants