libreoffice package abandoned

gpw928

gpw928

A package upgrade just deleted libreoffice-7.5.5.2_3.
It's still in the ports tree, but has enough dependencies to sink the Titanic:
Code: 
[strand.156] $ cd /usr/ports
[strand.157] $ grep -i "^libreoffice" INDEX* | cut -c1-70
libreoffice-7.6.2.1|/usr/ports/editors/libreoffice|/usr/local|Full int
libreoffice-i18n-7.6.2.1|/usr/ports/editors/libreoffice-i18n|/usr/loca
I really need to be have to be able read documents in various M$ formats.
I see that the apache-openoffice-4.1.14_3 package is available.
Does anyone know what's going on with the libreoffice package?

Edit: I just installed the apache-openoffice-4.1.14_3 package, and it hangs on start-up...
 
I managed to lock it before upgrading, but it does not start anyway. The rectangular LO box pops up quickly then disappears. Hopefully back up soon.
 
It looks like you are tracking latest repo, not quarterly? In quarterly it's at 7.5.4.2. I'm guessing that if you look at build logs that the 7.6.2.1 version probably failed to build.
 
gpw928 said:
Does anyone know what's going on with the libreoffice package?
Click to expand...
You can query the (failed) build status of a package at https://portsfallout.com or on https://freshports.org of the ports page editors/libreoffice. Look at the top of the ports page, next to the version number, for the three leaf nuklear symbol icon. Klicking on it brings you to portsfallout.com ports fallout list. From there one can inspect the build environment. For 132amd64-default the fallout detail.

Under "Category" is the cause of the build failure recorded. One can also inspect the build log, which is accessible if you have a ipv6 connection.

But there is also a "Report URL", leading to the freebsd-pkg-fallout FreeBSD mailing list, to inform the maintainer, with the log attached, viewable over ipv4.

The cause for libreoffice to fail build is runaway build:
Code: 
=>> Killing runaway build after 7200 seconds with no output

In case of libreoffice, the package should be back in short time, after the runaway cause is resolved.
 
Thank you for all the responses.

I'm tracking the latest package builds (not quarterly) on my daily driver FreeBSD system.

I reinstalled libreoffice-7.5.5.2_2 from /var/cache/pkg, but ran into dependency issues with shared libraries, so I will just await the fix.

I have installed libreoffice on my ZFS server as a work-around (it tracks quarterly).
 
gpw928 said:
I see that the apache-openoffice-4.1.14_3 package is available.
Click to expand...
apache-openoffice failed to build since 2022Q3, because prereq boost-libs was changed to use c++11, and apache-openoffice code is incompatible with c++11. It looked not all too easy to fix.

gpw928 said:
Does anyone know what's going on with the libreoffice package?
Click to expand...
No, but libreoffice has a random build problem. Every 2nd or 3rd run it goes into an endless loop during build. I was wondering why nobody else sees this problem. The workaround is to just rerun the build.


T-Daemon said:
You can query the (failed) build status of a package at https://portsfallout.com or on https://freshports.org of the ports page editors/libreoffice.
Click to expand...
Aha. From that link:
Code: 
[build PKG] Gallery/backgrounds
touch /wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-7.6.2.1/workdir/Gallery/backgrounds.final
[build BIN] extras
S=/wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-7.6.2.1 && I=$S/instdir && W=$S/workdir &&  mkdir -p $W/Module/nonl10n/ && touch $W/Module/nonl10n/extras
[build MOD] extras
S=/wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-7.6.2.1 && I=$S/instdir && W=$S/workdir &&  mkdir -p $W/Module/ && touch $W/Module/extras
=>> Killing runaway build after 7200 seconds with no output

From my build logs:

Code: 
[build PKG] Gallery/backgrounds
touch /var/local/ports/usr/ports/editors/libreoffice/work/libreoffice-7.5.4.2/workdir/Gallery/backgrounds.final
[build BIN] extras
S=/var/local/ports/usr/ports/editors/libreoffice/work/libreoffice-7.5.4.2 && I=$S/instdir && W=$S/workdir && mkdir -p $W/Module/nonl10n/ && touch $W/Module/nonl10n/extras
[build MOD] extras
S=/var/local/ports/usr/ports/editors/libreoffice/work/libreoffice-7.5.4.2 && I=$S/instdir && W=$S/workdir && mkdir -p $W/Module/ && touch $W/Module/extras
Killed

