Open jameslamb opened 5 days ago
Ah, the conflict here is actually betwen xorg-xorgproto
and xorg-renderproto
. This makes sense because xorg-xorgproto
is a new upstream package that merges together all of the xorg-*proto
packages, except xcb-proto
.
The individual packages are no longer maintained, so we're in the process of migrating everything to use xorg-xorgproto
. This issue should be dealt with when xorg-libxrender
is updated to use xorg-xorgproto
, which is something that I plan to do in the very near future.
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 r-base44_and_m2w64-ucrt
migration which is propagating through the X.org stack right now, so basically there's already a migration for these happening. Also, FWIW the proto
packages just contain C header files and pkg-config files, and in most cases they're the same, so it's OK to have a little mix-and-match going on for a little while.
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 libxrender
and succeed.
I won't close this until @jakirkham has a chance to look though... I'm not sure about some of the questions from https://github.com/conda-forge/xorg-libxrender-feedstock/issues/11#issuecomment-2380240668 and what (if anything) needs to be done to use older packages.
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 https://github.com/rapidsai/cucim/pull/785#discussion_r1777636427.
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