SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
sbopkg -c indicates there is a new version of LibreOffice available. I ran `sqg -p libreoffice` to build the queue, then ran `sbopkg -i LibreOffice`. I got the following messages:
Code:
Found jdk-8u121-linux-x64.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
MD5SUM check for jdk-8u121-linux-x64.tar.gz ... FAILED!
Expected: 91972fb4e753f1b6674c2b952d974320
Found: 81ee08846975d4b8d46acf3b6eddf103
Do you want to use the downloaded jdk source:
jdk-8u121-linux-x64.tar.gz in /var/cache/sbopkg?
You can choose among the following options:
- (Y)es, keep the source and continue the build process;
- (N)o, delete the source and abort the build process;
- (R)etry download and continue the build process; or
- (A)ttempt to download from third party source repository.
(Y)es, (N)o, (R)etry, (A)lternative ?: Y
Keeping the source and continuing.
Building package for jdk...
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
jdk:
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?:
What does this mean? is the repo version of jdk corrupt?
more info after further investigation ...
The /var/cache/sbopkg/jdk-8u121-linux-x64.tar.gz file isn't a gzip file. It's an html file with the following content:
Code:
Sorry!
In order to download products from Oracle Technology Network you must agree to the OTN license terms.
Be sure that...
Your browser has "cookies" and JavaScript enabled.
You clicked on "Accept License" for the product you wish to download.
You attempt the download within 30 minutes of accepting the license.
From here you can go...
So, how then does one retrieve a file for which license terms must be agreed to?
You must Agree to Oracle's download agreement before this can be downloaded.
This means you have to use a web browser to download it. Sorry wget folks.
This problem with using wget for downloading the Oracle JDK is why I've changed the requirement in LibreOffice (not libreoffice being discussed here) to openjdk (openjdk8 works too). These don't need user intervention via a web browser so are great for automated build systems.
I later did test builds of all SBo packages requiring jdk but substituting openjdk8; all SlackBuilds except office/ganttpeoject built perfectly well using openjdk8. I'd recommend all maintainers of SlackBuilds requiring jdk to satisfy for themselves that openjdk8 is OK and perhaps change their SlackBuilds' requirement.
mfoley, you need to be very careful. 'libreoffice' and 'LibreOffice' are two different SlackBuilds. 'libreoffice' packages the official upstream binary, whereas 'LibreOffice' builds from source.
So, if what you really did is exactly what you wrote:
Quote:
Originally Posted by mfoley
I ran `sqg -p libreoffice` to build the queue, then ran `sbopkg -i LibreOffice`
then you built a queue for one package, then ran a different build. You need to be consistent. You probably want 'libreoffice'.
This problem with using wget for downloading the Oracle JDK is why I've changed the requirement in LibreOffice (not libreoffice being discussed here) to openjdk (openjdk8 works too). These don't need user intervention via a web browser so are great for automated build systems.
Yikes!!!! LibreOffice and libreoffice are different?!! I thought those package names were case insensitive. Why is there a LibreOffice and a libreoffice? How do I get libreoffice off my system? Running `slackpkg remove libreoffice` gives me "The file(s) libreoffice can't be removed - package not installed." Yet it gave me a success message after the installation.
I'd also like to get the jdk off my system, but:
Code:
# ls /var/log/packages/ | grep jdk
jdk-8u121-x86_64-1_SBo
# slackpkg remove jdk-8u121-x86_64-1_SBo
Looking for jdk-8u121-x86_64-1_SBo in package list. Please wait... DONE
The file(s) jdk-8u121-x86_64-1_SBo can't be removed - package not installed.
Yikes!!!! LibreOffice and libreoffice are different?!! I thought those package names were case insensitive. Why is there a LibreOffice and a libreoffice?
As is normal with Unix, case is important. If you read the READMEs for both, your question about the difference will be answered.
Quote:
Originally Posted by mfoley
How do I get libreoffice off my system? Running `slackpkg remove libreoffice` gives me "The file(s) libreoffice can't be removed - package not installed." Yet it gave me a success message after the installation.
You created a build queue for libreoffice but then attempted to install LibreOffice. In the end, nothing was installed.
Quote:
Originally Posted by mfoley
I'd also like to get the jdk off my system, but:
Code:
# ls /var/log/packages/ | grep jdk
jdk-8u121-x86_64-1_SBo
# slackpkg remove jdk-8u121-x86_64-1_SBo
Looking for jdk-8u121-x86_64-1_SBo in package list. Please wait... DONE
The file(s) jdk-8u121-x86_64-1_SBo can't be removed - package not installed.
Have I trashed my system?
I think what you did should work unless the package is corrupt, but maybe try either of these and see if there's any difference:
As is normal with Unix, case is important. If you read the READMEs for both, your question about the difference will be answered.
Actually, I've read the READMEs for both and it doesn't tell me the difference -- at least as far as I can understand. In fact the page for libreoffice references LibreOffice and 5.3.2 throughout. So, not obvious -- at least to me.
Quote:
You created a build queue for libreoffice but then attempted to install LibreOffice. In the end, nothing was installed.
OK, I can live with that explanation.
Quote:
I think what you did should work unless the package is corrupt, but maybe try either of these and see if there's any difference:
which appeared to want to remove ALL packages in my system. I did the CTRL-C as it was working on the first one and I reinstalled GConf-3.2.6-x86_64-3. So, that was not a good idea. I guess I'll not worry about it, though the java jdk is huge and if I don't need it it would be nice to get rid of it, but apparently slackpkg doesn't know how to do that. I now have several jdk's installed:
Mystery solved. I had to unblacklist SBo packages for the slackpkg remove to work.
Just as an FYI, you don't need to use slackpkg to remove packages. You can simply type removepkg jdk to remove it. slackpkg is an online aware component of pkgtools (that was added into official Slackware in 12.2, but was available in extra/ since 9.1), but it really shines in ensuring your Slackware is up-to-date with the mirrors. While it does incorporate other aspects of pkgtools (installing and removing packages), personally, I stick to the singular scripts (installpkg and removepkg) most of the time because it won't be affected by any blacklist you have for slackpkg.
REQUIRES contains a space-separated list of all required build-time and run-time dependencies, each named exactly as listed on the SlackBuilds.org site. It should not contain anything that is part of Slackware itself. The content of REQUIRES should only be first level dependencies (i.e. no deps of deps).
Optional dependences should not be listed in REQUIRES - they should still be listed in the README (and preferably will list what feature the optional dependency provides). If the maintainer feels that a dependency is, while techically optional, strongly recommended enough to require it, that is generally acceptable - we'll retain veto power on that but we expect that it won't be an issue.
So although you are correct that jdk (openjdk, openjdk8) is not necessary to build libreoffice from the SlackBuild (which just repackages existing binaries), it is still there because it is a potential runtime requirement. Perhaps your particular usage of libreoffice doesn't need it but who's to say whether your usage is typical. It's the maintainer's decision as to whether a techically (sic) optional but strongly recommended requirement is included.
I've told you this before, but apparently you haven't listened. The only required dependency for libreoffice is perl-archive-zip. Everything else should be left up to the user's discretion, especially proprietary software like jdk. So since you will not correctly inform users I guess I can do it for you...
Also, the precompiled binary libreoffice package will complain if jdk is not installed, but will still work fine. Willy was kind enough to provide this in his script so users can disable it if desired.
Code:
# If you want to disable java support by removing executable permissions
# form LibreOffice's java loader (this will not affect other apps), set this
# variable to "YES" Default is "NO"
DISABLE_JAVA=${DISABLE_JAVA:-NO}
I've told you this before, but apparently you haven't listened. The only required dependency for libreoffice is perl-archive-zip. Everything else should be left up to the user's discretion...
No, everything on the REQUIRES line is left to the maintainer's discretion. That's the SBo policy. If you don't like it, then maybe take it up on the mailing list and see if you can get some admins on board who might be willing to change it.
As a maintainer, you are able to add optional dependencies is the REQUIRES section if you feel like the software should have the features it provides. It is up to users to remove any dependencies they don't want (just like it is up to them to add features based on flags and/or additional dependencies).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.