Date: Fri, 13 Feb 2015 18:25:13 -0600 From: Adam Vande More <amvandemore@gmail.com> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Aliased Fonts in Xombrero Message-ID: <CA%2BtpaK122L=RXF%2B4ycN48AWtiih41krfVs-P25744D--kNnQfw@mail.gmail.com> In-Reply-To: <20150213205247.GI75183@itcom245.staff.itd.umich.edu> References: <20150213205247.GI75183@itcom245.staff.itd.umich.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 13, 2015 at 2:52 PM, William Bulley <web@umich.edu> wrote: > The bugzilla report shows exactly what I ran into. :-) > That is not in dispute. > What more (short of "piling on") should I provide? > If you don't know what information to provide, the most comprehensive method is to run the build in a typescript w/ MAKE_JOBS_UNSAFE set: cd /usr/ports/www/xombrero script xombrero.build make MAKE_JOBS_UNSAFE=1 And post/upload the relevant bits. Generally, +/- 20 lines from the FIRST error is what is needed to assess why the failure is occurring. Sometimes more info is needed like uname, freebsd-version, arch, port options, /etc/make.conf, other installed pkgs, how was make called, etc. Also, a "me too" isn't harmful especially if no one else has said it. A "me too" is probably also desired if some period of activity has passed eg *bump*. A bug report with all the sufficient information has a much better chance of being pursued than one where information needs to be teased out of the user. -- Adam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK122L=RXF%2B4ycN48AWtiih41krfVs-P25744D--kNnQfw>