Comment # 35
on bug 111077
from Matt Turner
(In reply to roland@rptd.ch from comment #34) > I do not see anything mentioned there. I've wget the file into > /etc/portage/patches/media-libs/mesa/ directory, which did not exist. > Anything else I need to do to get Gentoo to pick up the patch? p50-ethernet ~ # mkdir -p /etc/portage/patches/media-libs/mesa/ p50-ethernet ~ # cd /etc/portage/patches/media-libs/mesa/ p50-ethernet /etc/portage/patches/media-libs/mesa # wget 'https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1852.patch' --2019-09-10 17:09:04-- https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1852.patch Resolving gitlab.freedesktop.org... 35.185.111.185 Connecting to gitlab.freedesktop.org|35.185.111.185|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: ‘1852.patch’ 1852.patch [ <=> ] 13.33K --.-KB/s in 0.08s 2019-09-10 17:09:04 (163 KB/s) - ‘1852.patch’ saved [13646] p50-ethernet /etc/portage/patches/media-libs/mesa # ebuild /var/db/repos/gentoo/media-libs/mesa/mesa-19.2.0_rc2.ebuild prepare * mesa-19.2.0-rc2.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking mesa-19.2.0-rc2.tar.xz to /var/tmp/portage/media-libs/mesa-19.2.0_rc2/work >>> Source unpacked in /var/tmp/portage/media-libs/mesa-19.2.0_rc2/work >>> Preparing source in /var/tmp/portage/media-libs/mesa-19.2.0_rc2/work/mesa-19.2.0-rc2 ... * Applying 1852.patch ... [ ok ] * User patches applied. >>> Source prepared. "Applying 1852.patch" is what you should see. There's nothing else you need to do other than putting the patch into that directory.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
