You are not logged in.

#1 2017-10-13 06:27:32

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 710
Website

libreoffice

I get:

shell> libreoffice
/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libboost_system.so.1.64.0: cannot open shared object file: No such file or directory

Seems libreoffice (both still and fresh) are build against boost 1.64, but the current version of boost is 1.65.

Last edited by andreas_baumann (2017-10-13 06:28:22)

Offline

#2 2017-10-13 14:03:43

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

The .BUILDINFO claims it was built while boost-libs 1.65.1-1 was installed. I have no clue.

Offline

#3 2017-10-13 18:15:58

tyzoid
Administrator
From: Ann Arbor, MI
Registered: 2017-06-17
Posts: 90

Re: libreoffice

Posting IRC chat from yesterday by a user with the same issue: https://mirror.archlinux32.org/irc-logs … l#16:44:27

Offline

#4 2017-10-15 16:23:25

Jiikuy
Member
Registered: 2017-10-14
Posts: 1

Re: libreoffice

tyzoid wrote:

Posting IRC chat from yesterday by a user with the same issue: https://mirror.archlinux32.org/irc-logs … l#16:44:27

I was that user reporting the problem. I made a workaround for this, but it's not a real solution:
I'm using symlinks:
/usr/lib/libboost_system.so.1.64.0 -> /usr/lib/libboost_system.so
/usr/lib/libboost_filesystems.so.1.64.0 -> /usr/lib/libboost_filesystems.so
/usr/lib/libboost_iostreams.so.1.64.0 -> /usr/lib/libboost_iostreams.so

Offline

#5 2017-10-16 07:53:32

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

I rescheduled libreoffice-still and libreoffice-fresh for a rebuild - maybe this solves everything

Offline

#6 2017-10-31 23:25:00

bushranger
Member
Registered: 2017-10-31
Posts: 6

Re: libreoffice

I migrated yesterday, and discovered the same issue with evolution. The affected libraries are libboost_system.so and libboost_thread.so. Symlinking them, as Jiikuy did, works. Seems like evolution is also due for a rebuild.

Offline

#7 2017-11-01 10:22:26

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

evolution was still in the pipeline (e.g. in testing) - I moved it to extra. Can you confirm, that the error is gone or does it still persist?
Sry for that, the recognition of dependencies is still somewhat unstable :-/

Offline

#8 2017-11-02 10:00:40

bushranger
Member
Registered: 2017-10-31
Posts: 6

Re: libreoffice

The error persists, unfortunately. With evolution 3.26.2-1 I still get
evolution: error while loading shared libraries: libboost_system.so.1.64.0: cannot open shared object file: No such file or directory
and
evolution: error while loading shared libraries: libboost_thread.so.1.64.0: cannot open shared object file: No such file or directory

Offline

#9 2017-11-02 10:04:07

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 710
Website

Re: libreoffice

Yes. Did you try the symlinking for the time being?

Offline

#10 2017-11-02 10:06:04

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

ok, I scheduled evolution for a rebuild - let's see if that fixes it ...

Offline

#11 2017-11-02 11:57:58

bushranger
Member
Registered: 2017-10-31
Posts: 6

Re: libreoffice

Yes, symlinks work. But - sorry for being a spoilsport - there is another dependency problem, in pdfTeX this time. Here goes:
pdftex: error while loading shared libraries: libpoppler.so.68: cannot open shared object file: No such file or directory
The library on the system is *.67, and again symlinking works.

Offline

#12 2017-11-02 12:01:02

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

np for reporting broken packages :-)
again: does the texlive-bin from testing work?

Offline

#13 2017-11-02 13:03:10

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

I seem to have messed up quite a lot (regarding which packages could be moved to stable and which could not).
I will now move all current packages to stable and see which need to be rescheduled.

Offline

#14 2017-11-03 12:03:47

bushranger
Member
Registered: 2017-10-31
Posts: 6

Re: libreoffice

Now both libreoffice and texlive work. Evolution still doesn't. The symlinks
libboost_system.so.1.64.0 -> libboost_system.so
libboost_thread.so.1.64.0 ->  libboost_thread.so
fix it. To be clear: evolution 3.26.2-1, which at the moment is the same in extra and in testing.

Offline

#15 2017-11-03 13:02:35

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

Hmm, this is strange. According to the package metadata, both evolution-3.26.2-1 were built while boost-libs-1.65.1-1 was installed - like I expected. The latter contains libboost_{system,thread}.1.65.1 (and not 1.64.0).
It seems, the build links against uninstalled (at build time) libraries :-/

Offline

#16 2017-11-05 08:51:26

