>>> OK ... then it ought to move (probably) :)
>>
>> See my post on repoforge users list.
>> http://lists.repoforge.org/pipermail/users/2012-January/022634.html
>> There's no one to move the package but Dag.
>
> Per your suggestion, I filed a bug report on this, although
> that tracker
>> OK ... then it ought to move (probably) :)
>
> Se my post on repoforge users list.
> http://lists.repoforge.org/pipermail/users/2012-January/022634.html
> There's no one to move the package but Dag.
Per your suggestion, I filed a bug report on this, although
that tracker seems like a lo
Dne 11.1.2012 17:12, email builder napsal(a):
> I'm on a 32 bit machine, not sure if that makes a difference.
> What I do know is this:
>
>
>
> yum update
>
> ==
> Package Arch V
Dne 11.1.2012 17:22, Johnny Hughes napsal(a):
> OK ... then it ought to move (probably) :)
Se my post on repoforge users list.
http://lists.repoforge.org/pipermail/users/2012-January/022634.html
There's no one to move the package but Dag.
DH
___
Cen
On 01/11/2012 09:59 AM, Nicolas Thierry-Mieg wrote:
> Johnny Hughes wrote:
>> On 01/11/2012 08:42 AM, email builder wrote:
>>> And then there's the problem Nicolas is pointing out, which seems
>>> to be part of my problem. If such conflicting packages are supposed
>>> to be in rfx but are not.
>> And then there's the problem Nicolas is pointing out, which seems
>> to be part of my problem. If such conflicting packages are supposed
>> to be in rfx but are not. Maybe Daniel could move it, which
>> would definitely help my yum to stop complaining
>
> It is now part of R
Johnny Hughes wrote:
> On 01/11/2012 08:42 AM, email builder wrote:
>> And then there's the problem Nicolas is pointing out, which seems
>> to be part of my problem. If such conflicting packages are supposed
>> to be in rfx but are not.Maybe Daniel could move it, which
>> would definitely
On 01/11/2012 08:42 AM, email builder wrote:
Well, kind of. If you review this thread, you'll see that the the
fix
was to stop using the RepoForge package for perl-NetAddr-IP so that it
wasn't mixed with CentOS packages for perl-Net-DNS and
perl-IO-Socket-INET6. Maybe
> And then there's the problem Nicolas is pointing out, which seems
> to be part of my problem. If such conflicting packages are supposed
> to be in rfx but are not. Maybe Daniel could move it, which
> would definitely help my yum to stop complaining
David not Daniel. My apologies m
>>> Well, kind of. If you review this thread, you'll see that the the
>>> fix
>>> was to stop using the RepoForge package for perl-NetAddr-IP so that it
>>> wasn't mixed with CentOS packages for perl-Net-DNS and
>>> perl-IO-Socket-INET6. Maybe your position is that you won't fix
>>> perl-N
Johnny Hughes wrote:
> On 01/11/2012 04:42 AM, David Hrbáč wrote:
>> Dne 11.1.2012 1:13, email builder napsal(a):
>>> Well, kind of. If you review this thread, you'll see that the the fix
>>> was to stop using the RepoForge package for perl-NetAddr-IP so that it
>>> wasn't mixed with CentOS packag
On 01/11/2012 04:42 AM, David Hrbáč wrote:
> Dne 11.1.2012 1:13, email builder napsal(a):
>> Well, kind of. If you review this thread, you'll see that the the fix
>> was to stop using the RepoForge package for perl-NetAddr-IP so that it
>> wasn't mixed with CentOS packages for perl-Net-DNS and
>>
Dne 11.1.2012 1:13, email builder napsal(a):
> Well, kind of. If you review this thread, you'll see that the the fix
> was to stop using the RepoForge package for perl-NetAddr-IP so that it
> wasn't mixed with CentOS packages for perl-Net-DNS and
> perl-IO-Socket-INET6. Maybe your position is that
>> Why? Just remove that package and install the one from CentOS.
>> Spamassassin doesn't need to be touched.
>
> Seems to me that you are still using the mix of repos. Packages from RF
> work fine.
Well, kind of. If you review this thread, you'll see that the the fix was to
stop using the R
Dne 10.1.2012 4:02, email builder napsal(a):
> Why? Just remove that package and install the one from CentOS.
> Spamassassin doesn't need to be touched.
Hello,
Seems to me that you are still using the mix of repos. Packages from RF
work fine.
root@specs2:1280:279:/$ rpm -q spamassassin perl-IO-S
>> I have three e-mail servers and the error is on all three.
>>
>> [root@MailIn ~]# service spamassassin restart
>> Stopping spamd: [ OK ]
>> Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at
> /usr/lib/perl5/5.8.8/Export
Gregory P. Ennis wrote:
>
> I have three e-mail servers and the error is on all three.
>
> [root@MailIn ~]# service spamassassin restart
> Stopping spamd:[ OK ]
> Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at
> /usr/lib/per
Gregory P. Ennis wrote:
>
> I have three e-mail servers and the error is on all three.
>
> [root@MailIn ~]# service spamassassin restart
> Stopping spamd:[ OK ]
> Starting spamd: Subroutine Net::DNS::Resolver::Base::AF_INET6 redefined at
> /usr/lib/per
\
>> Is there somewhere at RepoForge I could notify them about this?
>
> users mailing list:
> us...@lists.repoforge.org
> http://lists.repoforge.org/mailman/listinfo/users
Thank you. I am reporting it now
___
CentOS mailing list
CentOS@centos.org
h
>> Is there somewhere at RepoForge I could notify them about this?
>
> users mailing list:
> us...@lists.repoforge.org
> http://lists.repoforge.org/mailman/listinfo/users
Thank you. I am reporting it now
___
CentOS mailing list
CentOS@centos.org
ht
On 01/09/2012 09:56 PM, email builder wrote:
> Is there somewhere at RepoForge I could notify them about this?
users mailing list:
us...@lists.repoforge.org
http://lists.repoforge.org/mailman/listinfo/users
--
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe
Google is the M
>> So maybe I *do* need to open a bug report? Where do I do
>> that?
>
> can you try to disable ipv6, then reboot and see if you still
> get the
> error message?
Sorry, it's a production machine, I'd rather not do that.
I can
make small
On 01/08/2012 08:40 PM, email builder wrote:
>
> So maybe I *do* need to open a bug report? Where do I do that?
can you try to disable ipv6, then reboot and see if you still get the
error message?
>>> Sorry, it's a production machine, I'd rather not do that. I can
>>> make sm
Johnny Hughes wrote:
> On 01/07/2012 12:50 PM, email builder wrote:
> I don't know what is causing your specific issue ... whether you
> are
> getting something newer in sa-update than is designed to work with
> CentOS (sa-update bypasses the normal rpm type updates and does u
So maybe I *do* need to open a bug report? Where do I do that?
>>>
>>> can you try to disable ipv6, then reboot and see if you still get the
>>> error message?
>>
>> Sorry, it's a production machine, I'd rather not do that. I can
>> make small
>> changes but a reboot-- Beside, if
On 01/07/2012 12:50 PM, email builder wrote:
I don't know what is causing your specific issue ... whether you
are
getting something newer in sa-update than is designed to work with
CentOS (sa-update bypasses the normal rpm type updates and does updates
from elsewhere).
>>> I don't know what is causing your specific issue ... whether you
>>> are
>>> getting something newer in sa-update than is designed to work with
>>> CentOS (sa-update bypasses the normal rpm type updates and does updates
>>> from elsewhere). It should only update rules, so maybe some of t
Le 06/01/2012 21:06, email builder wrote :
>> I don't know what is causing your specific issue ... whether you are
>> getting something newer in sa-update than is designed to work with
>> CentOS (sa-update bypasses the normal rpm type updates and does updates
>> from elsewhere). It should only u
>>> But before I try that, I'm wondering, shouldn't it be easy
>>> from the error message to simply understand what package
>>> is creating the problem?
>>>
>>> It turns out it's not sa-update specifically doing this, but the
>>> restart of spamassassin itself:
>>>
>>> /etc/init.d/spamassa
On 01/06/2012 09:36 AM, Johnny Hughes wrote:
> On 01/05/2012 10:17 PM, email builder wrote:
> Hmm, OK, prioritze CentOS repo over RepoForge then will yum update
> figure out the rest? I don't see any priority settings in my yum
>>> conf
> files...
# yum list | grep priori
On 01/05/2012 10:17 PM, email builder wrote:
Hmm, OK, prioritze CentOS repo over RepoForge then will yum update
figure out the rest? I don't see any priority settings in my yum
>> conf
files...
>>> # yum list | grep priorities
>>> yum-priorities.noarch
>>> Hmm, OK, prioritze CentOS repo over RepoForge then will yum update
>
>>> figure out the rest? I don't see any priority settings in my yum
> conf
>>> files...
>>
>> # yum list | grep priorities
>> yum-priorities.noarch 1.1.16-16.el5.centos
> installed
>
>> Hmm, OK, prioritze CentOS repo over RepoForge then will yum update
>> figure out the rest? I don't see any priority settings in my yum conf
>> files...
>
> # yum list | grep priorities
> yum-priorities.noarch 1.1.16-16.el5.centos
> installed
>
> # cat /etc/yu
From: email builder
> Hmm, OK, prioritze CentOS repo over RepoForge then will yum update
> figure out the rest? I don't see any priority settings in my yum conf
> files...
# yum list | grep priorities
yum-priorities.noarch 1.1.16-16.el5.centos installed
# cat /etc/
>> The only hints I can find seem to suggest to remove
>> perl-IO-Socket-INET6, but trying to do so using yum (I
> don't
>> want to start using another method of package
> management)
>> tells me that spamassassin is a dependency and will also
> be
>> rem
On 01/04/2012 10:29 PM, email builder wrote:
>The only hints I can find seem to suggest to remove
>
>perl-IO-Socket-INET6, but trying to do so using yum (I don't
>want to start using another method of package management)
>tells me that spamassassin is a dependency an
The only hints I can find seem to suggest to remove
perl-IO-Socket-INET6, but trying to do so using yum (I don't
want to start using another method of package management)
tells me that spamassassin is a dependency and will also be
removed - obviously undesirable.
>>> On my Zimbra server (CentOS 5.7), sa works fine.
>
>>> I have spamassassin-3.3.1-2.el5 and
>>> perl-IO-Socket-INET6-2.51-2.fc6 installed.
>> Same here. Are you running sa-update? SpamAssassin works
>> fine for me, but sa-update is giving this error every time it runs.
>
> Yes, it
On 01/04/2012 01:33 AM, email builder wrote:
> John, THANK YOU very much for responding --
>
>
>
>>> The only hints I can find seem to suggest to remove
>>> perl-IO-Socket-INET6, but trying to do so using yum (I don't
>>> want to start using another method of package management)
>>> tells me th
>> On my Zimbra server (CentOS 5.7), sa works fine.
>> I have spamassassin-3.3.1-2.el5 and
>> perl-IO-Socket-INET6-2.51-2.fc6 installed.
> Same here. Are you running sa-update? SpamAssassin works
> fine for me, but sa-update is giving this error every time it runs.
Yes, it seems to run fine
John, THANK YOU very much for responding --
>> The only hints I can find seem to suggest to remove
>> perl-IO-Socket-INET6, but trying to do so using yum (I don't
>> want to start using another method of package management)
>> tells me that spamassassin is a dependency and will also be
>> r
From: email builder
> The only hints I can find seem to suggest to remove
> perl-IO-Socket-INET6, but trying to do so using yum (I don't
> want to start using another method of package management)
> tells me that spamassassin is a dependency and will also be
> removed - obviously undesirable.
If
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, but
now it's happening again:
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.
43 matches
Mail list logo
