After some help on the CentOS list, I may have found the problem:
perl-NetAddr-IP-4.044-1.el5.rf === I think that is the problem package
I don't know if that version is required by the repoforge packages ...
but base contains perl-NetAddr-IP-4.027-5.el5_6
I would see if I could
On 1/8/12 9:52 PM, email builder wrote:
rpm -e --nodeps perl-IO-Socket-INET6
By the way, is there a way to grep for the errant code? My
feeble attempt didn't turn up much:
as in one of my previous emails:
'locate IO-Socket-INET6'
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
On 1/9/12 6:25 AM, Michael Scheidell wrote:
On 1/8/12 9:52 PM, email builder wrote:
rpm -e --nodeps perl-IO-Socket-INET6
By the way, is there a way to grep for the errant code? My
feeble attempt didn't turn up much:
as in one of my previous emails:
'locate IO-Socket-INET6'
locate INET6
rpm -e --nodeps perl-IO-Socket-INET6
By the way, is there a way to grep for the errant code? My
feeble attempt didn't turn up much:
as in one of my previous emails:
'locate IO-Socket-INET6'
Sorry I missed that!
This gives only docs:
/usr/share/doc/perl-IO-Socket-INET6-2.51
used 'it' for YEARS in production, (commercial product,)
several
platforms, i386, amd64, FreeBSD versions 6.4-7.4.
ONE DAY, ONE BRAND NEW CLIENT was having real problems with their
mailq. email was backing up.
Two days to figure it out, I deleted the INET6 module (on freebsd,
On 1/7/12 1:56 PM, email builder wrote:
while I*DO* appreciate your suggestion, since I am fairly confident to say I
doubt that my config is the problem in a DNS resolver/IPv6 function
redefinition, I'm not too interested in proving that point by making those
changes on a production machine.
while I*DO* appreciate your suggestion, since I am fairly confident to say
I doubt that my config is the problem in a DNS resolver/IPv6 function
redefinition, I'm not too interested in proving that point by making
those
changes on a production machine. Again, thanks anyway.
I am
I am the ports maintainer for the FreeBSD version of SpamAssassin.
used 'it' for YEARS in production, (commercial product,) several
platforms, i386, amd64, FreeBSD versions 6.4-7.4.
ONE DAY, ONE BRAND NEW CLIENT was having real problems with their mailq.
email
was backing up.
Sure, but the point is that my spamassassin and per-Net-DNS (where the
error is happening?) are up to date from the CentOS repo so shouldn't
they work without an error when spamassassin restarts?
It isn't the job of the SA project to worry about specific distros and
repositories.
Wow, really? Then why wouldn't RedHat or CentOS have a fixed
updated
version in their repo? That seems egregious if what you say is
indeed the
case.
RedHat (and CentOS, since their whole mission is to match RHEL
feature-for-feature and bug-for-bug) believes that their Enterprise
On Sat, 7 Jan 2012 11:00:31 -0800 (PST), email builder wrote:
many packages as native CentOS as I can. I'm going to try to
figure out where to file a bug I guess, but I have a fear I'll get
rebuffed
without any help at all.
build perl rpms from cpan is imho safe and ok, but using cpan
And if you temporarily move all your config files and run the same command,
does the error go away?
Regards,
KAM
Does spamassassin -D --lint 21 | grep -i Resolver show the same
error?
Yes
Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated
version in their repo? That seems egregious if what you say is indeed the
case.
RedHat (and CentOS, since their whole mission is to match RHEL
feature-for-feature and bug-for-bug) believes that their Enterprise Linux
On 1/6/2012 3:31 PM, email builder wrote:
Sure, but the point is that my spamassassin and per-Net-DNS (where the
error is happening?) are up to date from the CentOS repo so
shouldn't they work without an error when spamassassin restarts?
It isn't the job of the SA project to worry about
On 2012-01-06 21:31, email builder wrote:
Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated
version in their repo? That seems egregious if what you say is indeed the
case.
RedHat (and CentOS, since their whole mission is to match RHEL
feature-for-feature and
Does spamassassin -D --lint 21 | grep -i Resolver show the
same error?
Yes
And if you temporarily move all your config files and run the same command,
does
the error go away?
Yikes, I'm reluctant to do this on a production machine. I have
only made config changes in local.cf
What is the Net::DNS version, are you pure ipv6 and are you
64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses
perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx.
If you're going to use rpmforge
What is the Net::DNS version, are you pure ipv6 and are you
64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses
perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx.
If you're going to use rpmforge
Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined
at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm
line 66 [ OK ] With my spamassassin, perl-Net-DNS and
per-IO-Socket-INET6 packages all
On 2012-01-05 21:28, email builder wrote:
What is the Net::DNS version, are you pure ipv6 and are you
64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses
perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is
/usr/lib/perl5/5.8.8/Exporter.pm line 65. at
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/Net/DNS/Resolver/Base.pm
line 66 [ OK ]
With my spamassassin, perl-Net-DNS and per-IO-Socket-INET6
packages all being from CentOS repo, I'm unsure why this would happen.
What
What is the Net::DNS version, are you pure ipv6
and are you
64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses
perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is
perl-Net-DNS-0.66-1.el5.rfx.
If you're
Wow, really? Then why wouldn't RedHat or CentOS have a fixed updated
version in their repo? That seems egregious if what you say is indeed the
case.
RedHat (and CentOS, since their whole mission is to match RHEL
feature-for-feature and bug-for-bug) believes that their Enterprise Linux
customers
What is the Net::DNS version, are you pure ipv6 and are you 64-bit?
Also, have you opened a bug with centos or redhat?
Try removing/commenting all your cf files especially anything dealing with ip's.
Other than that, I would likely update net dns with cpan at least temporarily
to see if it
On 04/01/12 07:35, email builder wrote:
Anyone have any other insights? Thanks!
I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that
package, besides being more up to date than the distro version also does
not require perl-IO-Socket-INET6. I suspect your version does not
On 04/01/12 15:30, Ned Slider wrote:
What does the following show:
rpm -q --requires perl-IO-Socket-INET6
Oops, I meant:
rpm -q --whatrequires perl-IO-Socket-INET6
On Wed, 04 Jan 2012 08:46:16 -0500, Kevin A. McGrail wrote:
What is the Net::DNS version, are you pure ipv6 and are you 64-bit?
in gentoo/funtoo its just perl-cleaner all
but it does not handle arch changes
Also, have you opened a bug with centos or redhat?
if more do this centos would
What is the Net::DNS version, are you pure ipv6 and are you 64-bit?
perl-Net-DNS-0.63-1.el5.rf
I don't use IPv6 that I know of (the errant package is installed whether
I like it or not as a dependency of spamassassin).
32 bit.
Also, have you opened a bug with centos or redhat?
I've
I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that
package,
besides being more up to date than the distro version also does not require
perl-IO-Socket-INET6. I suspect your version does not really require
perl-IO-Socket-INET6 either.
You may be right. It was
What does the following show:
rpm -q --requires perl-IO-Socket-INET6
Oops, I meant:
rpm -q --whatrequires perl-IO-Socket-INET6
no package requires perl-IO-Socket-INET6
Woa wait a minute! Then why this???
yum remove perl-IO-Socket-INET6
Loaded plugins: fastestmirror
Setting up
email builder wrote:
What does the following show:
rpm -q --requires perl-IO-Socket-INET6
Oops, I meant:
rpm -q --whatrequires perl-IO-Socket-INET6
no package requires perl-IO-Socket-INET6
Try rpm -q --whatrequires 'perl(IO::Socket::INET6)' - Perl dependencies
in RPM-land are
On 04/01/12 21:33, email builder wrote:
What is the Net::DNS version, are you pure ipv6 and are you 64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx.
If you're
On 04/01/12 21:41, email builder wrote:
I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that package,
besides being more up to date than the distro version also does not require
perl-IO-Socket-INET6. I suspect your version does not really require
perl-IO-Socket-INET6 either.
On 2012-01-04 23:22, Ned Slider wrote:
On 04/01/12 21:41, email builder wrote:
I have spamassassin-3.3.2-2.el5 installed from rpmforge on el5 - that
package,
besides being more up to date than the distro version also does not
require
perl-IO-Socket-INET6. I suspect your version does not
What does the following show:
rpm -q --requires perl-IO-Socket-INET6
Oops, I meant:
rpm -q --whatrequires perl-IO-Socket-INET6
no package requires perl-IO-Socket-INET6
Try rpm -q --whatrequires 'perl(IO::Socket::INET6)' - Perl dependencies
in RPM-land are rarely
What is the Net::DNS version, are you pure ipv6 and are you 64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx.
If you're going to use rpmforge packages, keep
What is the Net::DNS version, are you pure ipv6 and are you
64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses
perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx.
If you're going to use rpmforge
On 1/4/2012 8:41 PM, email builder wrote:
H... how did it get like that in the first place? (and how'd you
know to check perl-Net-DNS?)
The use of packages and extra repositories makes it very difficult to
really pinpoint the exact error but the errors you posted pointed more
to
On 05/01/12 01:28, email builder wrote:
What is the Net::DNS version, are you pure ipv6 and are you 64-bit?
perl-Net-DNS-0.63-1.el5.rf
You are in no man's land there - the distro uses perl-Net-DNS-0.59-3.el5
and the latest rpmforge package is perl-Net-DNS-0.66-1.el5.rfx.
If you're
Anyone have any other insights? Thanks!
Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum
I remember getting this error a while ago, and it was fixed (don't
remember how, but I think just by upgrading), but now it's
happening again:
Subroutine
Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum
I remember getting this error a while ago, and it was fixed (don't
remember how, but I think just by upgrading), but now it's
happening again:
Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at
On 12/31/11 10:46 PM, email builder wrote:
Hi,
Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum
I remember getting this error a while ago, and it was fixed (don't
remember how, but I think just by upgrading), but now it's
happening again:
Subroutine
Hi,
Running CentOS5 with SpamAssassin v3.3.1-2.el5 installed via yum
I remember getting this error a while ago, and it was fixed (don't
remember how, but I think just by upgrading), but now it's
happening again:
Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at
43 matches
Mail list logo
