Hello, Sorry for not responding sooner, I didn't get the email from the BTS. Cut and paste from bugs.debian.org:
"This strongly suggests to me that you are using a locally compiled/installed version of Perl and not the one shipped as part of Debian (that would be in /usr/lib/perl and /usr/share/perl). With this in mind I am not sure I am going to be able to help you very much as the problem could just as easily be in the perl as in my request-tracker3.4 package. I recommend you run request-tracker3.4 (and all Debian perl packages for that matter) with the version of perl shipped with Debian and see if that fixes your problems. If nothing else this will provide an upgrade from the 5.8.2 version you are using to the 5.8.7 which comes with testing/etch. We do depend on a version of perl (>= 5.8.3) for a good reason, ignoring dependency lists is going to result in all sorts of trouble for you." History of the box is installed from stable CDroms, then upgraded to testing. The error is from liblog-dispatch-perl. Heres all my /var/log/dpkg.log lines for perl, liblog, and rt: 2005-08-09 13:33:43 install perl <none> 5.8.7-3 2005-09-06 15:20:08 install liblog-dispatch-perl <none> 2.10-1 2005-09-06 15:20:09 install request-tracker3.4 <none> 3.4.2-4 2005-10-02 08:37:22 upgrade request-tracker3.4 3.4.2-4 3.4.4-1 The box lives behind a firewall with no inward access only outbound thru a proxy/cache to port 80, so its unlikely it was rooted. Its a fresh "testing" box never used for development doesn't even have a compiler installed... Nothing in /opt etc. Which I agree makes a weird error message. I looked at: http://search.cpan.org/src/DROLSKY/Log-Dispatch-2.11/Changes And found: 2.10 Feb 11, 2004 - Fix a doc bug in Log::Dispatch::Syslog. It defaults to using a unix socket, not an inet socket. The problem in the past seemed to be RT was trying to connect via the unix socket thus I had to force it to the default inet socket, although upstream claims it was only a documentation change. Also the same version of liblog-dispatch-perl is in stable, testing, and unstable. Today I changed /etc/request-tracker3.4/RT_SiteConfig.pm back to @LogToSyslogConf = () unless (@LogToSyslogConf); restarted, and don't get the old error. However this was after I upgraded today per /var/log/dpkg.log 2005-10-02 08:37:22 upgrade request-tracker3.4 3.4.2-4 3.4.4-1 I guess file this as unreproducible.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
