Core 201 Testing Error

Installing & Running IPFire Testing
1

Hi,
I tried installing the latest test version on a test virtual machine, but I can’t update my machine, giving me an error.

upgrade
upgrade1277×704 123 KB

12:58:02 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
12:58:02 pakfire: TIME INFO: Time Server 195.32.70.195 has -0.000816 sec offset to localtime.
12:58:02 pakfire: DOWNLOAD ERROR: The downloaded file (pakfire2/2.29.1-x86_64/paks/core-upgrade-2.29-200.ipfire) wasn’t verified by IPFire.org. Sorry - Exiting…
12:58:00 pakfire: DOWNLOAD INFO: File received. Start checking signature…
12:58:00 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
12:55:49 pakfire: DOWNLOAD INFO: pakfire2/2.29.1-x86_64/paks/core-upgrade-2.29-200.ipfire has size of 124221330 bytes
12:55:48 pakfire: DOWNLOAD INFO: Host: mirror1.ipfire.org (HTTPS) - File: pakfire2/2.29.1-x86_64/paks/core-upgrade-2.29-200.ipfire
12:55:48 pakfire: MIRROR INFO: 1 servers found in list
12:55:48 pakfire: DOWNLOAD STARTED: paks/core-upgrade-2.29-200.ipfire
12:55:48 pakfire: CORE UPGR: Upgrading from release 199 to 201
12:55:48 pakfire: CORE INFO: core-list.db is 5 seconds old. - DEBUG: noforce
12:55:48 pakfire: CORE INFO: Checking for Core-Updates…
12:55:48 pakfire: PAKFIRE INFO: IPFire Pakfire 2.29.1-x86_64 started!
12:55:43 pakfire: PAKFIRE INFO: Pakfire has finished. Closing.
12:55:43 pakfire: DOWNLOAD FINISHED: pakfire2/2.29.1-x86_64/lists/core-list.db
12:55:43 pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
12:55:43 pakfire: DOWNLOAD INFO: File received. Start checking signature…
12:55:43 pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
12:55:42 pakfire: DOWNLOAD INFO: pakfire2/2.29.1-x86_64/lists/core-list.db has size of 903 bytes
12:55:42 pakfire: DOWNLOAD INFO: Host: mirror1.ipfire.org (HTTPS) - File: pakfire2/2.29.1-x86_64/lists/core-list.db
12:55:42 pakfire: MIRROR INFO: 1 servers found in list
12:55:42 pakfire: DOWNLOAD STARTED: lists/core-list.db
12:55:42 pakfire: CORE INFO: core-list.db is 13 seconds old. - DEBUG: force
12:55:42 pakfire: DOWNLOAD FINISHED: pakfire2/2.29.1-x86_64/lists/packages_list.db
2

It’s a problem with the time synchronization with the server.

3

My testing installation is set to the default of syncronise time daily.

Upgrade to CU201, via WUI, completed without problems. I have few addons, but libxxhash did also upgrade.

Reboot, via WUI, also went smoothly.

4

I would doubt that it is a time sync issue. The delta is 0.8 milliseconds.

In the code for checking the signature, if it fails it checks if it can access the time server. If it can access the server then it shows the message that was provided, showing the time info in case the delta is too high. If it is too high then the gpg --verify signature check will fail but a fraction of a millisecond will not cause that problem.

The file was successfully downloaded

so I think the most likely thing is that there was some corruption during that download that didn’t cause a break in the download itself, so it completed. However that corrupted download then failed the gpg --verify check of the file downloaded.

I would try the update again and see if it repeats or not.

1 Like
5

Hi,
I tried updating my test installation, and it worked without a hitch.

1 Like
6

Same here, no problems so far.