Bug #8932
closed
Upgrade to HaProxy 0.59_11 fails on 2.4.3
0%
Description
I cannot upgrade to haproxy 0.59_11 because getarraybyref() no longer exists:
Executing custom_php_install_command()...PHP ERROR: Type: 1, File: /usr/local/pkg/haproxy/haproxy.inc, Line: 2338, Message: Call to undefined function getarraybyref()pkg-static: POST-INSTALL script failed
Updated by Florian Apolloner over 5 years ago
Are you saying that packages are served from one repo only and will more or less immediately break if a new release of pfsense is out?
Updated by Jim Pingle over 5 years ago
No, each release has its own branch. It's possible that an edit intended to only stay on 2.4.4 was picked back to 2.4.3_1.
That said, now that 2.4.4 is out, 2.4.3-p1 is no longer officially supported, so your most likely path to resolution is to upgrade and then try it again.
Updated by Florian Apolloner over 5 years ago
Well it sounds as if https://github.com/pfsense/FreeBSD-ports/pull/555#discussion_r212271252 got into 2.4.3?
Updated by Pi Ba over 5 years ago
It seems like 2.4.3 is automatically pulling in the 2.4.4 repository files..?? Even though the 2.4.3 files still exist:
https://files00.netgate.com/pfSense_v2_4_3_amd64-pfSense_v2_4_3/All/pfSense-pkg-haproxy-0.59_9.txz
Not sure whats going wrong there, but it could be nice to offer 2.4.3 users to stay on 2.4.3 while they want/need it..
Updated by Jim Pingle over 5 years ago
It shouldn't be, they are on different branches (RELENG_2_4_3 vs RELENG_2_4_4), the commit may have been manually cherry-picked there.
Updated by Pi Ba over 5 years ago
I agree "it shouldnt be". But i'm seeing my 2.4.3 box offer to install haproxy 0.59_11 .. which at least isn't available in the 2_4_3 folder on the files00 server..
Updated by Florian Apolloner over 5 years ago
I can confirm that upgrading to 2.4.4 fixes it, as well as downgrading haproxy to 0.59_9 via: pkg add -f https://files00.netgate.com/pfSense_v2_4_3_amd64-pfSense_v2_4_3/All/pfSense-pkg-haproxy-0.59_9.txz
Updated by Jim Pingle over 5 years ago
Ah, I forgot that it automatically probes the "latest stable" repo which automatically points you to 2.4.4/RELENG_2_4_4 to obtain updates.
Aside from the "legacy" option for 2.3.x that's how it has always worked. If you're tracking stable updates it will pull from the latest branch on the line.
It's not built to let people stay outdated with packages.