Upgrade from 2.3.2 to 2.3.3 fails (some packages are locked)
-
Hi,
When I try to upgrade from 2.3.2, all packages have been updated except 3 packages marked as "locked" :
/root: pkg upgrade
Updating pfSense-core repository catalogue…
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.pkg-1.8.7_1 is locked and may not be modified
Checking for upgrades (3 candidates): 33%pkg-1.8.7_1 is locked and may not be modified
Checking for upgrades (3 candidates): 66%pfSense-kernel-pfSense-2.3.2 is locked and may not be modified
Checking for upgrades (3 candidates): 100%pfSense-2.3.2 is locked and may not be modified
Processing candidates (3 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.Should I manually unlock these packages ?
Many thanks in advance for your help.
-
You should use pfSense-upgrade or the 13/ option from the menu, not pkg upgrade.
-
Thank you for your answer.
I have tried another upgrade method because it had failed without any error message (except "failed") :
Enter an option: 13
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
pfSense repository update completed. 437 packages processed.
Upgrading pkg... failed. -
When is the last time this machine was rebooted?
-
It has been rebooted yesterday when the upgrade failed.
-
It has been rebooted yesterday when the upgrade failed.
Before or after the upgrade failed?
Has the upgrade been attempted immediately after a reboot?
-
The pfSense was up since many weeks when I tried the first upgrade attempt. It failed, I rebooted. Retried an upgrade that failedagain.
-
Really even if you reboot 249 times, if won't fix the braindead pkg. Dunno where that idea came from.
-
even if one pray while rebooting ? :)
more seriously, any idea about this problem ? what about manually unlocking locked packages ? what would be the consequences ?
-
Cannot imagine how would that do more harm, can try that if you are bored.
-
