I understand that. But i have no clue on how to install those kinds of files in my jail. And even if i somehow figure out how it works it doesn’t fix the problem for all the other users that are still running TrueNAS Core or something else on FreeBSD 13 and also can’t update to the latest version.
And so far as i understand it, it’s the official port for FreeBSD 13 that doesn’t get updated.
And i did reach out to the maintainer but i haven’t gotten a response. So i’m trying to find another way to keep my server from having a vulnerability with an unknown impact. It’s something big because you guys have emailed me about updating my server to a current version. Which i wanna do but can’t because for some unkown reason to me the official package doesn’t get pushed.
I know but that’s going to take weeks. Just the backup of Plex following https://support.plex.tv/articles/201539237-backing-up-plex-media-server-data/ has taking me all evening because it’s 144.000 files. On Windows and Linux you can skip the Cache folder which contains 142.000 files in my case but i’m running FreeBSD. I could probably skip it but who knows for sure? The official manual doesn’t so that’s going to take another evening of combing through weird blogs that haven’t been updated sinds 2019 .
Eh, it’s the FreeBSD ports collection. Ports are submitted by … whoever. Sometimes it’s the official original developer. More often it’s a 3rd-party volunteer who creates those packages.
In this case it’s a 3rd party, not an official Plex package. They already submitted the updates for the security fix.
The FreeBSD ports maintainers build packages on a schedule, not immediately. Usually latest is around weekly, quarterly is every couple months. But also things don’t always go perfectly, sometimes it takes a bit longer. Build status for various versions here: https://pkg-status.freebsd.org/
It just hasn’t been built yet.
You could switch to the port instead of the pkg. You could use the official downloads from Plex. Or there’s an imperfect-but-popular script called PMS_Updater.
Thanks. Now I kinda understand what the problem is. Yesterday i tried to follow a guide on the TrueNAS forum for an updater script but that one pointed to a Github that didn’t exist.
Well, I haven’t received any such e-mail and I just checked, including spam… As others have mentioned, it should be available once the package builders complete building the packages it should be available… I have no control over the package servers and have no knowledge of TrueNAS Core…
I guess you could always spin up a VM or system with FreeBSD 13 and use the ports system to make your own package…
That’s weird. But it’s all good. I now understand a little better how this stuff works and that it takes time. And just to be clear: i really appreciate all the effort you and all the other people put in keeping the software i use daily running smoothly.