You are not logged in.
error: failed to commit transaction (conflicting files)
libglvnd: /usr/include/EGL/egl.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/EGL/eglext.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/EGL/eglplatform.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GL/gl.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GL/glcorearb.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GL/glext.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GL/glx.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GL/glxext.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GLES2/gl2.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GLES2/gl2ext.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GLES2/gl2platform.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GLES3/gl3.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GLES3/gl31.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GLES3/gl32.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/GLES3/gl3platform.h exists in filesystem (owned by mesa)
libglvnd: /usr/include/KHR/khrplatform.h exists in filesystem (owned by mesa)
Errors occurred, no packages were upgraded.
experiences on pentium4/stable.
Offline
Every version of libglvnd seems to swallow more and more files from mesa..
Offline
Same issue here. Similar one was already mentioned here by levi, but I couldn't find a hint how to proceed/solve it.
Last edited by babubobu (2019-10-20 18:31:37)
Offline
I was able to upgrade on the 16th so I assume whatever issue I was reporting about there has been fixed. I'm just doing another update now which include a new version of mesa, and it seems to have installed the files just fine (currently it's rebuilding the linux modules as a post-install step).
I have mesa 19.2.1-2.0 now and libglvnd 1.2.0-3.0 and I'm running on intel graphics if that makes a difference.
Edit: mesa is from the testing repos also. That might well make a difference. libglvnd doesn't currently have a testing release mind you. Pushing mesa 19.2.1-2.0 to replace 19.2.0-2.2 in stable might well fix this it seems.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
I think it's a new bug of a similar kind. :-)
Because I'm pretty sure I fixed the old duplicate files (3 files or so).
Offline
Offline
Yes, that looks to me the same as the list of errors in the OP of this thread. I assume those ignored upgrades are something you configured this tool to do before running it.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Is it similar to this? ... so we're not allone
Offline
Mmh. So, do we push mesa to stable? Or just apply force? :-)
Offline
Force won't (necessary) help here: file conflicts are not tracked in our database. I lost track of what mesa/libglvnd combination works and which is broken - if the one in testing works, just push it to stable, then.
regards,
deep42thought
Offline
Yes, the one in testing currently works fine for me, no conflicts. I've just done a fresh update and while it didn't touch mesa or libglvnd, it went through smoothly. So there should be limted problems and certainly no file conflicts between it and libglvnd due to pushing mesa to stable.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Yes. this looks good. I pushed the versions from testing and nothing broke (so far).
Offline