My thoughts on Slackware, life and everything

Tag: libreoffice (Page 4 of 20)

Chromium and LibreOffice updates

Due to the Corona (COVID-19) crisis, Google decided to postpone the introduction of Chromium 81 to the stable channel. Understandably due to the challenges created by sending most developers home for their own safety and protection, which is a cause for less efficient work schedules.
Instead, there is an increased focus on addressing security related issues in Chromium 80 and releasing those in rapid succession. After all, any crisis attracts the worst of humankind to mess with the more gullible part of the population and browser based phishing and hack attempts are on the rise.

And so, yesterday there was another version upgrade, and I built the new chromium packages for Slackware 14.2 and -current already. The chromium-80.0.3987.149 release can be downloaded from any mirror – or upgraded using slackpkg/slackpkg+ if you use that.

In addition, new LibreOffice packages are available for Slackware -current.

You’ll get the latest and greatest ‘fresh’ release of 6.4.2 and unfortunately, no new packages for Slackware 14.2. I am unable to compile the 6.3 or 6.4 releases on the stable version of Slackware due to outdated/obsoleted libraries.

Note: among the packages for LibreOffice that are targeting Slackware-current, you will find a “libreoffice-kde-integration” package which adds Qt5 and KDE5 (aka Plasma5) support to the LibreOffice suite.
If you run Slackware-current but do not have KDE5 packages installed at all, don’t worry. LibreOffice will work great – the KDE integration package just will not add anything useful for you. On the other hand, if you have Plasma5 installed you will benefit from native file selection dialog windows and other integration features. And even if you do not have Plasma5 but you do have Qt5 installed, then you will be able to run LibreOffice with Qt5 User Interface elements instead of defaulting to GTK3.

If you want to compile LibreOffice 6.4.2 packages yourself using my SlackBuild script, then be aware that by default the KDE5 support is disabled. You will have to set the value of the script parameter “ADD_KDE5” to “YES”. Additionally you will have to install the packages that this functionality depends on otherwise the compilation will fail.
Read the ‘README.kde5‘ file in the source directory for the list of packages you’ll need. All of the required packages can be  found in my ‘ktown’ repository: https://slackware.nl/alien-kde/current/latest/

Enjoy! Eric

LibreOffice 6.3.4 packages for Slackware-current

After a recent upgrade of the ‘boost’ package in slackware-current my LibreOffice package was in need of a refresh.
I do of course offer a ‘boost-compat‘ package in my own repository to prevent breakage of the 3rd-part applications that have a boost dependency, but a newer release of LibreOffice was available anyway.
So I compiled LibreOffice 6.3.4 for Slackware -current and uploaded these packages to my repository.

Note that the packages for LibreOffice in my repository, do contain “libreoffice-kde-integration” for Slackware -current, containing Qt5 and KDE5 (aka Plasma5) support. On the other hand, the packages I compile for Slackware 14.2 do not contain “libreoffice-kde-integration” any longer.
If you run Slackware-current but do not have KDE5 packages installed at all, don’t worry. LibreOffice will work great – the KDE integration package just will not add anything useful for you. On the other hand, if you have Plasma5 installed you will benefit from native file selection dialog windows and other integration features. And even if you do not have Plasma5 but you do have Qt5 installed, then you will be able to run LibreOffice with Qt5 User Interface elements instead of defaulting to GTK3.

If you want to compile Libreoffice 6.3.4 packages yourself using my SlackBuild, then be aware that by default the KDE5 support is disabled. You will have to set the value of the script parameter “ADD_KDE5” to “YES”. Additionally you will have to install the packages that this functionality depends on otherwise the compilation will fail.
Read the ‘README.kde5‘ file in the source directory for the list of packages you’ll need. All of them can be  found in my ‘ktown’ repository: https://slackware.nl/alien-kde/current/latest/

Enjoy! Eric

New LibreOffice packages for Slackware 14.2 and -current

I uploaded the latest releases of LibreOffice for Slackware 14.2 and -current.

On Slackware 14.2 you can enjoy the stable 6.2.8 version, this is the last release in the 6.2 series. For Slackware-current I went with the latest and greatest ‘fresh’ release of 6.3.3 which became available last week.

Note that the packages for LibreOffice in my repository, do contain “libreoffice-kde-integration” for Slackware -current, containing Qt5 and KDE5 (aka Plasma5) support. On the other hand, packages for Slackware 14.2 do not contain “libreoffice-kde-integration” any longer.
If you run Slackware-current but do not have KDE5 packages installed at all, don’t worry. LibreOffice will work great – the KDE integration package just will not add anything useful for you. On the other hand, if you have Plasma5 installed you will benefit from native file selection dialog windows and other integration features. And even if you do not have Plasma5 but you do have Qt5 installed, then you will be able to run LibreOffice with Qt5 User Interface elements instead of defaulting to GTK3.

If you want to compile Libreoffice 6.3.2 packages yourself using my SlackBuild, then be aware that by default the KDE5 support is disabled. You will have to set the value of the script parameter “ADD_KDE5” to “YES”. Additionally you will have to install the packages that this functionality depends on otherwise the compilation will fail.
Read the ‘README.kde5‘ file in the source directory for the list of packages you’ll need. All of them can be  found in my ‘ktown’ repository: https://slackware.nl/alien-kde/current/latest/

