Hello OPNsense Community & Developers,
I am experiencing a persistent update loop with two minor upstream shared libraries: graphite2 (v1.3.14) and libdeflate (v1.25). The WebGUI firmware status page continually prompts that these updates are available. When the update is triggered, pkg successfully fetches and extracts the files, but immediately removes them during the automatic post-install cleanup phase. Consequently, the packages reappear as missing "New" (N/A) entries on the next update check.
Environment Details:
OPNsense Version: 26.1.10-amd64
OS: FreeBSD 14.3-RELEASE-p4
OpenSSL: 3.0.18
Plugins Active: Zenarmor (Home Subscription) using a Local Elasticsearch 8.11.3 reporting database instance, running alongside Java (openjdk17).
The Behavior / Update Log CLI Output:
When running the update via the root shell, the package manager successfully pulls the files, but then explicitly lists them under Installed packages to be REMOVED directly afterward:
Processing candidates (6 candidates): .... done
The following 2 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
graphite2: 1.3.14 [OPNsense]
libdeflate: 1.25 [OPNsense]
Number of packages to be installed: 2
181 KiB to be downloaded.
[1/2] Fetching libdeflate-1.25.pkg: ....... done
[2/2] Fetching graphite2-1.3.14.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/2] Installing graphite2-1.3.14...
[1/2] Extracting graphite2-1.3.14: .......... done
[2/2] Installing libdeflate-1.25...
[2/2] Extracting libdeflate-1.25: .......... done
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 2 packages:
Installed packages to be REMOVED:
graphite2: 1.3.14
libdeflate: 1.25
Number of packages to be removed: 2
[1/2] Deinstalling graphite2-1.3.14...
[1/2] Deleting files for graphite2-1.3.14: .......... done
[2/2] Deinstalling libdeflate-1.25...
[2/2] Deleting files for libdeflate-1.25: .......... done
Checking all packages: .......... done
The following package files will be deleted:
/var/cache/pkg/openjdk17-17.0.10+7.1_1.pkg
/var/cache/pkg/elasticsearch8-8.11.3~ff6f5709d3.pkg
/var/cache/pkg/libdeflate-1.25.pkg
/var/cache/pkg/graphite2-1.3.14.pkg
/var/cache/pkg/elasticsearch8-8.11.3.pkg
...
The cleanup will free 295 MiB
Deleting files: .......... done
Nothing to do.
Flushing temporary package files... done
***DONE***
Has anyone else utilizing local Elasticsearch deployments run into this package manager looping pattern? Is there an upcoming repository metadata sync planned to align the Java/Elasticsearch dependency tags with these specific library versions on the FreeBSD 14.3 base?
Thank you for your time and continued incredible work on the OPNsense ecosystem!