Hello,
I’ve installed Centos Stream 10 and enabled the EPEL repo. I don’t see libreoffice available in the base, appstream, or epel repos. I searched for the el10/epel10/epel10.2 tag on libreoffice builds on koji, but it looks like there’s no build of libreoffice for CS10. There are builds for eln*, and for EPEL9, I’m wondering what I’m missing for 10.. Can someone point me in the right direction to get LO on CS10? Thanks!
You can install it as a flatpak, see flathub.org.
As @cbravo says it is only available as a flatpak. The package was decided not to be worked on anymore by Red Hat so unless a group of packagers maintains it in EPEL, then the upstream builds are where to get it.
Are there any RH supported office programs for EPEL 10?
Not that I know of. Nothing in EPEL is Red Hat supported. In general the only items supported by Red Hat are packages built and shipped in Red Hat Enterprise Linux. Everything else is ‘caveat emptor’
Installation details can be found here;
If someone wants libreoffice in EPEL 10 as an alternative to the Flathub package, here is the relevant request. Many dependencies are currently missing and would need to be added first.
LibreOffice is not officially available for CentOS Stream 10 yet, but it can usually be installed through Flatpak or third-party repositories as a reliable workaround.
Thanks for the hint.
As I’m really interested in the process and would be willing to contribute, I would be grateful for an explanation of the following process:
A person writes in bugzilla: “There are a lot of dependencies missing. Please file a bug for each and have them block this bug.”
Another person later asks: “Are there still package requests to be opened? I only see three open.”
And gets the answers from the first person: “If they’ve been opened, the don’t block this bug. So, yes, probably.”
Unfortunately I do not understand the rules and the procedures they are talking about. Where would I best start with making myself familiar with it?
My motivation behind it:
I recently installed CentOS, but I miss a few really crucial packages in EPEL. Some flatpaks are not stable enough for my purpose (e.g. LibreOffice crashes too often, and I would prefer a better integrated package).
So: what could be done to further support the provision of LibreOffice in EPEL?
Thanks for any help.
Awesome, we’re always looking for new contributors.
To add a package to EPEL, the necessary build time and runtime dependencies need to be available first. Right now package maintainers primarily manage this through bugzilla bugs, which can be set to block or depend on one another. A package maintainer may or may not have access to add each individual dependency, so the bugs are a way to work collaboratively on related tasks. Anyone can file the bugs to track the work and then they can be worked on by the relevant maintainer of each package.
For a contrived example, let’s say Alice maintains package foo, and Bob maintains package bar, and foo requires bar to build or run. Someone may file a bug asking for foo, and then file a bug asking for bar. The bar bug would block the foo bug. First Bob would take care of the bar bug, and then Alice would take care of the foo bug.
At the time @limb commented on the missing dependencies, it looks like there were 41 not available. Since then, four request bugs were marked as blocking this one (or this bug was marked as depending on four other bugs, which is the same thing). Those bugs already existed, and just didn’t have the depends/blocks relationship set yet. One of them has been completed, and three are still open.
There could be additional bugs that have been filed that don’t have the depends/blocks relationship to this bug set. The remaining dependencies need to be reviewed for one of three outcomes:
I recommend starting with this general guide for filing a Fedora bug.
Once you’re familiar with that, also review this guide that is specific to filing EPEL package requests bugs.