ZeroLinux
Member
Registered: 2017-11-04
Posts: 5

Re: libreoffice

Please, make it clear: is the latest libreoffice-fresh works with manually created symlinks or it works out of box with boost-libs 1.65?

Offline

#17 2017-11-05 09:20:39

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 710
Website

Re: libreoffice

On the machine with core/extra/community with the standard pacman.conf I get:

libreoffice-still 5.3.6-4
ldd /usr/lib/libreoffice/program/soffice.bin  | grep boost
        libboost_system.so.1.65.1 => /usr/lib/libboost_system.so.1.65.1 (0xb0cd1000)
        libboost_filesystem.so.1.65.1 => /usr/lib/libboost_filesystem.so.1.65.1 (0xb0cb5000)
        libboost_iostreams.so.1.65.1 => /usr/lib/libboost_iostreams.so.1.65.1 (0xb0c98000)

and with testing and community-testing activated I get:

libreoffice-fresh-5.4.2-2
ldd /usr/lib/libreoffice/program/soffice.bin  | grep boost
        libboost_system.so.1.65.1 => /usr/lib/libboost_system.so.1.65.1 (0xb083d000)
        libboost_filesystem.so.1.65.1 => /usr/lib/libboost_filesystem.so.1.65.1 (0xb0821000)
        libboost_iostreams.so.1.65.1 => /usr/lib/libboost_iostreams.so.1.65.1 (0xb0804000)

On the machine with testing and community-testing I get:

libreoffice-still 5.3.6-4
libboost_system.so.1.65.1 => /usr/lib/libboost_system.so.1.65.1 (0xb0c8d000)
        libboost_filesystem.so.1.65.1 => /usr/lib/libboost_filesystem.so.1.65.1 (0xb0c71000)
        libboost_iostreams.so.1.65.1 => /usr/lib/libboost_iostreams.so.1.65.1 (0xb0c54000)

libreoffice-fresh-5.4.2-2
        libboost_system.so.1.65.1 => /usr/lib/libboost_system.so.1.65.1 (0xb0803000)
        libboost_filesystem.so.1.65.1 => /usr/lib/libboost_filesystem.so.1.65.1 (0xb07e7000)
        libboost_iostreams.so.1.65.1 => /usr/lib/libboost_iostreams.so.1.65.1 (0xb07ca000)

All versions work. So I think It's working now with boost 1.65.1.

Offline

#18 2017-11-05 09:35:50

ZeroLinux
Member
Registered: 2017-11-04
Posts: 5

Re: libreoffice

andreas_baumann, thank you

Offline

#19 2017-11-10 12:59:55

bushranger
Member
Registered: 2017-10-31
Posts: 6

Re: libreoffice

I can confirm libreoffice-still 5.3.7-4 also works out of the box.

Just to close the topic of evolution, which I brought up a few posts back. It turned out the problem was a dependency of a dependency of a dependency...
To be precise: evolution -> evolution-data-server ->  libphonenumber -> protobuf.  I ended up building protobuf 3.4.1-1; all went smoothly.  With this, evolution 3.36.2-1 (which I also built, just to be sure) works.  I'd be happy to subject my build of protobuf 3.4.1-1 to wider testing.

Offline

#20 2017-11-10 14:27:43

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

I rescheduled protobuf, let's see if we also need to rebuild evolution then :-)

Offline

#21 2017-11-29 16:43:37

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 710
Website

Re: libreoffice

I see in my local cache:

find ../../archauto32/mirror/ -name libreoffice-still-5.3.7-6*
../../archauto32/mirror/i686/testing/libreoffice-still-5.3.7-6.0-i686.pkg.tar.xz
../../archauto32/mirror/i686/testing/libreoffice-still-5.3.7-6.0-i686.pkg.tar.xz.sig
../../archauto32/mirror/i686/testing/libreoffice-still-5.3.7-6.1-i686.pkg.tar.xz
../../archauto32/mirror/i686/testing/libreoffice-still-5.3.7-6.1-i686.pkg.tar.xz.sig
../../archauto32/mirror/i686/staging/libreoffice-still-5.3.7-6.0-i686.pkg.tar.xz
../../archauto32/mirror/i686/staging/libreoffice-still-5.3.7-6.0-i686.pkg.tar.xz.sig

What puzzles me here, why is staging older than testing?

Offline

#22 2017-11-29 18:08:13

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

-6.1 is current and is not in stable (nothing is, as a matter of fact).
So I guess, you forgot --delete option on rsyncing or it's not working properly.

Offline

#23 2017-11-29 18:37:58

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 710
Website

