LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   I can't install google-chrome on Slackware 13.1 for x86_64 (http://www.linuxquestions.org/questions/slackware-14/i-cant-install-google-chrome-on-slackware-13-1-for-x86_64-a-820435/)

alculquicondor 07-17-2010 04:21 PM

I can't install google-chrome on Slackware 13.1 for x86_64
 
After I downloaded the required files from http://slackbuilds.org/repository/13...google-chrome/
I did this:
Code:

root@shekatsu8er:/home/alculquicondor/google-chrome# ls                 
README                                  google-chrome.SlackBuild  google-chrome.info
google-chrome-stable_current_amd64.deb  google-chrome.SlackBuild~  slack-desc
root@shekatsu8er:/home/alculquicondor/google-chrome# ./google-chrome.SlackBuild
ar: google-chrome-stable_current_i386.deb: No such file or directory

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
ar: /home/alculquicondor/google-chrome/google-chrome-stable_current_i386.deb: No such file or directory
lzma: (stdin): File format not recognized
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
root@shekatsu8er:/home/alculquicondor/google-chrome# ARCH=x86_64 ./google-chrome.SlackBuild
no entry control.tar.gz in archive

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
no entry data.tar.lzma in archive
lzma: (stdin): File format not recognized
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

Could anybody install it on x86_64? I need the control.tar.gz? Where can I download it?
Thanks

diamondsandrain 07-17-2010 04:25 PM

google-chrome-stable_current_i386.deb: No such file or directory

Did you download the software as well or just the slackbuild? You need both. The link to the software is on the same page.

And yes, that slackbuild works perfectly for me on x86_64

You may also need to edit the slackbuild to tell it that you are running x86_64. It seems to be searching for the 32 bit version.

Sorry about that. I didn't read all the way to to bottom. I thought that was just the script going on doing things after the initial error.

"ar p google-chrome-${RELEASE}_current_${DEBARCH}.deb control.tar.gz"

Seems to be looking in the archive for the control.tar.gz. I was able to get it working just now on my system. Perhaps this was a corrupted download.

diamondsandrain 07-17-2010 05:04 PM

Yes, Ark is capable of opening the .deb file. There is a control.tar.gz inside it in the version I have downloaded.

hoodooman 07-17-2010 05:32 PM

Install sbopkg and install the package from there.http://www.sbopkg.org/

diamondsandrain 07-17-2010 06:51 PM

Quote:

Originally Posted by hoodooman (Post 4036648)
Install sbopkg and install the package from there.

There is a reason that I don't use sbopkg for chrome. Its because I had already installed chrome before I had ever heard about sbopkg and for some reason it was always telling me that the version of chrome that I had was newer than the one in the repos.

The version I had was pulled from slackbuilds.org and built that way. Is there some reason that is the case?

slakmagik 07-17-2010 08:47 PM

google-chrome sources don't have versioned filenames and the slackbuild extracts the information in an atypical way so sbopkg didn't initially deal with that correctly but it should work now, as you note in your edit.

alculquicondor 07-18-2010 01:09 AM

You were right. The package was corrupt. Thanks.
Althought, the script didn't recognized my arch, so I have to put, as before:
Code:

# ARCH=x86_64 ./google-chrome.SlackBuild


All times are GMT -5. The time now is 11:02 PM.