+ echo -n 'Extracting packages-21.1-LibreSSL-amd64.tar...'
Extracting packages-21.1-LibreSSL-amd64.tar...+ rm -rf '/var/cache/opnsense-update/.sets.pending/packages-*'
+ mkdir -p /var/cache/opnsense-update/.sets.pending/packages-21.1
+ pkg-static clean -qya
pkg-static: Repository OPNsense has a wrong packagesite, need to re-create database
pkg-static: Repository OPNsense cannot be opened. 'pkg update' required
+ tar -C/var/cache/opnsense-update/.sets.pending/packages-21.1 -xpf /var/cache/opnsense-update/84841/packages-21.1-LibreSSL-amd64.tar
+ echo 21.1
It looks like that when OPNsense.conf URL changes the repository is "out of date" and some aux tools will not update but instead complain even if in -q mode.
This is a bit unfortunate, because we can't update from an upstream repo anymore so need to probably restore the upgrade config after successful upgrade, at least until we reboot again...
The same also goes for manipulating the config from OPNsense.conf on the command line.
It looks like that when OPNsense.conf URL changes the repository is "out of date" and some aux tools will not update but instead complain even if in -q mode.
This is a bit unfortunate, because we can't update from an upstream repo anymore so need to probably restore the upgrade config after successful upgrade, at least until we reboot again...
The same also goes for manipulating the config from OPNsense.conf on the command line.