Re: libreoffice

yeah, stupid me. :-)

Offline

#24 2017-11-29 18:43:27

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 710
Website

Re: libreoffice

So, I tested libreoffice-still-5.3.7-6.1, reported it (Via the reporting mail mechanism, I mean). When does it get pushed to core?
I mean, to get finally rid of the icu 59 issues.

Offline

#25 2017-11-29 21:52:09

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 421

Re: libreoffice

There was an open bugreport for libreoffice-still, so it would not be marked as 'tested' and therefor not moved to stable.

I switched the bug report to "for stable package", so it is now marked as "tested" - however, there are still some dependent/ing packages untested:

[slave@archlinux32-buildmaster ~]$ why-dont-you stabilize libreoffice-still
The following packages are dependent on "libreoffice-still", but cannot be stabilized:
btfs.dc7cb6f695e1b29320048a19a5dba42e48315100.f3155c8b662cefa706f54be2337f47e6b21ec083.community (not tested yet for 2 days)
curl.00be7741817b235c0f0847f95ad429dba8abaaf4.ab77876d700e89b0d58b20ff7f5922703e0bf44c.core (not tested yet for 0 days)
darkhttpd.5572cefa22af18ab6664a357263c9238dc5b2852.ab77876d700e89b0d58b20ff7f5922703e0bf44c.community (not tested yet for 0 days)
fcitx-cloudpinyin.9c036083e465974a4d7038e0dd6806a36a74cd4f.ab77876d700e89b0d58b20ff7f5922703e0bf44c.community (not tested yet for 1 days)
git-review.be5547e739ec0d41aad0b028cb49411e48773410.fffd6dcc82f431ca4fa6ccd6ee9714bd4995ceb4.extra (not tested yet for 3 days)
git.a6d036f197ba86d45bd699b19d864e27bd70b042.ab77876d700e89b0d58b20ff7f5922703e0bf44c.extra (not tested yet for 0 days)
gitlab-gitaly.47680321213f94d7a1d549bfb89b6bbc3914a3b1.fffd6dcc82f431ca4fa6ccd6ee9714bd4995ceb4.community (not tested yet for 3 days)
gitlab-runner.a89d86bcb1e9844f141beee0ee2e8b116e45c77a.fffd6dcc82f431ca4fa6ccd6ee9714bd4995ceb4.community (not tested yet for 3 days)
gitlab-shell.a89d86bcb1e9844f141beee0ee2e8b116e45c77a.fffd6dcc82f431ca4fa6ccd6ee9714bd4995ceb4.community (not tested yet for 3 days)
gitlab-workhorse.1152b153af957b58edcf7a333f78e66acf7e9ea6.fffd6dcc82f431ca4fa6ccd6ee9714bd4995ceb4.community (not tested yet for 3 days)
gitlab.25438f8eb71bcb76051fc116f9f2f22dbb2ad57d.5fb6d7acdf2b16b5d05522f1009328b4ffc1a454.community (not tested yet for 3 days)
libcurl-compat.2d5501993cb46e52e40b6aeb2edf546f99a43cb5.ab77876d700e89b0d58b20ff7f5922703e0bf44c.community (not tested yet for 0 days)
libcurl-gnutls.2d5501993cb46e52e40b6aeb2edf546f99a43cb5.ab77876d700e89b0d58b20ff7f5922703e0bf44c.community (not tested yet for 0 days)
libwps.937ba4e40bf4698456ef5bd9bdb50b6f3815b4e8.ab77876d700e89b0d58b20ff7f5922703e0bf44c.extra (not tested yet for 0 days)
metasploit.65da557c6fe71d2cc6648eba801be5f306056627.f3155c8b662cefa706f54be2337f47e6b21ec083.community (not tested yet for 2 days)
pacredir.41ee0eb4fc21f36acc39bbb515709f58a8d937a4.ab77876d700e89b0d58b20ff7f5922703e0bf44c.community (not tested yet for 1 days)
passenger.985ec2717b51e8e3afa5dd58c517563448cd19af.ab77876d700e89b0d58b20ff7f5922703e0bf44c.community (not tested yet for 0 days)
shards.f89437cec8eadc4ac13b7e80a64b02d54d9a8af3.7f968a875a8c7b353ddcefee095c792fc24752db.community (not tested yet for 5 days)
strongswan.b97a57a8daf76c15b976ca8f0b2e3ffa8241b879.a03b20ef399a363b5f31b34c3d33d34eb83f7280.community (not tested yet for 7 days)

Should I boldly mark all those as tested, so it can be moved?

Offline

Board footer

Powered by FluxBB