I swear, we didn’t pay somebody off on the BSD side to break 13.3 packages right at this particular moment in time to make a point for us. But I am getting a certain level of amusement in watching this, only personally fought these kinds of ports / package breakages for closing in on 2 decades now… This brings back memories.
3 Likes
This is not “breakage”; you should never just update “the day a new build hits the street”. However, quarterly is sort of in a pickle unless they switch trees (but that’s not the end of the world if you’re a “just a user”).
BTW, that’s messed up, man. Some people may not know how to deal with this ‘breakage’ and be “up a creek”. If you have experience, then share not revel.
Okay!? I guess I’ll chime in on how to fix it (I still think it’s messed up that iX would just leave their users out-to-dry or find joy in something like this–this can seem catastrophic to some users).
If you are affected by this issue–I assure you this situation is not catastrophic–basically you should wait a bit but if you’ve already ran a pkg upgrade in a jail of yours, and some of your packages were uninstalled. You can update your ports tree to latest and reinstall those packages.
Chapter 4. Installing Applications: Packages and Ports | FreeBSD Documentation Portal
Eh?
Should iX hold our hand every time? It’s not their issue, it’s FreeBSD’s. Any jail user should not expect much support from iX anyway.
5 Likes
We use language like “Unsupported” for a reason. We don’t control upstream infrastructure like FreeBSD. You can manually fix it today, it can break on you again tomorrow just as easily and there’s not a darn thing we can do about it…
3 Likes
I think it’s more than enough that iX even did the 13.3 update for the community users.
This version is not supported and offered to enterprise customers so iX wont get paid for it this way. And I dont think that community users who use free version of Truenas will pay them either.
So I think community users should be just glad that iX did all this work basically “for free” and shouldnt complain too much. Y’know “don’t look a gift horse in the mouth” and all that 
5 Likes
Missed my point. Not asking to “fix” anything up/down/sidestream. If you or anyone know how to help the problem/issue, why would you just sit back and watch?
And stop making me the bad guy!
Easily fixable by creating your own Poudriere package builder. I have that going locally, building my own packages in a 13.2 poudriere-provisioned jail, and now all my application jails have an endless supply of updated packages (or, rather, I should say, until the underlying ports still support building on 13.2, but that’s surely a longer timeframe than upstream support for 13.2 packages).
2 Likes
I did pay for my setup. You didn’t? …But that’s not my point (and of course releasing 13.3 was a good thing! Why would anyone suggest otherwise) it was more along the lines of “common curtesy”. It’s totally understandable to want people to use your latest product but there may be other issues why people have not updated and/but to watch–or find humor in–someone’s problem when you have the knowledge on how to “help” is just not nice (or to use the situation to pile on more FUD).
Welcome @jmpalacios.
Nice. You wouldn’t happen to have any links or writeups you could share would ya?
Upstream FreeBSD package builders most probably always run with a clean slate (i.e. poudriere bulk’s -c flag), meaning that already-built packages are always deleted just prior to a new build run even if nothing changed for them.
If this is indeed the case, that’d mean that, if a package fails to build in a new build/bulk run, then it’d mysteriously disappear from the upstream repository when you ‘pkg update’ in your downstream environment (VM/jail/whatever).
The way to go about this is usually to check for potentially upstream package builder failures, for which freshports.org helps a great deal, report it / follow related discussions if found, and then ‘pkg update’ again once the build issue gets fixed and the target package appears again in the repository.
1 Like
Thank you for your warm welcome, but hardly a newcommer here, just silent the last few months 
I’ve been honing my local poudriere environment to the point of being able to script it via cron for nightly & quarterly builds, thus fully replacing the upstream FreeBSD repositories for all my jails on “latest” and “quarterly”, but I don’t yet have any write ups I could easily share (though I should indeed get serious about that, so many non-trivial things I’ve done that I’d love to publish somewhere!).
In any case, when it comes to poudriere, I’ve hardly done anything novel on top of creating a FreeBSD 13 VM, hosted right on my TrueNAS CORE right and with the necessary RAM & CPU allocations, and then follow any number of poudriere tutorials you’ll find out there on how to customize your local /usr/local/etc/poudriere.conf file to your needs.
Once you do that, you go to your target VM’s/jails/what-have-you and create a pkg repository file at /usr/local/etc/pkg/repos/$YourRepoName.conf for your local builder, and then either disable the upstream FreeBSD repo via a local /usr/local/etc/pkg/repos/FreeBSD.conf file, or become used to using pkg update -r $YourRepoName && pkg upgrade -r $YourRepoName every time you go on a package upgrade rampage.
If you’d still like more tips, feel free to hit me up via any kind of DM you might like.
1 Like
Oh?! Well, then I take it back! Consider yourself no longer welcome by me.
Yeah, I have the same thing. I have so many notes, I need to take. Hit me up if you get some notes going (not just this, either) and I’ll do the same. I also really need to resurrect my github account to host some of these notes.
EDIT:
Great minds…
One day I’ll get a blog going, and hopefully, among other things, finish up and post that thorough write up I put together on FreeBSD GEOM that I so much enjoyed researching for back when TrueNAS didn’t even tell you what ZFS pool a disk belonged to!
Alright, last side-bar (I’ll try a DM or whatever, still not good with that stuff yet).
I’m trying to resurrect a side-project to sort of help in man page writing. let me know if you want it (when I get my github going again).
Welcome @jmpalacios
1 Like
Will 13.3+ be offered to Enterprise customers at some point?
It is a community release only. See: