This problem has been resolved long ago on the city-fan repo trac page. Take a look at this: http://trac.city-fan.org/cfo-trac/ticket/2
Excerpt: you have to forcefully install (rpm -iv --replacefiles --replacepkgs --force) any available curl and libcurl from the official repos, uninstall the faulty city-fan based curl and libcurl rpms (rpm -e --nodeps), same goes to c-ares which bugs over IPv6, and suddenly you have a working yum. I spent around a week with this issue, and your thread has gave me the keywords that resulted in the above thread. Thanks a lot! 2014. január 15., szerda 9:09:58 UTC+1 időpontban Paul Boniol a következőt írta: > > In OpenSUSE, yast (GUI system config, update, etc.) has a parameter for > disabling IPv6. > > Under the hood it adds a line > net.ipv6.conf.all.disable_ipv6 = 1 > into a file in /etc/sysctl.d/ (99-sysctl.conf on my system). I think it > can be any file name that follows the general name format (and *likely > must be executable*). (See also How to Turn Off IPv6 at > https://wiki.debian.org/DebianIPv6). This method (though not the file > name) seems to be the way modern Linux systems are disabling IPv6. > > In previous versions, it has been a kernel parameter: ipv6.disable_ipv6=1 > I haven't tried that with this version, but an easy fix. > > Another that I have not tried but found when Googling for disabling IPv6 > was > sudo sh -c "echo 0 > /proc/sys/net/ipv6/conf/interface/disable_ipv6" > > Paul > > > On Tue, Jan 14, 2014 at 10:53 AM, Tilghman Lesher > <[email protected]<javascript:> > > wrote: > >> HE = Hurricane Electric. He's suggesting that you create a tunnel to >> a known IPv6 network, so that if you cannot get the resolver to do A >> lookups first, you just make IPv6 route. >> >> On Tue, Jan 14, 2014 at 10:35 AM, Howard White >> <[email protected]<javascript:>> >> wrote: >> > On 01/14/2014 10:24 AM, Blake Dunlap wrote: >> >> >> >> If you get desperate, you could always just fix the ipv6 transport >> >> temporarily, using a he tunnel. =) >> >> >> >> -Blake >> >> >> > >> > I am desperate and I do not understand your tunnel reference... >> > >> > :( >> > >> > Howard >> > >> > >> > -- >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "NLUG" group. >> > To post to this group, send email to [email protected]<javascript:> >> > To unsubscribe from this group, send email to >> > [email protected] <javascript:> >> > For more options, visit this group at >> > http://groups.google.com/group/nlug-talk?hl=en >> > >> > --- You received this message because you are subscribed to the Google >> > Groups "NLUG" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to [email protected] <javascript:>. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> -- >> Tilghman >> >> -- >> -- >> You received this message because you are subscribed to the Google Groups >> "NLUG" group. >> To post to this group, send email to [email protected]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/nlug-talk?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "NLUG" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
