-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Clobbering errors: conflict between xorg-xorgproto and xorg-renderproto #11
Comments
Ah, the conflict here is actually betwen The individual packages are no longer maintained, so we're in the process of migrating everything to use |
Thanks James and Peter! 🙏 So how should we handle existing packages using the legacy libraries?
|
@jakirkham I've been migrating the proto packages as part of the |
Thanks very much @pkgw! It looks to me like merging #10 (and probably other PRs for other dependencies) has fixed the cases I'd reported here. The reproducible examples I'd reported here all now pull in the new build of I won't close this until @jakirkham has a chance to look though... I'm not sure about some of the questions from #11 (comment) and what (if anything) needs to be done to use older packages. |
Thanks Peter and James! 🙏 The original occurrence where we saw this issue appears to be resolved thanks to your migration efforts Happy to close or keep open (in case it is useful for tracking other such occurrences) |
Ok great, thanks! I'll close this... we all have enough open GitHub issues we're watching 😅 Anyone finding this from search can comment saying they hit the same issue and I'll re-open it. |
Solution to issue cannot be found in the documentation.
Issue
Installing the latest version of
xorg-libxrender
(0.9.11
) on a linux-64 system results in clobbering becausexorg-libx11
andxorg-renderproto
appear to both include the X11 headers.results in errors like the following:
Its two
xorg-*
direct dependencies can be installed individually, but not together, so they eventually lead to this conflict.Tried each of the following in a clean environment.
I discovered this in rapidsai/cucim#785 (comment).
Reporting it here because this feedstock introduces dependencies on these conflicting packages... but I only got here by first noticing this issue from
openslide
. Others might notice it if installingopenslide
orcairo
, given this graph of dependency relationships:Installed packages
Environment info
The text was updated successfully, but these errors were encountered: