> On Apr 20, 2017, at 11:03 AM, C. <[email protected]> wrote:
>
> Hi there
>
> I had the bad idea of upgrading packetfence.
> BAD idea.
>
> The new pf 7.0.0 does not work at all, pf box is a brick now :-)))
> After manually updating mariadb, freeradius, haproxy and other packages do
> not update, nor pf.
> After adding testing repos for Jessie, updates get error on radius packages.
> Radius does not start, pf does not start.
>
> Guys, what have you done ?!?
> What version of Debian have you used for testing the product, before making
> it public ?!?
>
> OMG...
Dearest C.
How about providing logs, configuration and some details which might actually
help others?
And just to be clear, did you follow the instructions in
https://github.com/inverse-inc/packetfence/blob/devel/UPGRADE.asciidoc
<https://github.com/inverse-inc/packetfence/blob/devel/UPGRADE.asciidoc> ?
Especially those related to the Mariadb upgrade?
There was indeed an issue due to GPG signing of the libssl package.
That issue has now been resolved.
I just upgraded a system from 6.5.1 to 7.0.0.
Regards,
--
Louis Munro
[email protected] <mailto:[email protected]> :: www.inverse.ca
<http://www.inverse.ca/>
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu/>) and
PacketFence (www.packetfence.org <http://www.packetfence.org/>)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
