Dave, Your message indicates that you are closing the bug due to lack of follow-up on my part. I did not receive any reply (other than the first BTS automated message). The problem still exists on my systems, but I am unsure what additional information would be useful to discover the cause of this issue.
My "home" laptop system primarily operates off Debian/unstable with a number of packages from Debian/experimental thrown in. A solid system that I use at work operates off Debian/testing. Both of these machines exhibit the same errors as described in the initial bug report. I have a third machine running Debian/stable, but due to some persistent network issues I cannot currently access it to see if this problem occurs there, too. I am perfectly willing to accept that through some fault of mine (local hacking, local misconfiguration, using experimental, etc.) something on my system could be causing colordiff to behave this way. That said, the other machine that exhibits this problem is used by several people and is in most respects a rather typical Debian installation. I do not do any development in Perl so I don't think there is anything special about my Perl environment on either machine that could cause colordiff to behave oddly. I don't even have any local CPAN modules. Is there any other information I can provide? -- --John Gruenenfelder Systems Manager, MKS Imaging Technology, LLC. Try Weasel Reader for PalmOS -- http://weaselreader.org "This is the most fun I've had without being drenched in the blood of my enemies!" --Sam of Sam & Max On Tue, May 07, 2013 at 05:09:18PM +0000, Debian Bug Tracking System wrote: >This is an automatic notification regarding your Bug report >which was filed against the colordiff package: > >#705255: colordiff: error messages ouput with default configuration > >It has been closed by Dave Ewart <[email protected]>. > >Their explanation is attached below along with your original report. >If this explanation is unsatisfactory and you have not received a >better one in a separate message then please contact Dave Ewart ><[email protected]> by >replying to this email. > > >Date: Tue, 7 May 2013 18:04:58 +0100 >From: Dave Ewart <[email protected]> >Subject: Closing bug, no follow-up from submitter, likely local issue >To: [email protected] >X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) >Message-ID: <20130507180458.426cfd5a@rockhopper> > >Closing this bug: no follow-up from the submitter: likely a serious >local issue in the colordiff setup for the submitter, but not a >colordiff bug. > >Date: Thu, 11 Apr 2013 20:45:58 -0700 >From: John Gruenenfelder <[email protected]> >Subject: colordiff: error messages ouput with default configuration >To: Debian Bug Tracking System <[email protected]> >Message-ID: <[email protected]> > >Package: colordiff >Version: 1.0.13-1 >Severity: normal > >Dear Maintainer, > >All of the output from colordiff begins with four error messages regardless of >what input I pass to it. For example, here is what I get when running >colordiff on my Mutt config: > >$ colordiff -U3 .muttrc.home .muttrc >Invalid colour specification (no) in /etc/colordiffrc >Invalid colour specification (diff) in /etc/colordiffrc >Invalid colour specification (off) in /etc/colordiffrc >Unknown option in /etc/colordiffrc: cvsstuff >--- .muttrc.home 2013-04-11 19:03:23.794554623 -0700 >+++ .muttrc 2013-04-11 19:19:22.108752374 -0700 > >This is immediately followed by the rest of the properly colorized diff >output. These errors/messages do not appear to have an effect on my usage. >I am submitting this bug report because these errors occur with the default >configuration as shipped with the colordiff Debian package. > >I first noticed this with version 1.0.10 but it persists with 1.0.13. I do >not have a ~/.colordiffrc file and there have been no changes to >/etc/colordiffrc. > >Users may find this particularly confusing since the default /etc/colordiffrc >file says in the comments that, among other values, "off" is a valid >color/alias. Actually, looking closer, it appears that colordiff complains >about every line in the file except for comments and the following three >lines: > >newtext=blue >oldtext=red >diffstuff=magenta > >I find it odd that there is no existing bug report, especially since this >problem seems to have existed since at least version 1.0.10. This would >suggest the problem is on my PC or with my configuration, but I haven't been >able to find anything. > > >-- System Information: >Debian Release: 7.0 > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable') >Architecture: amd64 (x86_64) >Foreign Architectures: i386 > >Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) >Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >Shell: /bin/sh linked to /bin/dash > >Versions of packages colordiff depends on: >ii perl 5.14.2-20 > >colordiff recommends no packages. > >colordiff suggests no packages. > >-- no debconf information
signature.asc
Description: Digital signature
