Dropping the glesv2.pc file breaks builds of both mutter and mutter328. In the case of mutter, it's indirect (meson checks for glesv2), and in the case of mutter 328, it's a direct failure because of "BuildRequires: pkgconfig(glesv2)".
Speaking for sway-sig, we have the same problem with package wlroots (`BuildRequires: pkgconfig(glesv2)`). I went through the upstream git repository for mesa and could not find any change that would hint on upstream dropping this file; for now, it seems like build configuration error (although take this with a grain of salt, I don't have any experience with building it ;) ).
With the latest rawhide compose, repoclosure reports these packages with broken dependencies because of the dropped .pc file: glmark2-2017.07-2.20180717git0003eff.fc30.src gnome-session-3.32.0-1.fc30.src libepoxy-1.5.3-2.fc30.src libprojectM-3.1.1-0.5.rc4.gitf2e0a32.fc31.src libyami-utils-1.3.1-2.20180921git7e801b5.fc30.src mir-1.1.0-3.fc30.src mutter-devel-3.32.1-1.fc31.i686 mutter-devel-3.32.1-1.fc31.x86_64 mutter328-3.28.3-7.fc31.src qt5-qtbase-5.12.1-5.fc31.src qt5-qtwayland-5.12.1-1.fc31.src webkit2gtk3-2.24.1-1.fc31.src weston-6.0.0-1.fc30.src wlc-0.0.11-5.fc30.src wlroots-devel-0.5.0-2.fc31.i686 wlroots-devel-0.5.0-2.fc31.x86_64 Packages which only check for glesv2.pc in their build scripts and fail later are not counted here, obviously.
commit b01524fff05eef66e8cd24f1c5aacefed4209f03 Author: Eric Engestrom <eric.engestrom> Date: Tue Mar 5 11:46:38 2019 +0000 meson: don't build libGLES*.so with GLVND GLVND already provides these, so distro packagers have been deleting them all along. Let's save ourselves the trouble and not build them in the first place. Signed-off-by: Eric Engestrom <eric.engestrom> Reviewed-by: Matt Turner <mattst88> Reviewed-by: Dylan Baker <dylan> Reviewed-by: Emil Velikov <emil.velikov>
Does is mean it's now an enforced liability of libglvnd-gles package to provide that pkg-config file since it's taking up the responsibility of the actual provider, anyway?
(In reply to Jan Pokorný [poki] from comment #4) > Does is mean it's now an enforced liability of libglvnd-gles package to > provide that pkg-config file since it's taking up the responsibility of > the actual provider, anyway? Yes.
According to kwizart in bug#1709310, libglvnd does not at this time provide any headers and/or pkg-config files, and considers this a mesa error. Without pointing any more fingers, can we perhaps have this change reverted in Fedora for the time being (so the above builds un-break), and continue the discussion upstream? I would rather someone more knowledgeable about mesa reported it – I do not particularly enjoy playing at being an relay station ;-)
Clarification of previous comment: libglvnd does not provide any *gl* headers, nor does it provide pkg-config files for the gles API.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.