Date: Thu, 08 Mar 2012 21:13:43 +0100 From: Hans Ottevanger <hans@beastielabs.net> To: portmgr-feedback@freebsd.org Cc: ports@freebsd.org, linimon@freebsd.org Subject: Re: FreeBSD unmaintained ports which are currently marked broken Message-ID: <4F5912F7.80302@beastielabs.net> In-Reply-To: <4F57748C.8090504@beastielabs.net> References: <201203070828.q278SXHH087611@portsmonj.FreeBSD.org> <4F57748C.8090504@beastielabs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/07/12 15:45, Hans Ottevanger wrote: > On 03/07/12 09:28, linimon@freebsd.org wrote: >> As part of an ongoing effort to reduce the number of problems in > [...] >> >> portname: x11/kdelibs3 >> broken because: does not compile >> build errors: none. >> overview: >> http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=kdelibs3 >> >> >> > > I have tried to rebuild kdelibs3 (using "make TRYBROKEN=yes") on > 8.3-PRERELEASE r232394 (both amd64 and i386 userland in a jail) and on > 10.0-CURRENT r232656 (amd64 only) on a recently portsnapped /usr/ports > and I cannot reproduce the build error mentioned in > > http://lists.freebsd.org/pipermail/cvs-ports/2012-March/237903.html > > All my builds finish without errors. > > Am I the only one seeing this? > > If kdelibs3 is actually broken, how could I reproduce the build error in > the commit message? > I see now that the brokenness has (silently) been limited to 7.x earlier today. Thanks. This saves some extra attention while rebuilding ports. Kind regards, Hans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F5912F7.80302>