Package updates handled differently for official hardware?

Ramosel

I'm currently helping BBCan177 out with testing for new features of pfBlockerNG. An issue came up recently when he had the Devs merge a PR to include the PHP pecl international library. This resulted in the public version of PfBlockerNG being updated to 2.1.1_8. He asked that I update to this version then reload the test files on top. For some reason, my system will NOT show the 2.1.1_8 version as being available… in the dashboard widget or the package manager. I know he pinged Renato on this issue but we have not heard back yet.

I ran the package update command: pfSense-upgrade -u

The component files updated and yet my system still does not show the 2.1.1_8 version of pfBlockerNG as even being available. After some checking and head-scratching the only difference I have been able to come up with is I am on a "Factory Load" version of pfSense 2.3.3-RELEASE-p1 and not a "Community Edition". I am on a new SG-4860.

Are the two versions, Factory vs. Community actually different in the way they handle package updates??

Can anyone else running an SG-4860 with the factory load and pfBlockerNG 2.1.1_6 or _7 tell me you are being shown an option to the _8 update?

Thanks in advance,
Rick

ivor

No difference, probably something updating on our end. This doesn't seem to be the right board for your question, so I will move it.

Steve_B

My CE 4860 shows v 2.1.1_6 installed, 2.1.1_8 available this morning

jimp

Packages and updates for Factory and CE use different sets of backend builders and repositories. Builds happen at different times and depending on how things happen, an update may not be synchronized from one side to the other until a later build run. It's usually very temporary when things are out of sync in that way.

Ramosel

@jimp:

Packages and updates for Factory and CE use different sets of backend builders and repositories. Builds happen at different times and depending on how things happen, an update may not be synchronized from one side to the other until a later build run. It's usually very temporary when things are out of sync in that way.

As always, Thanks Jim!
It was just an anomaly that neither BBCan177 nor I could account for other than the Factory build. I knew from history they eventually show up… BUT, we were trying to test something invoked by the PR and I needed the _8 release to test. I tried to keep it out of gen pop but someone had other ideas. I know better now.

Rick