Upgrade packages on 2.4.5-p1

RyanM

I am running 2.4.5-RELEASE-p1. I went to my "Package Manager" today to update packages. It showed I have several that can be upgraded. When I click the icon to upgrade, it takes me to the "Package Installer" page, and prints:

Please wait while the update system initializes

But then nothing happens. Any ideas?

bchan

@ryanm I got same error. After some reading in the web, logs in /cf/conf showed:

WARNING: Current pkg repository has a new PHP major
         version. pfSense should be upgraded before
         installing any new package.

I believe it was the reason why installer stucks.

RonpfS

@ryanm There was a change in the repo this morning,
System > Update > System Update select Previous Stable Version (2.4.5 Deprecated), then go to Package Manager tab, no more update available.

bchan

@ronpfs Thanks for the tip. I have noticed that pf 2.5 is also available for upgrade. Will the php version problem I found cause any hiccup in the upgrade?

RonpfS

@bchan I don't know, I didn't lauch any pkg update before changing the 2.4.5 setting.

Check the log, maybe some pkg install is still running, check the forum & reddit for similar issues.

Gertjan

@bchan said in Upgrade packages on 2.4.5-p1:

Will the php version problem I found cause any hiccup in the upgrade?

If the base system, kernel, libs etc are still 2.4.5-p1 - and PHP libs are upgrades as packages are now for "2.5.0" than things get messy at best.
Retrieve your config file. keep it in a save place, and if doubts, clean install.
To 2.4.5-p1 or
To 2.5.0.

In any case, remember to select the right :

bradyrtech

@ronpfs Good morning -- would this repo change also result in a system running 2.4.5-p1 (as of last night), showing the 2.5.0 update available -- no longer show the 2.5.0 update available as of this morning? the "Previous Stable Version (2.4.5 Deprecated)" is now the selected branch under System > Update > System Update.

No changes were made over the last 8 hours. I just decided to wait until I woke up this morning to do the upgrade and it [was] looking like it was pulled but perhaps this repo change is the culprit. "Latest stable version (2.5.x)" is a selectable, but not the default branch now.

thanks!
-ryan

lohphat

Yup. So this is a bug in the UI that it doesn't communicate this, it just hangs.

lohphat

This post is deleted!