On 09/24/2012 03:23 PM, Thomas Tsai wrote: > I’m upgrading from v3.5 to v3.5.1. when I perform “yum update > --enablerepo=PacketFence,rpmforge” on a EL6 system, the following > dependencies issues rise: > > --> Finished Dependency Resolution > > Error: Package: packetfence-3.5.1-1.el6.noarch (PacketFence) > > Requires: perl(Net::Appliance::Session) = 1.36 > > Removing: perl-Net-Appliance-Session-1.36-1.el6.rf.noarch > (@rpmforge) > > perl(Net::Appliance::Session) = 1.36 > > Updated By: perl-Net-Appliance-Session-3.122100-2.el6.noarch > (epel) > > perl(Net::Appliance::Session) = 3.122100 > > You could try using --skip-broken to work around the problem > > You could try running: rpm -Va --nofiles –nodigest > > I have rpmforge and epel repo’s enabled. > > > > Any suggestions? Looks like there was an rev update to Perl net > appliance while pf 3.5.1 still requires the older ver? Not sure what > the best tack is. >
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.. -- 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) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
