Updates to 2.7.0 CE ??? (Solved)

jdeloach

I got message from Netgate that there are updates available to several pfSense packages, but in message it says these are for 2.7.0 CE.

My pfSense is still on 2.6.0 CE. Is it safe to install these updates on an 2.6.0 CE installation or should hold off till I upgrade to 2.7.0 CE

bmeeks

@jdeloach said in Updates to 2.7.0 CE ??? (Solved):

Is it safe to install these updates on an 2.6.0 CE installation

Absolutely not!

Installing packages compiled for a different pfSense version will likely bring over new shared library dependencies that will break your existing pfSense install. Of note with 2.7 CE is the move to PHP 8.x from 7.x. That is a huge change that absolutely will break your existing 2.6 CE installation if PHP is upgraded to 8.x by one of the 2.7 CE package updates.

Update pfSense BEFORE updating packages when a newer pfSense version is available.

SteveITS

@jdeloach What message and what package? If it was about patches, the System Patches package has patches for the version you’re using.

jdeloach

@SteveITS
Here is the email I received.

Notifications in this message: 1

9:02:02 An update to pfSense version 2.7.0.a.20230529.0600 is available

The following updates are available and can be installed using System > Package Manager:

apcupsd: 0.3.91_10 ==> 0.3.92_1
Cron: 0.3.8_1 ==> 0.3.8_3
nmap: 1.4.4_5 ==> 1.4.4_7
Notes: 0.2.9_3 ==> 0.2.9_5
pfBlockerNG-devel: 3.2.0_4 ==> 3.2.0_5
sudo: 0.3_7 ==> 0.3_8

Some how Netgate's notification system thought I was running pfSense 2.7.0 but I didn't install it because I knew it was wrong.

SteveITS

@jdeloach I’m unaware of a notification system. It wasn’t from a script on your firewall? I’ve seen that posted before. Is your update branch set to 2.7?

Dobby_

@jdeloach said in Updates to 2.7.0 CE ??? (Solved):

.....or should hold off till I upgrade to 2.7.0 CE

I would do so in any case! It makes no sense
to install packages for 2.7 on 2.6 because the
PHP code was on change and "something" as
I would be imagine about or from.

I’ve seen that posted before. Is your update branch set to 2.7?

I think this will be the problem here.