file collision(s): /usr/include/X11/extensions/vldXvMC.h between two packages: x11-base/xorg-proto-2019.1 x11-libs/libXvMC-1.0.12 Reproducible: Always Steps to Reproduce: 1. emerge --sync 2. emerge -auvDN world Actual Results: x11-libs/libXvMC-1.0.12 failed to emerge with the message: >>> Installing (1 of 1) x11-libs/libXvMC-1.0.12::gentoo * checking 21 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/include/X11/extensions/vldXvMC.h * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-base/xorg-proto-2019.1:0::gentoo * /usr/include/X11/extensions/vldXvMC.h * * Package 'x11-libs/libXvMC-1.0.12' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. >>> Failed to install x11-libs/libXvMC-1.0.12, Log file: >>> Installing (1 of 1) x11-libs/libXvMC-1.0.12::gentoo * checking 21 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/include/X11/extensions/vldXvMC.h * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-base/xorg-proto-2019.1:0::gentoo * /usr/include/X11/extensions/vldXvMC.h * * Package 'x11-libs/libXvMC-1.0.12' NOT merged due to file collisions. * If necessary, refer to your elog messages for the whole content of the * above message. >>> Failed to install x11-libs/libXvMC-1.0.12, Log file: Expected Results: It should not fail
Created attachment 591006 [details] build.log
The two packages owning the file: # portageq owners / /usr/include/X11/extensions/vldXvMC.h x11-base/xorg-proto-2019.1 /usr/include/X11/extensions/vldXvMC.h x11-libs/libXvMC-1.0.12 /usr/include/X11/extensions/vldXvMC.h The two files from the two packages are identical: # diff /usr/include/X11/extensions/vldXvMC.h ./vldXvMC.h
i can confirm this issue
Commit https://gitlab.freedesktop.org/xorg/lib/libxvmc/commit/0fab90b409a3e4848603bdb6b438523038239f23 upstream. It is claimed that there will be no conflict with xorg-proto-2019.2. This should be reflected in ebuild.
*** Bug 695628 has been marked as a duplicate of this bug. ***
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9cb66262dff567c30bbbbb09a4002117bf549cad commit 9cb66262dff567c30bbbbb09a4002117bf549cad Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2019-09-25 20:57:31 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2019-09-25 20:57:54 +0000 x11-libs/libXvMC: Add blocker dep on x11-base/xorg-proto Closes: https://bugs.gentoo.org/695606 Signed-off-by: Matt Turner <mattst88@gentoo.org> x11-libs/libXvMC/libXvMC-1.0.12.ebuild | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
How is one supposed to upgrade their system when 2019.1 is the latest version of xorg-proto? I get the blocker and have no way forward: [nomerge ] x11-drivers/xf86-video-intel-2.99.917_p20190301::gentoo USE="dri sna udev uxa xvmc -debug -tools" [ebuild U ] x11-libs/libXvMC-1.0.12::gentoo [1.0.11::gentoo] USE="-static-libs" ABI_X86="32 (64) (-x32)" 0 KiB [blocks B ] <x11-base/xorg-proto-2019.2 ("<x11-base/xorg-proto-2019.2" is blocking x11-libs/libXvMC-1.0.12)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2e62bffae201000b823cf563fc1dee2e40e81199 commit 2e62bffae201000b823cf563fc1dee2e40e81199 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2019-09-26 12:35:02 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2019-09-26 12:39:11 +0000 profiles: [QA] Package mask x11-libs/libXvMC-1.0.12. The ebuild blocks against <x11-base/xorg-proto-2019.2, and at the same time depends on it (newest version in tree is xorg-proto-2019.1). Bug: https://bugs.gentoo.org/695606 Signed-off-by: Ulrich Müller <ulm@gentoo.org> profiles/package.mask | 4 ++++ 1 file changed, 4 insertions(+)
Will be unmasked when the new xorgproto release is in tree.
