Project

General

Profile

Actions
Copy link

Bug #12898

closed

Update HAProxy Backend to Latest LTS

Added by Kris Phillips about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
haproxy
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
All

Description

The version of HAProxy in stable is very old and due to be unsupported at the end of the year. We should really move to the 2.4 branch for LTS support on the latest LTS.

This version is already in Freshports:
https://www.freshports.org/net/haproxy

Actions
Copy link
 #1

Updated by Viktor Gurov about 2 years ago

  • Assignee set to Viktor Gurov

HAProxy-devel is already 2.4 (2026-Q2 (LTS))

HAProxy-stable update to 2.2 version (2025-Q2 (LTS)):
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/655
https://gitlab.netgate.com/pfSense/FreeBSD-ports/-/merge_requests/194

Actions
Copy link
 #2

Updated by Kris Phillips about 2 years ago

Viktor Gurov wrote in #note-1:

HAProxy-devel is already 2.4 (2026-Q2 (LTS))

HAProxy-stable update to 2.2 version (2025-Q2 (LTS)):
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/655
https://gitlab.netgate.com/pfSense/FreeBSD-ports/-/merge_requests/194

Why are we moving to 2.2 for the stable release? 2.4 is the current LTS and 2.6 is set to be the next LTS in Q2 of this year. Even 2.2 is quite old at this point. I would say we should move the -devel branch to 2.6 to stay in line with the next LTS and move stable to the current LTS of 2.4.

Actions
Copy link
 #3

Updated by Viktor Gurov about 2 years ago

Kris Phillips wrote in #note-2:

Viktor Gurov wrote in #note-1:

HAProxy-devel is already 2.4 (2026-Q2 (LTS))

HAProxy-stable update to 2.2 version (2025-Q2 (LTS)):
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/655
https://gitlab.netgate.com/pfSense/FreeBSD-ports/-/merge_requests/194

Why are we moving to 2.2 for the stable release? 2.4 is the current LTS and 2.6 is set to be the next LTS in Q2 of this year. Even 2.2 is quite old at this point. I would say we should move the -devel branch to 2.6 to stay in line with the next LTS and move stable to the current LTS of 2.4.

The -devel branch means the development state only for the package, but not for the haproxy binary.
The current -devel branch uses haproxy 2.4.9, while non-devel can use 2.2.x.

Actions
Copy link
 #4

Updated by Jim Pingle about 2 years ago

  • Status changed from New to Pull Request Review

They are still putting out 2.2.x releases and it's a smaller and therefore safer jump. If that is OK then after a while we can always bump both up again to later versions.

Actions
Copy link
 #5

Updated by Viktor Gurov about 2 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by Danilo Zrenjanin about 2 years ago

  • Status changed from Feedback to Resolved

Installed HAproxy on the:

2.7.0-DEVELOPMENT (amd64)
built on Fri Mar 11 06:21:33 UTC 2022
FreeBSD 12.3-STABLE


[2.7.0-DEVELOPMENT][admin@pftest2.ipbgd.office]/root: pkg version | grep haproxy
haproxy22-2.2.19                   =
pfSense-pkg-haproxy-0.61_5         =

I am marking this ticket resolved.

Actions
Copy link

Also available in: Atom PDF