This is harmless, just needs to re-run.

Also to notice here: this happens with various versions of libreoffice. Only perchance did it this time hit the official testbuild.
 
Libreoffice disappeared and I ran a pkg search and I too noticed apacheopenoffice. Is it coming back?
For now relying upon /var/cache/pkg/
What about those poor souls who do not have a copy?


Update:
Sadly didn't help much.
Code: 
ld-elf.so.1: Shared object "libboost_locale.so.1.82.0" not found, required by "libutllo.so"
Tried to use the newer 1.83 and created soft-link for the old one and now getting this error:
Code: 
ld-elf.so.1: /usr/local/lib/libreoffice/program/libutllo.so: Undefined symbol "_ZN5boost6locale4info2idE"

Also tried older packages, no luck .
 
quakerdoomer said:
Thanks will try. Really desperate. Feel so abandoned by FreeBSD. Getting tough day by day to resist switching to Linux.
Click to expand...
I switched to the latest packages on my FreeBSD daily driver quite a while back to get the latest version of something that was known to be badly compromised (a web browser, I think).

I never really understood how bleeding edge the "latest" packages were until yesterday. So I have had a lucky run.

I always want my web browser to be "current" because I don't want to be vulnerable to hacks. But I do need my systems to be stable. So I have a quandary.

Maybe there's a case for a third category of packages, "quarterly+security"?

Edit: I see that there's another discussion already running on this subject...
 
gpw928 said:
I switched to the latest packages on my FreeBSD daily driver quite a while back to get the latest version of something that was known to be badly compromised (a web browser, I think).

I never really understood how bleeding edge the "latest" packages were until yesterday. So I have had a lucky run.

I always want my web browser to be "current" because I don't want to be vulnerable to hacks. But I do need my systems to be stable. So I have a quandary.

Maybe there's a case for a third category of packages, "quarterly+security"?
Click to expand...
I agree with you. Especially with Google chrome the state of updates is appalling. Chrome has pledged weekly security updates but we do not get that as frequently. There was a time when ungoogled-chromium used to keep up with FreeeBSD releases but those days are gone. I am considering diving into how to compile chromium on FreeBSD on my own. I really am mad at Opera and Vivaldi to be honest. They used to release FreeBSD builds, now even Vivaldi does not care but run around telling everyone how true they are to the essence of the Original Opera browser. The only good reliable browser which sends near-timely updates is Firefox. I wish they also had the blue colored Nightly releases for FreeBSD.
 
Normally engineering decisions in FreeBSD are defaulted to the principle of least surprise.

I would argue that the package removals are certainly a big surprise and should only be done if this behavior prevents an even bigger surprise.
 
We are told to stick to Quarterly releases if we do not want to lose packages and not use the Latest release repository. Staying a quarter behind increases security issues. On one had we say FreeBSD is much secure than Linux and the likes of MS and Meta uses it to run its servers and on the other hand we say, stay 3 months behind if you want all your software intact. FreeBSD is not suitable anymore for Desktop usage I feel.
 
Tieks said:
Nope. Quarterly will get security updates as well.
Click to expand...

Are you sure?
I just compared
and


Firefox version in the latest shows:
Code: 
{"name":"firefox","origin":"www/firefox","version":"118.0,2","comment":"Web browser based on the browser portion of Mozilla","maintainer":"gecko@FreeBSD.org","


Firefox version in the quarterly shows:
Code: 
{"name":"firefox","origin":"www/firefox","version":"118.0.1,2","comment":"Web browser based on the browser portion of Mozilla","maintainer":"gecko@FreeBSD.org",

Sure eventually it will get that update. Not as of now.
 
The problem here is that some package combine these two properties:
- often have security issues
- are complicated to build with many dependencies

Such as Firefox and Chromium. It is very difficult to fulfill the promise of security backports in quarterly when these ports are involved.

One possible solution is to use Linux binaries.
 
You must log in or register to reply here.
Back
Top