Date: Mon, 14 Oct 2019 15:28:33 -0700 From: John Kennedy <warlock@phouka.net> To: Jan Beich <jbeich@freebsd.org> Cc: freebsd-x11@freebsd.org Subject: Re: sway-1.2_1 crashes Message-ID: <20191014222833.GA13723@phouka1.phouka.net> In-Reply-To: <o8ym-7mul-wny@FreeBSD.org> References: <20191007165337.GA85696@phouka1.phouka.net> <wodg-9qj1-wny@FreeBSD.org> <20191007232340.GB85696@phouka1.phouka.net> <20191008172007.GA89365@phouka1.phouka.net> <d0f4-pju3-wny@FreeBSD.org> <20191011082409.2swof5muimfpwz5w@pamparam> <20191011174059.GE46984@phouka1.phouka.net> <o8ym-7mul-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 12, 2019 at 03:51:14AM +0200, Jan Beich wrote: > John Kennedy <warlock@phouka.net> writes: > > ... Jan's link eventually leads to this: > > > > https://github.com/freebsd/freebsd-ports/commit/a7c3fd3d428e > > That didn't land in the mainline. I've used a commit from Greg's repo[1] > (frequently rebased) to save time on testing. GitHub allows referencing > commits from any fork, so one has to pay attention to tags and branches > a commit exists in. Using the original repo instead of a fork allows to > reference a commit even if the fork is removed or renamed but if the > commit is orphaned for prolonged time it maybe garbage-collected. > > -- > [1] https://github.com/myfreeweb/freebsd-ports-dank/commits/lite > A lot of stuff have been submitted on bugzilla but not everything. Well, I knew it didn't end up in the mainline, I just couldn't figure out where it was. I learned a few more poudriere tricks, but I patched my local git ports tree with that patch. That certainly seems to fix the VT problem. Is there any reason it hasn't been pushed out? It made ~43 of my ports recompile, but it also seems like it's been out there a while. For all the compiling I do from ports, I haven't dug into that process.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191014222833.GA13723>