Printing in 64-Bit Google-Chrome fails
Richard Shaw
hobbes1069 at gmail.com
Wed Feb 2 02:22:06 UTC 2011
On Tue, Feb 1, 2011 at 8:15 PM, David <dgboles at gmail.com> wrote:
> On 2/1/2011 9:00 PM, Richard Shaw wrote:
>> On Tue, Feb 1, 2011 at 6:40 PM, Genes MailLists <lists at sapience.com> wrote:
>>> All of yours are not updated (they look way behind .. i mean way way
>>> behind) ..this is the current unstable I have - just letting yum update
>>> from the google repo:
>>>
>>> google-chrome-unstable-10.0.648.6-72589.x86_64
>>
>> Yeah, after seeing your previous email I did some researching but
>> didn't find anything wrong with my repo... I just did a "yum clean
>> all" and I still see the same versions.
>>
>> My /etc/yum.repos.d/google.repo:
>> [google]
>> name=Google - i386
>> baseurl=http://dl.google.com/linux/rpm/stable/i386
>> enabled=1
>> gpgcheck=1
>> gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
>>
>> [google-testing]
>> name=Google Testing - i386
>> baseurl=http://dl.google.com/linux/rpm/testing/i386
>> enabled=1
>> gpgcheck=1
>>
>> [google64]
>> name=Google - x86_64
>> baseurl=http://dl.google.com/linux/rpm/stable/x86_64
>> enabled=1
>> gpgcheck=1
>> gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
>>
>>
>>> I'd force install fresh if I were you. Also I did not realized they
>>> could be installed on top of each other interesting .. I only have
>>> unstable. I thought they all ended up in same place (/opt/google/chrome).
>>
>> I've only got the one installed, the rest are just available packages.
>>
>> Richard
>
>
> Go to the three links. Those repos are empty.
No, not empty, just not directly browse-able.
Output from "yum repolist"
google Google - i386 5
google-chrome64 Google Chrome 3
google-testing Google Testing - i386 1
google64 Google - x86_64 4
The numbers on the end are the number of packages in the repo.
I do get updated packages from time to time, but they seem to lag
horribly. Anyway I found the problem.
My links go to the general google repo, not the chrome specific one.
What's strange is if you do a google search on "google yum repo", the
links you find tell you to use the information just like I have.
I downloaded directly from the google website the latest google-chrome
and opened the RPM archive and found the shell script that adds the
chrome specific repo. Now I'm showing the newer software packages.
# yum list google-chrome*
Loaded plugins: changelog, presto, refresh-packagekit, remove-with-leaves, rpm-
: warm-cache
Installed Packages
google-chrome-beta.x86_64 8.0.552.200-65749 @google64
Available Packages
google-chrome-beta.i386 8.0.552.200-65749 google
google-chrome-beta.x86_64 9.0.597.84-72991 google-chrome64
google-chrome-stable.i386 7.0.517.44-64615 google
google-chrome-stable.x86_64 8.0.552.237-70801 google-chrome64
google-chrome-unstable.i386 9.0.576.0-65344 google
google-chrome-unstable.x86_64 10.0.648.11-73099 google-chrome64
I wonder if Google knows about this discrepancy?
Thanks,
Richard
More information about the users
mailing list