Date: Sun, 2 Apr 2017 11:52:24 +0200 From: Mathieu Arnold <mat@mat.cc> To: Jan Beich <jbeich@FreeBSD.org>, Antoine Brodin <antoine@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r437156 - in head/textproc/libxml++26: . files Message-ID: <363133c4-c26b-0300-4bfe-3e3464caaf50@mat.cc> In-Reply-To: <1stb-9mzr-wny@FreeBSD.org> References: <201703282018.v2SKIhbZ065761@repo.freebsd.org> <1stb-9mzr-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 02/04/2017 =C3=A0 11:28, Jan Beich a =C3=A9crit : > Antoine Brodin <antoine@FreeBSD.org> writes: > >> Author: antoine >> Date: Tue Mar 28 20:18:42 2017 >> New Revision: 437156 >> URL: https://svnweb.freebsd.org/changeset/ports/437156 >> >> Log: >> Revert r437110, this upgrade breaks lots of ports depending on it >> =20 >> With hat: portmgr > When backing out a commit make sure to re-open the referenced bug and > either quote or provide links to the build logs. That way the submitter > can try to fix bustage then re-land the patch. It'd also help to avoid > duplicate bugs opened only to bump into the same issue. I'm sorry, but no. Portmgr is already spread thin because of everyone breaking everything all the time. When we back things out, we restore the ports tree to whatever state it was before, we do not have the time to go and have a look at what other things should be changed, or to fix things. --=20 Mathieu Arnold
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?363133c4-c26b-0300-4bfe-3e3464caaf50>