Last week I upgraded to 25.7 RC2 - which has worked well. I did this by changing to the development stream and then updating.
Now that 25.7 is released I switched back to the community stream & searched for updated.
mostly the suggested updates looked good, but I noticed this on the preview:
opnsense N/A 25.7 new OPNsense
opnsense-devel 25.7.r_33 26.1.a_4 upgrade OPNsense
opnsense-update 25.7.r2 25.7 upgrade OPNsense
So presumably that would result in both opnsense & opnsense-devel being installed (with the latter being on the next alpha)
Is there an appropriate way around this to get to 25.7? Do I just accept?
It's not a big issue -- I have a snapshot (proxmox) from before the update to 25.7 rc2 so I could revert to that and do a normal update. My config is also backed up automatically to google drive, and it's only a home system. So no big risks.
But it was intriguing to know if there is an appropriate process to follow here? (other than don't)
I was able to sort this out (thanks to gemini)
- unlocked/force removed opnsense-devel
- ran bootstrap
- force-sync
Seems intact - nice to see how the recovery processes work
The appropriate way would have been to change the Type from Development to Community in System -Firmware -Settings
What you did was destructive and risky - and uncalled for. But it was golden guidance from AI.
Yes:
> opnsense N/A 25.7 new OPNsense
> opnsense-devel 25.7.r_33 26.1.a_4 upgrade OPNsense
> opnsense-update 25.7.r2 25.7 upgrade OPNsense
Looks correct to me. Wants community "opnsense" as "new". pkg has a bug where it thinks opnsense-devel needs to be upgraded because it is newer than what is currently installed but it is being replaced anyway as you can see from the "new".
> The appropriate way would have been to change the Type from Development to Community in System -Firmware -Settings
Given that "new" thing it was already set this way. Just needed an "update" click.
Cheers,
Franco