Comment # 37
on bug 111077
from Matt Turner
(In reply to roland@rptd.ch from comment #36) > # mkdir -p /etc/portage/patches/media-libs/mesa/ > # cd /etc/portage/patches/media-libs/mesa/ > wget 'https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1852.patch' > --2019-09-11 18:35:51-- > 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.1s > > 2019-09-11 18:35:52 (113 KB/s) - ‘1852.patch’ saved [13646] > # ebuild /usr/portage/media-libs/mesa/mesa-19.0.8.ebuild prepare > * mesa-19.0.8.tar.xz BLAKE2B SHA512 size ;-) ... > [ ok ] > * checking ebuild checksums ;-) ... > [ ok ] > * checking miscfile checksums ;-) ... > [ ok ] > >>> Unpacking source... > >>> Unpacking mesa-19.0.8.tar.xz to /var/tmp/portage/media-libs/mesa-19.0.8/work > >>> Source unpacked in /var/tmp/portage/media-libs/mesa-19.0.8/work > >>> Preparing source in /var/tmp/portage/media-libs/mesa-19.0.8/work/mesa-19.0.8 ... > >>> Source prepared. > > I'm sorry but this procedure does not pick up the patch. Any ideas why this > could be the case? The directory /var/db/repos/gentoo/media-libs/mesa/ in > your version does not exist on my system. Huh. Very strange. :| (The /var/db/repos/gentoo path is the new path for ebuild repositories. It's exactly the same as /usr/portage on your system. It's a pretty recent change. See https://wiki.gentoo.org/wiki//var/db/repos/gentoo) Maybe just build and test from a git checkout, like you were doing in the git bisect. I'm not sure why portage isn't applying the patch :(
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
