Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39241 - [nvidia-libgl][mesa-libgl][mesa] wrong 'libegl'/'libgles' replace/provides/conficts
Attached to Project:
Arch Linux
Opened by Gustavo Alvarez (sl1pkn07) - Saturday, 08 March 2014, 21:12 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 09 March 2014, 13:20 GMT
Opened by Gustavo Alvarez (sl1pkn07) - Saturday, 08 March 2014, 21:12 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 09 March 2014, 13:20 GMT
|
Details'libegl' and 'libgles' provides/replaces/conficts is stored in wrong package (mesa).
i think is better if stored in nvidia-libgl/mesa-libgl, like a 'libgl' provides/conflicts/replaces because libgles/libegl libs (symlinks to work) is now provide by these packages instead mesa greetings |
This task depends upon
nevermind (for the moment)
greetings
There just doesn't seem to be any real impact though.
package_mesa() {
[...]
provides=('libglapi' 'osmesa' 'libgbm' 'libgles' 'libegl' 'khrplatform-devel')
conflicts=('libglapi' 'osmesa' 'libgbm' 'libgles' 'libegl' 'khrplatform-devel')
replaces=('libglapi' 'osmesa' 'libgbm' 'libgles' 'libegl' 'khrplatform-devel')
We need them for the upgrade from previous mesa packages where it was splitted
Do we have a timeline policy for moving on from older configurations?