Enjoy! Eric

LibreOffice 6.2.7 packages available for Slackware 14.2

There was a recent update in my repository of LibreOffice packages, but that libreoffice-6.3.2 was just for slackware-current.

There’s a recent release in the LibreOffice 6.2 stable series as well (ok… five weeks ago, not that recent…), and so I decided to use my build box’s free weekend to come up with packages for LibreOffice 6.2.7.
This release has a security improvement over previous versions, in that it will popup a warning to the user if a document tries to run an embedded script (similar to existing warning mechanism for embedded macros).

As you may know, the Document Foundation advises the 6.2.x series for use in production environments while the 6.3.x series is targeted at technology enthousiasts. Precisely why I have 6.3.x in the repository for -current and 6.2.x will be available for users of our stable Slackware 14.2.

Note: I am no longer including support for KDE4. The “libreoffice-kde-integration” package is no longer available for the 6.2.x releases in my repository and you should “removepkg” the older version if you have that installed. The KDE4 support in LibreOffice 6 has been broken for a while and your Office applications will run great on KDE4 without that “KDE integration”. The LibreOffice UI will be based on GTK3 widgets instead and KDE4’s theming engine will make that its User Interface blends in properly.
For the libreoffice-6.3 series and onwards, I will again build ‘libreoffice-kde-integration’ sub-packages but then targeting Qt5 and KDE5. That works really well.

Enjoy! Eric

LibreOffice 6.3.2 for Slackware-current – and how to deal with “Shared library .so-version bump”

The recent update in slackware-current of the icu4c and boost packages caused some 3rd-party package breakage. The new versions of icu4c and boost come with incompatible library ABI changes.

Let me first elaborate a bit on the strategies that are available to a Slackware user on how to deal with incompatible library updates in -current.

One of the reasons people are wary of installing and running Slackware-current is the fact that at any given moment, distro updates can break 3rd-party packages (i.e. packages you have installed that are not part of the Slackware distribution itself). Slackware-current is in constant flux, it is our development environment, and software versions can make sudden jumps with unexpected consequences.

Big tip: before running any update on a slackware-current system, first check the ChangeLog.txt and scan the updates since your previous upgrade for the text “Shared library .so-version bump.” which is another way of saying “incompatible ABI change”.
If this text accompanies a package update you can be pretty certain that some 3rd-party packages that depend on it will stop working. And if that particular package is boost, icu4c or poppler, expect massive breakage. The safest approach in a case like this, is: wait with upgrading your Slackware-current; check for packages that have a dependency on the package with the ABI breakage: and track the 3rd-party repositories for updates that address the ABI breakage.

There is another strategy- one which allows you to upgrade to the latest -current while avoiding broken packages. That is to keep the older libraries on your system – the libraries your 3rd-party packages are depending on. You can simply extract these older libraries from the previous version(s) of the upgraded Slackware package. Darren Austen and I worked together to create a package repository containing historical Slackware-current packages (32bit, 64bit official packages and my own multilib archive). See https://slackware.uk/cumulative/ if you are in need of older package versions.

And in the special case of incompatible icu4c, boost and poppler updates, the easiest (short-term) workaround is to install my icu4c-compat, boost-compat and poppler-compat packages. Essentially, these convenience packages wrap the libraries of several older (original Slackware) icu4c, boost and poppler packages.
Applications that depend on these older libraries will keep on running and in the meantime you can wait for the 3rd-party packager to recompile the affected packages (or recompile yourself at your leisure). I update these packages immediately after updates to their Slackware originals. The process takes almost no time, compared with recompiling all the broken stuff.
NOTE: These ‘compat’ packages do not replace Slackware’s own icu4c, boost and poppler packages! They should be installed in parallel.

Libreoffice

The most obvious package breakage in my own repository is of course LibreOffice. It is a big package and many people do not want to recompile this themselves. A good decision, because the LibreOffice package would not compile against the new icu4c 65.1 and I needed to find the cause and create a patch first.

Since I had to compile new packages anyway, I went for the latest 6.3.2 release of LibreOffice which was announced two weeks ago.

Note that the new packages for LibreOffice 6.3.2 in my repository, do contain “libreoffice-kde-integration”, containing Qt5 and KDE5 (aka Plasma5) support.
If you do not have KDE5 packages installed at all, don’t worry. LibreOffice will work great – the KDE integration package just will not add anything useful for you. On the other hand, if you have Plasma5 installed you will benefit from native file selection dialog windows and other integration features. And even if you do not have Plasma5 but you do have Qt5 installed, then you will be able to run LibreOffice with Qt5 User Interface elements instead of defaulting to GTK3.

If you want to compile Libreoffice 6.3.2 packages yourself using my SlackBuild, then be aware that by default the KDE5 support is disabled. You will have to set the value of the script parameter “ADD_KDE5” to “YES”. Additionally you will have to install the packages that this functionality depends on otherwise the compilation will fail.
Read the ‘README.kde5‘ file in the source directory for the list of packages you’ll need. All of them can be  found in my ‘ktown’ repository: https://slackware.nl/alien-kde/current/latest/

Enjoy! Eric

« Older posts Newer posts »

© 2024 Alien Pastures

Theme by Anders NorenUp ↑