On Thursday, 09.05.2013 at 01:08 -0700, John Gruenenfelder wrote: > 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.
Hmmm, strange. Don't know why you didn't get a notification of my
followup message ...
> 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?
OK, let's investigate :-)
Please send the output of the following:
dpkg -l |grep colordiff
which colordiff
whereis colordiff
env|grep PATH
grep 'my \$version' `which colordiff`
Also please send the content of /etc/colordiffrc and ~/.colordiffrc
That should all attempt to eliminate the possibility that some
non-distributed colordiff is interfering: the error you posted
originally sounded very much like a very old version of colordiff
was being called, because the wording of the error "Invalid colour
specification" has changed. Since colordiff 1.0.6/1.0.7 it has been
"Invalid colour specification for setting ..." rather than just "Invalid
colour specification ..."
Cheers,
Dave.
--
Dave Ewart [email protected], http://twitter.com/DaveEwart
All email from me is digitally signed, http://www.sungate.co.uk/
GPG key updated Jan 2013 see http://www.sungate.co.uk/gpg
Fingerprint: CF3A 93EF 01E6 16C5 AE7A 1D27 45E1 E473 378B B197
signature.asc
Description: Digital signature
