No LibreOffice in package repos???

siealex said:
I'm talking not about upgrading, but about a fresh installation.
In such cases, is it possible to force install the quarterly packages without switching the whole system to the quarterly repo?
Click to expand...
Interesting. I think by default whatever "CURRENT" is (15.0 at the moment) by default points at latest. I'm not sure if quarterly is built for CURRENT it may be I just never cared to look.
 
It seems there isn't.
Code: 
$ w3m -dump http://pkg.freebsd.org/FreeBSD:15:amd64/
Index of /FreeBSD:15:amd64/

 File Name  ↓    File Size  ↓      Date  ↓
Parent directory/ -              -
base_latest/      -              2025-Aug-19 12:03
base_weekly/      -              2025-Aug-17 12:02
kmods_latest/     -              2025-Aug-08 12:01
latest/           -              2025-Aug-17 11:42
 
Charlie_ said:
It seems there isn't.
Code: 
$ w3m -dump http://pkg.freebsd.org/FreeBSD:15:amd64/
Index of /FreeBSD:15:amd64/

 File Name  ↓    File Size  ↓      Date  ↓
Parent directory/ -              -
base_latest/      -              2025-Aug-19 12:03
base_weekly/      -              2025-Aug-17 12:02
kmods_latest/     -              2025-Aug-08 12:01
latest/           -              2025-Aug-17 11:42
Click to expand...
Thanks that verifies my understanding.
I've never heard of a desire to "run CURRENT but point pkgs at quarterly". It's usually "run PRODUCTION (CURRENT -1 like 14.x) and pkgs from latest" to get updates on applications sooner.
I've always looked at CURRENT as you may need to run it for your specific hardware but you need to accept breakage that may take a while to resolve.

Everyone runs what they need to for "reasons" but hard to help unsupported combinations. So sometimes all folk can give is ideas and thoughts, not definitive solutions
 
Right now the latest snapshot Aug. 19th is giving me various error messages if I try to install anything, including pkg. :)
(I know we're not supposed to talk about CURRENT here, but I thought you folks might get a charge out of it. Get it? CURRENT? Charge?
It's a POWERful pun.)
Ok, ok, I'll see myself out, thanks.

To be serious for moment, the snapshot of 0819-2025, marked PRERELEASE if you run uname -r, has an /etc/pkg/repos/FreeBSD.conf pointing to latest, including the kmods.
 
scottro said:
Right now the latest snapshot Aug. 19th is giving me various error messages if I try to install anything, including pkg. :)
(I know we're not supposed to talk about CURRENT here, but I thought you folks might get a charge out of it. Get it? CURRENT? Charge?
It's a POWERful pun.)
Ok, ok, I'll see myself out, thanks.

To be serious for moment, the snapshot of 0819-2025, marked PRERELEASE if you run uname -r, has an /etc/pkg/repos/FreeBSD.conf pointing to latest, including the kmods.
Click to expand...
Maybe related?
 
Actually, I saw those, but was more interested in making my current, get a charge out of joke, but thanks to both of you. When I got the errors, the first thing I did was go to the CURRENT mailing list.
When I was working at a CentOS shop, back when it was more RH, I used to use Fedora, so I'd be prepared for any surprises. But, to be honest, with FreeBSD, I usually keep a VM of CURRENt, but--I also am almost never unpleasantly surprised. I'd say they do make an effort to keep POLA (Principle Of Least Astonishment) and do a good job of it most of time.
 
Few years back, AFAIR ~v12, pkg upgrade removed LibreOffice, and I deleted older downloaded pkg from the cache before that upgrade, so I was left without it. Luckily, having LibreOffice is not critical for me, but I had to wait for it to reappear in the repo. Since, I'm always upgrading with pkg upg -n | grep Number first, and if there is nothing scheduled to be removed, I go with pkg upg -y, but if there is something that pkg upgrade wants to remove and I need it, I'll put lock on those packages first and only then go with pkg upg.
 
Last edited:
Another good example for why using pkg upg -n | grep Number first is a smart thing to do, from just an hour ago:

pkg upg wanted to remove print/hplip, print/cups-filters and print/gutenprint. I like my hplip icon being in Plasma task manager because hplip app GUI is quite simple to set duplex printing and other goodies (I have HP P3015dn connected to LAN so I can print from all my boxen; I know that all can be set from cups, but often this is much simpler and faster).

I put a lock on hplip and only then proceeded with upgrade. BTW, reason that hplip appears in KDE 6.4.4 task manager is that this install is upgraded for the long time, so I still have a lot of qt5/kf5 stuff around, and hplip doesn't work well with qt6 only. I hope that reason for removal from the repo is that HP devs are working on new, qt6 compatible version.

In the meantime, hplip is still there, it's not removed and works as well as before.
 
Last edited:
And hplip, gutenprint and cups-filters are back in the 'latest' pkg repo. Only cups-filters had minor upgrade (1.28.17_9 -> 1.28.17_10), hplip and gutenprint didn’t have any version change, yet they disappeared for a day or two, and pkg upg wanted to remove them from the system. Repo eFups happen from time to time, especially with 'latest', that’s why I’m advocating for professional/corporate use to always install from own, local poudriere built repo, and to be very careful in personal use when using official 'latest' repo.
 
vmisev said:
that’s why I’m advocating for professional/corporate use to always install from own, local poudriere built repo, and to be very careful in personal use when using official 'latest' repo.
Click to expand...
This is reasonable and honestly what a lot of people have said for a long time. Following "latest" for pkg is akin to using CURRENT and one needs to be aware of "There is always a chance for breakage".
Maintaining ones own repos is always a good idea if you have the ability.

But that's also why the recommendations are "if you are following RELEASE you should follow Quarterly not Latest"
 
mer said:
Following "latest" for pkg is akin to using CURRENT and one needs to be aware of "There is always a chance for breakage".
Maintaining ones own repos is always a good idea if you have the ability.

But that's also why the recommendations are "if you are following RELEASE you should follow Quarterly not Latest"
Click to expand...
I admit, I’m an obsessive-compulsive upgrader 😊. On my personal desktop I run STABLE, on all other OSes I have RELEASE in VM and everywhere I follow 'latest', but I always go with ' pkg upg -n' first, please see 4 posts up.

For professional use, running dedicated poudriere shouldn’t be too expensive nor demanding of too much resources. At the end of the day, there should be SBOM, and then is clear which pkgs are needed (good chance that number of them is quite low) and from there is even easy to calculate how long initial build and then upgrades will take.
 
Last edited:
  • Like
Reactions: mer
You must log in or register to reply here.
Back
Top