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.
I'm not sure what is causing all of these little quirks in my systems as of late, but I wanted to see if anyone has had an issue with this build, something similar, or could try to build it and see what their results are. I'll explain below.
I have a desktop that has had slackware on it for about 9 months now. No real issues. It has had owncloud-client installed via sbopkg and upgraded regularly for about 4 months now. Once again, no issues. However, upon trying to upgrade to 1.8.4 from 1.8.3 I get a build failure stating:
rmdir: failed to remove '/tmp/sbopkg.Z4DMJh/package-owncloud-client/usr/man': No such file or directory
If I comment out the line:
rmdir $PKG/usr/man
it builds fine. This also occurs on a brand new (to me) laptop with a fresh install of slackware and trying to install 1.8.4 (not an upgrade). I get the same error if I download the source and slackbuild and run the script manually without sbopkg.
Can anyone recreate this issue? The maintainer and I have been emailing back and forth and it seems that he can't recreate the issue on his machine. It's strange that I have 2 different machines with the same error using 2 separate methods on each.
I had the same problem using sbopkg: the build failed with error
Code:
rmdir: failed to remove '/tmp/SBo/package-owncloud-client/usr/man': No such file or directory
The same fix worked for me, I just commented out the line:
Code:
rmdir $PKG/usr/man
near the bottom of owncloud-client.Slackbuild and built and installed the package without using sbopkg.
Cheers,
Michael
PS: this is on a relatively new installation of slackware64-current, and it was an upgrade to the earlier version which I had installed using sbopkg from the 14.1 SBo repository.
Last edited by michaelslack; 08-31-2015 at 11:49 PM.
Reason: Added PS note
Well, at least there are 2 of us. The line to create that folder and the line to remove it was added to the slackbuild in its latest version. I haven't updated one of my machines and can look at my locally stored version of the slackbuild and compare it with the newest version.
You can also check /var/log/packages/owncloud-client-version_SBo to see what folders were created and on my machine that WAS upgraded, I don't have /usr/man being created when I comment out the line to remove it. Which makes sense, considering the error. So not sure what isn't working as far as our machines go that is different to the maintainers. Not new to linux, but new to build scripts so I'm going to take some time and learn about what is going on between the two.
I get it too, everyone should since the package doesn't have any manpages, not to mention it doesn't even have usr/man... Just remove the line.
Edit: If you want to learn more about slackbuild scripts, try spending some time studying these. http://slackbuilds.org/templates/
Updating packages ahead of SBo is also a good way to learn how things work.
FWIW, owncloud-client 2.0.1 is out. "It is almost the same as 2.0.0 except a one line fix that is needed for doing special branding options." [source], so it really doesn't need a further update at SBo.
Now that the new owncloud-client is on its way, I will push owncloud-server 8.1.1 or 8.1.2 to SBo (depending on when 8.1.2 is announced). 8.1.x needs owncloud-client 1.8 or newer. Please read the README for information about "trusted domains" configuration.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.