System Patches package version 2.2.x

[jimp]

Update the package, look over the list and just apply anything you think you might benefit from that isn't already applied. Or whack the apply all recommended button again and it'll just apply all the new stuff.

No need to revert or touch anything before/after otherwise.

[JonathanLee]

@jimp Thank you, I appreciate all you do. It's working great on my 2100 MAX

[JonathanLee]

@jimp @LamaZ Your patch for authenticated NTP status is also still working.

[keyser]

@jimp said in System Patches package version 2.2.x:

Update the package, look over the list and just apply anything you think you might benefit from that isn't already applied. Or whack the apply all recommended button again and it'll just apply all the new stuff.

No need to revert or touch anything before/after otherwise.

While I really applaude this patch manager and the delivery mechanism it brings, I would like to add that unless 23.05 is right around the corner, it’s my firm belief that a 23.01.1 should be released asap.
It’s a long list of patches now, and waiting many months before they are applied to the average 23.01 upgrader, is simply not the right solution in my opinion.

[jimp]

@keyser said in System Patches package version 2.2.x:

@jimp said in System Patches package version 2.2.x:

Update the package, look over the list and just apply anything you think you might benefit from that isn't already applied. Or whack the apply all recommended button again and it'll just apply all the new stuff.

No need to revert or touch anything before/after otherwise.

While I really applaude this patch manager and the delivery mechanism it brings, I would like to add that unless 23.05 is right around the corner, it’s my firm belief that a 23.01.1 should be released asap.
It’s a long list of patches now, and waiting many months before they are applied to the average 23.01 upgrader, is simply not the right solution in my opinion.

23.05 is targeted for early May (before BSDCan), we're already in the first stages of the release cycle and things are looking pretty good overall. At this point it would take us longer to shift gears and put out a patch release than to keep moving forward.

[keyser]

@jimp said in System Patches package version 2.2.x:

23.05 is targeted for early May (before BSDCan), we're already in the first stages of the release cycle and things are looking pretty good overall. At this point it would take us longer to shift gears and put out a patch release than to keep moving forward.

Here’s hoping that your schedule stays on track - that’s within the next 3 weeks :-)

[JonathanLee]

@jimp Will I need to remove all patches before the inplace upgrade? Custom ones also? Or can I just leave them?

[SteveITS]

@jonathanlee no just apply new ones.

[chrcoluk]

Nice, I am only on 2.6.0, one of the reasons i didnt move to plus is I didnt know if custom system patches could still be done for that version.

This package is one of the nicest features about pfSense, not just because of the recommended patches but the fact you officially support people making their own patches which is awesome.

I currently have 16 of my own patches active via this package.

[JonathanLee]

@steveits but for new OS updates do we remove before PfSense updates?

[JonathanLee]

https://redmine.pfsense.org/issues/13984

Off topic, but has anyone checked out this patch that is set up for pull request review??

[SteveITS]

@jonathanlee said in System Patches package version 2.2.x:

@steveits but for new OS updates do we remove before PfSense updates?

I do not. After upgrading pfSense, the upgrade will have upgraded the System Patches package. It will only show patches that apply to the new pfSense version.

Basically, all recommended patches are going to be included in the next pfSense version.

[jimp]

@jonathanlee said in System Patches package version 2.2.x:

@steveits but for new OS updates do we remove before PfSense updates?

No, you do not need to do anything in this package before upgrading. Just leave it as-is.

In the majority of cases, what you are updating to will contain all of the patches available to previous versions. If you had custom patches that are not a part of pfSense software you might need to reapply those after upgrading, but otherwise you don't need to touch anything in the package before or after upgrading.