Messages

Thanks @franco for clarification regarding the loop.
My problem is/was the same like for @mfld-pub: installing, providing new update and afterwards start from scratch...  ;D

Thanks a lot for all replies!

Turned out the fetch command ran in a timeout. Removing "-T 30" from /usr/local/sbin/opnsense-update made it work - at least the first step downloading the file and sig.

Because the rest of the update process failed to work, too, I decided to let it be like it currently is and hope for a working update to the upcoming release-candidate.

Last question for the while: Will the release-candidate be available via "development" repository or do will I have to change this back to "community"?

Thanks,
Marsellus

Hi guys,

today I first updated 21.7.4 to 21.7.7, then changed firmware type to "development" and updated to 22.1.b_141. Fine, all went smoothly.
But now I get a pending update shown 22.1.b_141 -> 22.1.b3.
Trying to update either in GUI or via CLI-option 12 results in this:

Code Select Expand

Fetching packages-22.1.b3-OpenSSL-amd64.tar: ............................... failed, no signature found

Mirror is set to "OPNsense", so pkg.opnsense.org is used. I can find the signature as packages-22.1.b3-OpenSSL-amd64.tar.sig at same URL like the tar itself, so why is this signature "not found"?

Any help is appreciated!

Thanks in advance, and have a Merry Xmas,
Marsellus W.