Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 749303 - =media-libs/mesa-20.1.10 blocks upgrade from =media-libs/mesa-20.1.8
Summary: =media-libs/mesa-20.1.10 blocks upgrade from =media-libs/mesa-20.1.8
Status: RESOLVED DUPLICATE of bug 744715
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-15 14:54 UTC by tt_1
Modified: 2020-10-16 02:33 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
output from emerge -auvND world (mesa-blockage,8.93 KB, text/plain)
2020-10-15 14:54 UTC, tt_1
Details
output from emerge --info (emerge-info,7.91 KB, text/plain)
2020-10-15 14:55 UTC, tt_1
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tt_1 2020-10-15 14:54:20 UTC
Created attachment 665846 [details]
output from emerge -auvND world

I get this blocker when trying to upgrade to unstable mesa-20.1.10 on amd64:

[ebuild     U ~] media-libs/mesa-20.1.10::gentoo [20.1.8::gentoo] USE="X classic dri3 egl gallium gbm gles2 llvm lm-sensors osmesa vaapi vdpau vulkan zstd -d3d9 -debug -gles1 -opencl (-selinux) -test -unwind -valgrind -vulkan-overlay -wayland -xa -xvmc (-libglvnd%*)" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="radeonsi (-freedreno) -i915 -i965 -intel -iris (-lima) -nouveau (-panfrost) -r100 -r200 -r300 -r600 -radeon -vc4 -virgl (-vivante) -vmware" 0 KiB
[blocks B      ] <media-libs/mesa-20.2[-libglvnd(-)] ("<media-libs/mesa-20.2[-libglvnd(-)]" is blocking media-libs/libglvnd-1.3.2-r1)


=media-libs/mesa-20.1.9 is also affected, anything post mesa-20.2.0 is not affected

the full output of emerge is attached
Comment 1 tt_1 2020-10-15 14:55:10 UTC
Created attachment 665849 [details]
output from emerge --info
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2020-10-16 02:33:57 UTC

*** This bug has been marked as a duplicate of bug 744715 ***