I’ve tried doing this using the UI and command line but the result is the same (here are the command line logs):
[root@ipfire2 ~]# pakfire status Core-Update 2.27-x86_64 Release: 164 -> 166 Update: wio Version: 1.3.2 -> 1.3.2 Release: 13 -> 14 Update: speedtest-cli Version: 2.1.3 -> 2.1.3 Release: 4 -> 5 Core-Version: 2.27-x86_64 Core-Update-Level: 164 Last update: 25d 18h 26m 25s ago Last core-list update: 21m 31s ago Last server-list update: 21m 36s ago Last packages-list update: 21m 33s ago Core-Update available: yes (166) Package-Updates available: 2 Reboot required: no [root@ipfire2 ~]# pakfire upgrade CORE UPGR: Upgrading from release 164 to 166 Giving up: There was no chance to get the file "meta/meta-core-upgrade-165" from any available server. There was an error on the way. Please fix it. No filename given in meta-file.
The box definitely has Internet access (I’m connecting to it using an internal OpenVPN connection) so it’s possible that the update location DB is not in a good state.
I’d appreciate pointers on how to fix this.