Hi,

I try to install office/libreoffice from Sbopkg package browser and I get following error:

(P)roceed or (Q)uit?: P


Processing libreoffice

libreoffice:
libreoffice not found in /var/cache/sbopkg.
--2013-06-15 14:26:13-- http://download.documentfoundation.o...x86_rpm.tar.gz
Resolving download.documentfoundation.org (download.documentfoundation.org)... 178.63.91.70
Connecting to download.documentfoundation.org (download.documentfoundation.org)|178.63.91.70|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-06-15 14:26:13 ERROR 404: Not Found.


libreoffice:
Would you like to continue processing the rest of the
queue or would you like to abort? If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:

office/libreoffice SlackBuild scripts is bad ? Need update ?

Thanks.

This happens a lot with Libreoffice
Just download the newest version, edit the build script and roll it yourself.

x86
http://www.libreoffice.org/download/...x86&lang=en-US

Email the maintainer of the script and ask him to update it. Or, grab a package from Eric's repository:

http://slackware.com/~alien/slackbuilds/libreoffice/

Hi,

You can look at Alien_Bob's;Please try the mirrors whenever available.

I will second (third?) getting LibreOffice from Alien Bob. It worked very smoothly for me when the one from Slackbuilds.org did not.

I'm very happy with Open Office, which is very good for production use on my client's desktops and workstations.

I just setup a brand new Slackware package repository on my company's website:

http://www.microlinux.fr/slackware/

Packages for 32-bit Slackware are here:

http://www.microlinux.fr/slackware/MLED-14.0/pkg/

And here's the link for Slackware64 packages:

http://www.microlinux.fr/slackware/MLED-14.0/pkg64/

The openoffice package is the latest Apache Open Office 3.4.1, which I also use for daily work, and I'm very happy with it.

The openoffice-langpack package currently contains only french and german translations, but it's easy to add other languages. Just run the build script:

http://www.microlinux.fr/slackware/M...fice-langpack/

You may have to comment out the md5sum check though, otherwise the script will exit.

Cheers,

Niki

All I ever do is download the gzipped OpenOffice rpm's from Apache, unzip and untar, do a 'rpm2tgz ./*' and then a pkgtool install. Always works perfectly for me.

> Old Today, 04:12 AM #6
>
> kikinovak

Hi kikinovak,

>
> Member
>
>
> Registered: Jun 2011
> Location: Montpezat (South France)
> Distribution: Slackware, Slackware64
> Posts: 817
> Rep: Reputation: 305 Reputation: 305 Reputation: 305 Reputation: 305
>
> I'm very happy with Open Office, which is very good for production use
> on my client's desktops and workstations.
>

Apache OpenOffice (AOO aka) is a great office suite.

But considering AOO to wear more than a year without updates and LibreOffice (aka LO) has been updated during this time, you do not think today is more convenient to use LO instead of AOO least until released version 4.0 AOO?

See you.

I may be wrong, but I'm naturally suspicious of software with a frantic release cycle. More often than not, new features get added in before some basic bugs get ironed out. Please ignore the flamewar potential, but this is one of the main reasons I prefer Xfce over KDE, Firefox ESR over Firefox, and Apache Open Office over Libre Office.

Libre Office has one particularly nasty bug in "Special Copy/Paste". I recently tried to special-copy a very long stream-of-consciousness paragraph from an XHTML page into an ODT document. The operation made Libre Office crash... and Apache Open Office handled it correctly. Earlier this year I deployed Libre Office at one of my client's networks. It must be said that this client uses many advanced features of the office suite. Folks reported a series of bizarre bugs, so I finally reverted all client PCs to Apache Open Office, and everything works fine now.

I have a very pragmatic approach in my choice of applications. I prefer those that JustWork(tm).

> Old Today, 11:34 AM #9
>
> kikinovak

Hi kikinovak,

>
> Member
>
>
> Registered: Jun 2011
> Location: Montpezat (South France)
> Distribution: Slackware, Slackware64
> Posts: 818
> Rep: Reputation: 305 Reputation: 305 Reputation: 305 Reputation: 305
>
> I may be wrong, but I'm naturally suspicious of software with a frantic
> release cycle. More often than not, new features get added in before
> some basic bugs get ironed out. Please ignore the flamewar potential,
> but this is one of the main reasons I prefer Xfce over KDE, Firefox ESR
> over Firefox, and Apache Open Office over Libre Office.
> Libre Office has one particularly nasty bug in "Special Copy/Paste". I
> recently tried to special-copy a very long stream-of-consciousness
> paragraph from an XHTML page into an ODT document. The operation made
> Libre Office crash... and Apache Open Office handled it correctly.
> Earlier this year I deployed Libre Office at one of my client's
> networks. It must be said that this client uses many advanced features
> of the office suite. Folks reported a series of bizarre bugs, so I
> finally reverted all client PCs to Apache Open Office, and everything
> works fine now.
> I have a very pragmatic approach in my choice of applications. I prefer
> those that JustWork(tm).
>

OK, thanks for your vision on that question about AOO vs LO actually.

See you.

> Old 06-15-2013, 08:36 AM #2
>
> slackass

Hi slackass,

>
> Member
>
>
> Registered: Apr 2006
> Location: SE Texas
> Distribution: Slack64-C ML
> Posts: 860
> Rep: Reputation: 74
>
> This happens a lot with Libreoffice
>

Why this happens a lot with Libreoffice ?

Thanks, see you.

You seem to be reading and responding to LQ posts using a mail client, therefore you are probably missing a lot of context.
He was referring to the fact that LibreOffice download URLs are only working for the most current version. When a new version of LibreOffice is released, download URLs for older versions stop working because the tarballs are removed from the server.

Eric

Because libreoffice keeps only one stable version download link at the time
When they update libreoffice, let's say 4.0.2 -> 4.0.3, previous link /stable/4.0.2 disappears and new link /stable/4.0.3 appears. There is a workaround which use alternative download link where they keep every releases (don't be confused with word "old", every release - even newest version - goes there), so you could download it any time. According to slackbuild's description it should be.
but last time I checked /old/stable doesn't exist anymore, so alternative link that works now is:
Slackbuild maintainer could simply use the later URL, but given LibreOffice maintainers nature, these links could change any time, so there is no point using them (at least until download URL's became stable).

I simply used the SlackBuild script for 4.0.2 and changed the version number to 4.0.3. Worked like a charm.

Or am I missing something?

No, I use it that way too. There is only one disadvantage to this approach - you have to manually download slackbuild, source package and then run slackbuild script, clean build environment afterwards, etc. With sbopkg and working slackbuilds it's a lot simpler.