Update from HAProxy Package 0.59_11 to 0.59_14 pulled HAProxy 1.8.14-52e4d43

[hostm]

Hello,

we are using pfsense with HAProxy package on a HA-pair for several years now, mostly without any issues.

About a hour ago I saw in the package manager that an update for the HAProxy package was available.

I did the update on the backup node.

Installed Version was: 0.59_11

Available Version: 0.59.14

Under Package Dependencies: haproxy17-1.7.11_1

But the update pulled the 1.8.14-52e4d43 version of HAProxy in. I tried to reinstall the package but the 1.8 stays.

Is it correct, that the 1.8 is now moving from haproxy-devel to haproxy?

I am unsure because of the dependency displayed.

Thanks in advance,
Daniel

[hostm]

I found a solution, but I want to share it for people with the same problem.

I could reproduce it by doing the update on the other machine and saving the logfile.

The following happens:

>>> Upgrading pfSense-pkg-haproxy... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 2 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	haproxy17: 1.7.11_1 [pfSense]

Installed packages to be UPGRADED:
	pfSense-pkg-haproxy: 0.59_11 -> 0.59_14 [pfSense]

Number of packages to be installed: 1
Number of packages to be upgraded: 1

The process will require 2 MiB more space.
650 KiB to be downloaded.
[1/2] Fetching pfSense-pkg-haproxy-0.59_14.txz: .......... done
[2/2] Fetching haproxy17-1.7.11_1.txz: .......... done
Checking integrity... done (1 conflicting)
  - haproxy17-1.7.11_1 [pfSense] conflicts with haproxy-1.7.11 [installed] on /usr/local/man/man1/haproxy.1.gz
Checking integrity... done (0 conflicting)
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 4 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	haproxy17: 1.7.11_1 [pfSense]

Installed packages to be UPGRADED:
	pfSense-pkg-haproxy: 0.59_11 -> 0.59_14 [pfSense]

Number of packages to be installed: 1
Number of packages to be upgraded: 1

The process will require 2 MiB more space.
Fetching haproxy-1.8.14.txz: .......... done
[1/4] Deinstalling haproxy-1.7.11...
[1/4] Deleting files for haproxy-1.7.11: ........ done
[2/4] Installing haproxy17-1.7.11_1...
[2/4] Extracting haproxy17-1.7.11_1: ........ done
[2/4] Installing haproxy-1.8.14...
pkg-static: haproxy-1.8.14 conflicts with haproxy17-1.7.11_1 (installs files into the same place).  Problematic file: /usr/local/man/man1/haproxy.1.gz ignored by forced mode
pkg-static: haproxy-1.8.14 conflicts with haproxy17-1.7.11_1 (installs files into the same place).  Problematic file: /usr/local/sbin/halog ignored by forced mode
pkg-static: haproxy-1.8.14 conflicts with haproxy17-1.7.11_1 (installs files into the same place).  Problematic file: /usr/local/sbin/haproxy ignored by forced mode
pkg-static: haproxy-1.8.14 conflicts with haproxy17-1.7.11_1 (installs files into the same place).  Problematic file: /usr/local/etc/rc.d/haproxy ignored by forced mode
[2/4] Extracting haproxy-1.8.14: ........ done
[3/4] Upgrading pfSense-pkg-haproxy from 0.59_11 to 0.59_14...
[3/4] Extracting pfSense-pkg-haproxy-0.59_14: .......... done
Removing haproxy components...
Menu items... done.
Services... done.
Loading package instructions...
Deinstall commands... done.
Syslog entries... done.
Saving updated package information...
overwrite!
Loading package configuration... done.
Configuring package components...
Loading package instructions...
Custom commands...
Executing custom_php_install_command()...done.
Menu items... done.
Services... done.
Writing configuration... done.
>>> Cleaning up cache... done.
Success

For any reason haproxy-1.8.14 is installed over the haproxy-1.7.11_1 including the binary.

Solution:

Per console I did:

pkg remove haproxy-1.8.14
pkg remove haproxy17-1.7.11_1
pkg install pfSense-pkg-haproxy-0.59_14

So only 1.7.11_1 was installed, the complete configuration remained untouched (although I took a backup before).

Regards,
Daniel