Hello Andi,

cd /usr/local/pf
wget https://github.com/inverse-inc/packetfence/commit/d9c88a93aa11348d33d350e0871a3880e21126f1.diff
patch -p1 --dry-run < d9c88a93aa11348d33d350e0871a3880e21126f1.diff
all is ok, there is no conflict ?
patch -p1 < d9c88a93aa11348d33d350e0871a3880e21126f1.diff

bin/pfcmd service httpd.portal restart



Regards
Fabrice

Le 2016-01-08 07:06, Morris, Andi a écrit :

Hi again,

I’ve found the bug and the fix on github. I’m not familiar with github at all though, can anyone please advise me how I can patch the files?

https://github.com/inverse-inc/packetfence/commit/d9c88a93aa11348d33d350e0871a3880e21126f1

Cheers,

Andi

*From:*Morris, Andi [mailto:amor...@cardiffmet.ac.uk]
*Sent:* 07 January 2016 16:07
*To:* packetfence-users@lists.sourceforge.net
*Subject:* Re: [PacketFence-users] 5.0.2 is out

Hi all,

Sorry to bump a very old thread, but I’m running version 5.0.1 and am in no position to upgrade my current production system at the moment. I’ve also just started utilising violations in anger, and have found that users clicking the Enable Network button do not get put back on the main network, which I presume is the “Fixed broken violation release process” patch mentioned below.

Am I able to get just that patch to apply to my system? I presume if I run the /usr/local/pf/addons/pf-maint.pl now I would end up getting lots of extra patches that I’ve not tested on my setup here.

Cheers,

Andi

*From:*Louis Munro [mailto:lmu...@inverse.ca]
*Sent:* 04 May 2015 17:06
*To:* packetfence-annou...@lists.sourceforge.net <mailto:packetfence-annou...@lists.sourceforge.net>; packetfence-users@lists.sourceforge.net <mailto:packetfence-users@lists.sourceforge.net>; packetfence-de...@lists.sourceforge.net <mailto:packetfence-de...@lists.sourceforge.net>
*Subject:* [PacketFence-devel] 5.0.2 is out

Hello list members,

We just released a minor update.
PF 5.0.2 is out.

This release is a bug fix only. No new features were introduced.

*Enhancements*

  * Added availables options (submit unknowns and update database) to
    the Fingerbank Settings page.
  * PacketFence will now leave clients.conf.inc empty if cluster mode
    is disabled.


*Bug Fixes*

  * PacketFence will longer unregister a device in pending state if
    the device is hitting the portal more than once while in "pending"
    state.
  * Fixed broken violation release process.
  * Fixed multiple lines returning from pfconfig.
  * Fixed undefined variables in portal template files.
  * Fixed provisioners OS detection with Fingerbank.


If you are already running 5.0.1 you may get the same code and fixes by running the /usr/local/pf/addons/pf-maint.pl script which will apply the same patches.

This release is merely a convenience for people upgrading from earlier releases or installing from scratch.


See https://github.com/inverse-inc/packetfence/blob/stable/NEWS.asciidoc for details

Best regards from Inverse,

--

Louis Munro
lmu...@inverse.ca <mailto:lmu...@inverse.ca> :: 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>)

------------------------------------------------------------------------


Cardiff Metropolitan University - 150 years of nurturing talent <http://www.cardiffmet.ac.uk/cardiffmet150>



------------------------------------------------------------------------------


_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to