pfSense 25.07b - Upgrade Notice - check_upgrade
-
Check :
and related System > Update System > Update Settings
The references to 25.03 are phased out.
It's "25.07" now.
If not already done, select "25.07" on both pages, save and try again ?( Just a suggestion - I went to "25.07.b.20250628.0006" and can't find any issues :( )
-
-
@RobbieTT said in pfSense 25.07b - Upgrade Notice - check_upgrade:
25.03
Mentioned ^^
It was 'b' or Beta in the past - before yesterday..
and doesn't exist anymore.
It's "25.07" now.Si I guess (tm) that your pfSEnse still tries to pul from a 25.03bxxxxx update server and it can't find it.
Anyway, just guessing here. -
@Gertjan said in pfSense 25.07b - Upgrade Notice - check_upgrade:
@RobbieTT said in pfSense 25.07b - Upgrade Notice - check_upgrade:
25.03
Mentioned ^^
It was 'b' or Beta in the past - before yesterday..
and doesn't exist anymore.
It's "25.07" now.Si I guess (tm) that your pfSEnse still tries to pul from a 25.03bxxxxx update server and it can't find it.
Anyway, just guessing here.That quote (25.03) is not from me, it only came from you!
I've no idea why you think the beta (b) marker does not exist anymore. Clearly the latest is 27.07.b, as shown in both my screenshot and on your own example screenshot too.
Are you trying to derail things again with the assertion of dubious knowledge and self-contradiction?
️ -
Ok, again :
As I had this "check_upgrade: "Updating repositories metadata" returned error code 1" as the issue, and you were asking for ideas.
And because I just upgraded to 25.07b and saw for a couple of seconds a message telling me "can't find metadata" I thought, when I read you post : Is your Update Branch set correctly ?
As I can image that 23.05b branch on the update server doesn't exist anymore.
A error code of "1" is afaik most often a "can't find error".@RobbieTT said in pfSense 25.07b - Upgrade Notice - check_upgrade:
Are you trying to derail things again
Yeah, right.
-
Now on 25.07.b.20250707.2346 and the check_upgrade notice has gone.
️ -
Still needs some improvement there probably. It throws that generic error for a number of failures and could be refined. I only hit it on a few systems at boot. It appears to be a race condition with the initial check.
-
@stephenw10
I'll keep an eye for it but all looks fine now.
Did the RA patch (685080088725a) and the Apple .png patch (6855d0f643a33) make it to this build?️ -
The RA patch should be there but I don't think the apple icons patch made it. Let me see....
-
@stephenw10
The icon issue has returned so it looks like it didn't make the cut (or has a different issue).️ -
Yup it's not there. Seeing if we can sneak it in. Otherwise it might have to be a system patch until 25.11.
-
