pfSense 2.8.1 no packages updates - reason?
-
Hello Netgate Team,
I have pfSense 2.8.1 in use. Is there a certain reason why installed packages do not receive an update? I noticed that on the GitHub pages there are newer package versions, e.g.
Backup latest 0.6.3 but 0.6.4 available
Lightsquid latest 3.0.7_5 but 3.0.9 available
pfBlockerNG-devel latest 3.2.10 but 3.2.12_4 available
squid latest 0.5.3 but 0.5.8 available
WireGuard latest 0.2.9_5 but 0.2.11 available -
@ramup The 'available' package versions you note have not yet been merged into the Netgate-hosted CE (private) package repository.
-
Those newer versions are from main/2.9.0 which isn't public yet.
-
@stephenw10
Thanks for the statement. So this means pfSense 2.8.1 will not receive package updates for a year or two in repect of the release cycle? -
Not necessarily. It's just why you are seeing newer code and it's not in 2.8.1 yet. Things get tested in head first.
-
@ramup said in pfSense 2.8.1 no packages updates - reason?:
Hello Netgate Team,
I have pfSense 2.8.1 in use. Is there a certain reason why installed packages do not receive an update? I noticed that on the GitHub pages there are newer package versions, e.g.
Backup latest 0.6.3 but 0.6.4 available
Lightsquid latest 3.0.7_5 but 3.0.9 available
pfBlockerNG-devel latest 3.2.10 but 3.2.12_4 available
squid latest 0.5.3 but 0.5.8 available
WireGuard latest 0.2.9_5 but 0.2.11 availablePackage versions on GitHub don’t always match what’s available through the pfSense repo. Netgate usually holds back newer package releases until they’ve been tested specifically against the current pfSense branch. So even if upstream or GitHub shows a newer tag, it won’t appear in the GUI until it’s validated for 2.8.1.
