Date: Mon, 20 Jun 2022 19:42:19 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 264772] Colorize stopped coloring logs. Message-ID: <bug-264772-7788-1ljplMLEQ9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264772-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-264772-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264772 Matthew Kern <mkern@alconconstruction.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkern@alconconstruction.com --- Comment #2 from Matthew Kern <mkern@alconconstruction.com> --- I'm not OP, but I'm fairly certain this is in reference to sysutils/coloriz= e, as of 0.3.4_2. The new version cannot find /usr/local/etc/colorizerc as a valid configurat= ion file, so prints "Can't read any configuration!" and does not colorize anyth= ing. This is due to the new "patch-colorize" line "++@config_files =3D ("%%PREFIX%%/etc/colorizerc");". I'm not sure if the maintainer expected %%PREFIX%% to be replaced before applying the patch, but it is applying as-= is (that %%PREFIX%% is not expanding to anything). Temporary workaround is to copy your colorizerc to ~/.colorizerc for any us= er who is using the program, as it is still able to find and read this. Perman= ent fix will be to correct that patch and bump versions. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264772-7788-1ljplMLEQ9>