On 09/26/2012 11:06 AM, Olivier Bilodeau wrote: ... > > I filed http://packetfence.org/bugs/view.php?id=1556 and I am having a > hard time to reproduce. > > We are bitten by this also in our build system. > > Yes, we require 1.36 because they changed their API in 3.x and we > haven't updated our code yet. > > Pinning a version *should* work so I wonder what is going on here.. >
Ok, we created a perl-Net-Appliance-Session with epoch 1 so that 1:1.36 will be better than 0:3.xx.. Please confirm that this fixes your issue. Can you try: yum clean all with all the proper repositories enabled. Then confirm that a `yum update` proceeds successfully. Thanks! More info here: http://packetfence.org/bugs/view.php?id=1556 -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
