23.09.rc Displaying 'later version than official' flag
-
Backend branches are being updated. Should be corrected shortly.
-
@stephenw10 said in 23.09.rc Displaying 'later version than official' flag:
Should be corrected shortly.
Certainly has changed, but still doesn't look correct
shouldn't the list say something
Current Beta Snapshots (23.09)
(perhaps a new entry for (Release Candidate 23.09 RC)
(and finally) Last Stable Version (23.05.1) - this is not an RC as shown??
also notice from the previous screen capture the update for 23.09.r is no longer being offered - I am showing now as "up to date"
the offer of the "r" version is gone from the dashboard as well (as it also again reports "on the latest version"
-
well now that's interesting. I was just walking past the switch cage on the way to grab lunch and the light on the 2100 is flashing as if there is an update. but currently none are showing on either the update page or dashboard as shown above..
I suspect that light was tripped active state earlier when the "r" version was offered and hasn't "reset" , since currently there is no update being offered.
I don't need to reset the light, just another observation that because an update was offered, and nothing was actually updated, and now there is nothing being offered. I have a new blinky light.
-
Yup it checks and updates once a day.
RC will be imminently available after some build tests. Stay tuned....
-
@stephenw10 said in 23.09.rc Displaying 'later version than official' flag:
checks and updates once a day
No worries, would have thought that checking manually (forced check) might have reset ye old blinky light. device is out in another area, out of sight, so I don't see it most time. just an observation
-
Mmm, me too. Though I'm not sure what it does to unset that other than actually upgrading. Or perhaps rebooting. Hmm
-
@stephenw10 said in 23.09.rc Displaying 'later version than official' flag:
Backend branches are being updated. Should be corrected shortly.
Am I now stuck in this in-between state due to the rug-pull?
️ -
@RobbieTT Better yet, should any of us be allowed to update to pfSense+ 23.09 from 23.05.1 ?
-
@NRgia said in 23.09.rc Displaying 'later version than official' flag:
@RobbieTT Better yet, should any of us be allowed to update to pfSense+ 23.09 from 23.05.1 ?
I don't want to join the pitchfork movement just yet and I remain on the optimistic* side of this apparent debacle; especially as I am only running this second (non-Netgate) machine so that I can do kernel and other invasive tests as requested by Netgate devs.
In the short-term though I could do with knowing where I stand with firmware loads as this last-minute change to the business model has happened in the middle of 23.09 beta / rc updates and I am unsure what happens next.
️(* I would be surprised if Netgate asked me to repartition my drive, run kernel dumps etc and for them to bill me $399.00 for doing so.)
-
@RobbieTT It's not about the pitchforks, I'm also using pfsense+ on a whitebox. I think it's a great thing that you test and help the devs, but aren't you interested if you can use it still? That's all
-
@RobbieTT said in 23.09.rc Displaying 'later version than official' flag:
change to the business model has happened i
Technically challenges aside - to what business model change do you refer?
-
@NRgia and @jrey
For sure I am interested, even though I own a Netgate 6100 and the pfSense+ licence that comes with it, it looks like it may (will?) negatively impact my ability to run a secondary machine.I'm just trying to stay out of it all for the moment. I will acknowledge that this has been a comms disaster for Netgate. They have reversed a position that they encouraged as recently as 2 weeks ago and have left their website and marketing in a confusing mess of conflicting statements and bad links. Nobody in business would intend to implement a change this - Netgate have stumbled out of the bar and pulled a gun - some of this has to be in error or badly mistimed.
Being 'crazy enough to do it' only works in the movies. I think Netgate needs some time to sort this all out - the recent blog post does not cut it.
️ -
The changes to the H+L sub availability are completely unrelated to the fact that some people saw an RC as available when they shouldn't have, yet.
When the RC is ready it will show up for everyone currently running 23.09-Beta. Currently that is held by the upstream OpenSSL fix which should be available very shortly.
Steve
-
Understood, I had not read the recent blog post to which you refer,
It won't impact me. I'm licensed. It will certainly impact a lot of "home" users and impact (likely in a negative fashion) and Netgate's ability to solicit and maintain the support of the open source concept.
The device and software (packages) on it are good, but not that good, that if push comes to shove, I wouldn't just unplug the device and move to something else.
I could give specific examples of packages that get installed, and likely on a lot of devices, that are simply full of security holes and/or out and out are subject to potential failures that can lead to security issues (that's open source). That's the risk and the game.
Netgate will likely come to a fork in the road where they have to decide (stay open or closed) good and bad in each of those, both them and users.
disclaimer, I have no vested interest in Negate. Could continue to "run" with or without their device and/or software. They will obviously proceed in a direction they feel best for their model. And users will ultimately do the same.
I've already crossed the bridge regarding the use of Netgate in certain situations, because of those potential failures and in those cases we use just use different products.Anyway this is somewhat off topic of the 23.09rc etc that debacle likely won't stop either way. It has been outstanding and consistent since at least 22.05 where every new update brings a "list" debacle.
-
-
and so it begins
https://forum.netgate.com/topic/183637/loved-past-tense-pfsense/5
(sorry my last off topic post on this thread)
-
@stephenw10 said in 23.09.rc Displaying 'later version than official' flag:
upstream OpenSSL fix which should be available very shortly.
can we revisit or can you define the term "shortly" ?
-
The fix is in. Baring something unforeseen expect the RC later today.
-
I guess we must be in the area of "something unforeseen"
In other news, the blinky light stopped (not last night, but the night before) so yesterday's yesterday. Maybe tomorrow's yesterday will be the RC day. We can only guess.
Is what it is.
-
@jrey said in 23.09.rc Displaying 'later version than official' flag:
I guess we must be in the area of "something unforeseen"
Yup there was an issue with OpenSSL. That's now fixed and we are testing internally. Should be public 'shortly'.
