|
How you access dropbox?
I tried to install dropbox client got from its office web site. The the packages claim that it need libnautilus-extension package which seems depends on gnome. I know, slack don't have gnome. How you access dropbox? Need to install gnome and libautilus-extension?
Thanks. |
The SlackBuild worked fine for me. In KDE, an icon will appear. http://slackbuilds.org/repository/14.0/network/dropbox/
|
Check out http://slackware.com/~alien/slackbuilds/dropbox-client/
It is my re-packaging of the fedora RPM and does some smart stuff to make it work without Gnome and with Slackware. First time you start the client, it will download the Dropbox daemon automatically. You will end up with a dropbox icon in your system tray. Opening the dropbox directory will work using the desktop environment's default file manager (dolphin in KDE, Thunar in XFCE) Eric |
By installing Alien's client together with the slackbuilds's syncing daemon, it works great! Thanks a lot!
|
I'm getting the following in my attempt to package the dropbox client... am I missing something?
Code:
An installation script was detected in ./install/doinst.sh, but |
does dropbox require multilib?
|
No, I am running it (Alien Bob's) on Slackware64
|
weird... i can't get it to package using the SlackBuild...
|
Builds just fine for me. Any errors? Are you running it as root?
|
Yep, running it as root... bombs shortly after unpacking the rpm with this
Code:
An installation script was detected in ./install/doinst.sh, but |
Strange?
Perhaps the rpm is corrupt. Delete the rpm file(s) from your build directory to force Alien Bob's script to download the needed rpm file. Then run the script again as root (su -). The only other thing I can think of is a permissions problem in /tmp |
Also, there is a lot more output from the SlackBuild than you showed us. Paste the full output so we can havea better look.
Eric |
Ok, so I removed the .rpm to let the script download it fresh and still no go. Permissions on my /tmp are drwxrwxrwt and mounted as
Code:
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,mode=1777,size=4G)Code:
Source 'nautilus-dropbox-1.4.0-1.fedora.x86_64.rpm' not available yet... |
Well I don't see anything out of the ordinary in your post above. I don't put my /tmp on tmpfs, but that should not cause this problem. Just for kicks, I put /tmp on tmpfs using same parameters you have shown. The script run fine.
Have you modified Alien Bob's script? |
I guess you are not running real Slackware then but some derivative distro? OR else you have replaced one or more original Slackware packages with some from another distro?
The rpm2tgz command on your computer creates the toplevel directory "nautilus-dropbox-1.4.0-1.fedora.x86_64/" in the resulting .tgz file. On Slackware however, the resulting .tgz file does not contain "nautilus-dropbox-1.4.0-1.fedora.x86_64/" as toplevel directory. I quickly verified this on Slackware 13.37 and 14.0 and it has not been different in earlier versions either. This is what the rpm2tgz command (which is used in dropbox-client.SlackBuild to extract the Fedora RPM) does on my machine. See the difference? Code:
# rpm2tgz nautilus-dropbox-1.4.0-1.fedora.x86_64.rpm |
Hrmm, I do see the difference between your output and mine... the weird thing is I have no idea why mine would be doing this... I have not touched anything "major" after recently installing 14.0 from scratch. I installed a bunch of packages from slackbuilds.org after rebuilding them... I'll look through the packages when I get home tonight. I know it's hard to figure out what might be affecting this change, but if you or anyone has any ideas why it might be doing this, please chime in.
|
So after seeing the output from AlienBob, I decided to run rpm2tgz directly from the command line to see if I could figure anything with that. Interesting thing is running rpm2tgz from the command produces the exact output listed in AlienBob's post! Running it from the script however, produces the output from mine... what gives?
EDIT: Ok, so I believe I figured out the cause of my issue and here's the lowdown! When AlienBob's script calls rpm2tgz, it passes along the full path and in my case it's a lengthy one, /usr/custom/src/slackware/dropbox/client. Regardless, I've narrowed it down to ANY path containing a directory named 'src'. If that specific directory exists in the path to the rpm then rpm2tgz bombs. Rename that directory to something else and it's fine! I suppose now that I've found the cause I can work around this issue for the time being and will mark this as solved... |
Good catch. See here.
|
| All times are GMT -5. The time now is 03:19 PM. |