Regression #13593
closed
pfSense-repo.abi left at FreeBSD:14:amd64 after changing update branch to DEVEL and back
0%
Description
After changing the update branch to DEVEL and back, /usr/local/share/pfSense/pkg/repos/pfSense-repo.abi is left containing "FreeBSD:14:amd64" and further update checks fail.
1) change to DEVEL:
Current Base System 2.6.0
Latest Base System 2.7.0.a.20221025.0600
2) change to latest stable (2.6.0):
Retrieving Unable to check for updates
3) from shell:
[2.6.0-RELEASE][admin@router]/usr/local/share/pfSense/pkg/repos: cat pfSense-repo.abi
FreeBSD:12:amd64
(change branch to DEVEL)
[2.6.0-RELEASE][admin@router]/usr/local/share/pfSense/pkg/repos:
cat pfSense-repo.abi
FreeBSD:14:amd64
(change branch to stable)
[2.6.0-RELEASE][admin@router]/usr/local/share/pfSense/pkg/repos: cat pfSense-repo.abi
FreeBSD:14:amd64
system log (14:07 is UTC, 9:07 is US CDT):
Oct 25 14:07:44 check_reload_status 353 Syncing firewall
Oct 25 14:07:44 php-fpm 69691 /pkg_mgr_install.php: Configuration Change: admin@ip (Local Database): Saved firmware branch setting.
Oct 25 09:07:13 pkg-static 50845 pfSense-repo upgraded: 2.6.0_8 -> 2.7.0.a.20221025.0600
Oct 25 09:07:11 pkg-static 47503 pkg upgraded: 1.17.5_2 -> 1.18.4_1
Oct 25 14:07:02 check_reload_status 353 Syncing firewall
Oct 25 14:07:01 php-fpm 69213 /pkg_mgr_install.php: Configuration Change: admin@ip (Local Database): Saved firmware branch setting.
Updated by
Updated by Kris Phillips over 2 years ago
I can confirm this on 22.05 when switching to the 23.01 repos as well.
Updated by Steve Wheeler over 2 years ago
- Status changed from New to In Progress
- Assignee set to Brad Davis
- Target version set to 2.7.0
- Plus Target Version set to 23.01
- Affected Architecture All added
- Affected Architecture deleted (
amd64)
This is now fixed in CE:
Nov 10 22:27:35 php-fpm 406 /pkg_mgr_install.php: Configuration Change: admin@172.21.16.8 (Local Database): Saved firmware branch setting. Nov 10 22:27:35 check_reload_status 444 Syncing firewall Nov 10 22:27:54 pkg-static 44617 pkg upgraded: 1.17.5_2 -> 1.18.4_1 Nov 10 22:27:57 pkg-static 48801 pfSense-repo upgraded: 2.6.0_8 -> 2.7.0.a.20221110.1541 Nov 10 22:28:28 php-fpm 407 /pkg_mgr_install.php: Configuration Change: admin@172.21.16.8 (Local Database): Saved firmware branch setting. Nov 10 22:28:28 check_reload_status 444 Syncing firewall Nov 10 22:28:46 pkg-static 40500 pfSense-repo downgraded: 2.7.0.a.20221110.1541 -> 2.6.0_8 Nov 10 22:28:48 pkg-static 40500 pkg downgraded: 1.18.4_1 -> 1.17.5_2
Updated by Patch Public over 2 years ago
It works for me now running pfsense 2.6.0-RELEASE (amd64)
Updated by Brad Davis over 2 years ago
- Status changed from In Progress to Feedback
Updated by Steve Wheeler over 2 years ago
This looks good in Plus too:
Nov 11 14:30:37 php-fpm 379 /pkg_mgr_install.php: Configuration Change: admin@172.21.16.8 (Local Database): Saved firmware branch setting. Nov 11 14:30:37 check_reload_status 417 Syncing firewall Nov 11 14:30:45 pkg-static 65234 pfSense-repo upgraded: 23.01.a.20221109.0600 -> 23.01.a.20221111.0600 Nov 11 14:45:04 php-fpm 379 /pkg_mgr_install.php: Configuration Change: admin@172.21.16.8 (Local Database): Saved firmware branch setting. Nov 11 14:45:04 check_reload_status 417 Syncing firewall Nov 11 14:45:25 pkg-static 22101 pfSense-upgrade upgraded: 1.0_27 -> 1.0_28 Nov 11 14:45:25 pkg-static 22101 pfSense-repo downgraded: 23.01.a.20221111.0600 -> 22.05_13
Updated by Jordan G over 2 years ago
much happier now, I had a 22.05 VM that was unable to check for updates after switching to dev branch last week. Now have the ability to check for updates/install packages on stable branch or update to latest dev build.
Updated by Kris Phillips over 2 years ago
Tested this on my 22.05 box as well. Looking good. This can be marked as Resolved.
Updated by Steve Wheeler over 2 years ago
- Status changed from Feedback to Resolved
Updated by Jim Pingle over 2 years ago
- Tracker changed from Bug to Regression
Not a problem in a release, excluding from release notes.
Updated by Jim Pingle over 2 years ago
- Release Notes changed from Default to Force Exclusion