Google voice for Linux is out as a Debian package only. Why can’t these people produce RPMs for other distros too? It seems every time I want something it’s not available for openSUSE and no one gives a **** about making a package.
No I am not competent to make RPMs I am just *****ing.
Ubuntu is a polished turd.
I can sense some tension 
Hi
It won’t be built by openSUSE or OBS anyway because it needs libffmpeg
AFAIK, so it will be up to someone like packman to publish…
You could always send an email to
voice-and-video-linux-packager{at}google{dot}com asking?
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.3 (x86_64) Kernel 2.6.34-12-default
up 7 days 2:59, 2 users, load average: 0.12, 0.17, 0.11
GPU GeForce 8600 GTS Silent - Driver Version: 256.44
I am trying to understand what you said. Is it because of a restricted format? If that is the case how do Google, Ubuntu and Debian get around this? I have always previously used PLF and now Packman for get around this stupidity. An openSUSE Skype package exists.
I do not know whaty OBS.
This really doen’t explan why it is so hard to get stuff packaged for openSUSE unless it’s unfounded resentment over the Novel MS deal.
It’s here on the forums…some people apparently have gotten it working. I don’t actually have a webcam so I can’t test but if you get it working please put out an RPM…
Google released Linux video chat plugin for Gmail
Screw Google…just do it ourselves…that’s the Linux way right?
BTW Malcolm I emailed them at that address
Delivery to the following recipient failed permanently:
[email]voice-and-video-linux-packager@google.com[/email]
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.2.1 <voice-and-video-linux-packager@google.com>… Mailbox disabled for this recipient (state 14).
I can’t do it myself that is why I am griping about it. I can’t materailse a package out of thin air and I do not know how to get someone to build it for me and openSUSE can’t apparently due to “restricted format” stupidity. Google voice isn’t the only software this applies too.
gripe, gripe, gripe
Ok…I don’t know who “Malcolm” is but whatever…challenge remains the same. Some people can do it…it’s just a matter of time now…
If they would make a package for Fedora it would satisfy almost every RPM based distro. That’s what a lot of other companies do.
Dang you moaner 
It’s no different that things like chrome, it has
stuff stripped out (ffmpeg) to build on openSUSE, but the one from
google doesn’t…
So far I’m at this building locally…
RPMLINT report:
===============
google-talkplugin.x86_64: W: suse-filelist-forbidden-opt /opt/google is
not allowed for official SUSE packages /opt may not be used by a
distribution. It is reserved for 3rd party packagers
google-talkplugin.src: W: source-or-patch-not-compressed bz2 data.tar.gz
A source archive or file in your package is not compressed using the bz2
compression method (doesn't have the bz2 extension). Files bigger than
100k should be bzip2'ed in order to save space. To bzip2 a patch, use
bzip2. To bzip2 a source tarball, use bznew
google-talkplugin.x86_64: W:
shared-lib-calls-exit /opt/google/talkplugin/lib/libCg.so
exit@GLIBC_2.2.5 google-talkplugin.x86_64: W:
shared-lib-calls-exit /opt/google/talkplugin/lib/libCgGL.so
exit@GLIBC_2.2.5 This library package calls exit() or _exit(), probably
in a non-fork() context. Doing so from a library is strongly
discouraged - when a library function calls exit(), it prevents the
calling program from handling the error, reporting it to the user,
closing files properly, and cleaning up any state that the program has.
It is preferred for the library to return an actual error code and let
the calling program decide how to handle the situation.
google-talkplugin.x86_64: W:
no-soname /opt/google/talkplugin/lib/libCg.so google-talkplugin.x86_64:
W: no-soname /opt/google/talkplugin/lib/libCgGL.so
google-talkplugin.x86_64: W:
missing-PT_GNU_STACK-section /opt/google/talkplugin/libnpgoogletalk64.so
google-talkplugin.x86_64: W:
missing-PT_GNU_STACK-section /opt/google/talkplugin/GoogleTalkPlugin
The binary lacks a PT_GNU_STACK section. This forces the dynamic
linker to make the stack executable. Usual suspects include use of a
non-GNU linker or an old GNU linker version.
google-talkplugin.x86_64: W:
binary-or-shlib-calls-gethostbyname /opt/google/talkplugin/libnpgoogletalk64.so
google-talkplugin.x86_64: W:
binary-or-shlib-calls-gethostbyname /opt/google/talkplugin/GoogleTalkPlugin
The binary calls gethostbyname(). Please port the code to use
getaddrinfo().
2 packages and 0 specfiles checked; 0 errors, 10 warnings.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.3 (x86_64) Kernel 2.6.34-12-default
up 7 days 4:45, 6 users, load average: 0.01, 0.10, 0.12
GPU GeForce 8600 GTS Silent - Driver Version: 256.44
In fact they do that for Chrome but it does not work properly in openSUSE whereas chromium does.
Hmm, better not tell my browser or it will decide to stop working…
28441 ? S 0:00 /opt/google/chrome/chrome --type=zygote
I think the problem is again the restricted format barrier. Chrome has a video player if I recall correctly.
Absolutely no problems playing YouTube videos and HTML5 videos. It detects the Adobe Flash player plugin and uses that.
It doesn’t seems to be the case to me
Depends: ia32-libs (>= 1.6), lib32gcc1 (>= 1:4.1.1-21+ia32.libs.1.19), lib32stdc++6 (>= 4.1.1-21), libasound2 | libpulse0, libc6 (>= 2.4), libc6-i386 (>= 2.3.4), libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.3.5), libgl1-mesa | libgl1, libgl1-mesa-glx | libgl1, libglew1.5 (>= 1.5.0dfsg1), libglib2.0-0 (>= 2.12.0), libgtk2.0-0 (>= 2.12.0), libpng12-0 (>= 1.2.13-4), libstdc++6 (>= 4.2.1-4), libx11-6, libxt6
Recommends: libnotify-bin
And manually looking at the binaries I didn’t found any reference to it.
Anyway, Packman can’t distribute it… or full copies of Microsoft Office 2010. There is copyright law, you need author’s authorization to do that.
Anyway, isn’t this plugin just another Jingle client? IMHO there are more convenient ways to use Jingle than in a web browser window. And, personally, I prefer the free software ones… specially since I don’t understand why in the hell doesn’t Google gives the source of this one.
You guys are facing this from the wrong perspective in my humble opinion…
Google does provide some software for openSUSE properly packaged in their repositories… this is the case of Chrome for example.
The main point also comes to notoriety… openSUSE needs to increase it’s user base notoriety in order to become a more attractive platform for their releases… and this starts by openSUSE users helping openSUSE to reach that goal… In other words, contribute and enroll in openSUSE Project, because I’m pretty sure openSUSE needs everyone!
Checkout the areas you like, where you would love to learn something and share… for example:
Don’t be shy! Join us and help us reaching higher notoriety by organizing events in your school or community! Promote openSUSE amongst friends and in social networks!
Hi All
OK, here are some rpms for y’all to test…
NOTE: URL’s removed, please see post #20
You need to install libopenssl 0.9.8 and ignore the dependency on it when installing and use zypper (it will then pull in any other dependencies eg;
sudo zypper in google-talkplugin-1.4.1.0-1.i586.rpm
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: nothing provides libcrypto.so.0.9.8(OPENSSL_0.9.8) needed by google-talkplugin-1.4.1.0-1.i586
Solution 1: do not install google-talkplugin-1.4.1.0-1.i586
Solution 2: break google-talkplugin by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c): 2
I tested as far as being recognized in the plug-ins and logging into my google account and it shows me as being able to video chat…
Thanks Malcolm!
I followed your instructions and got it working on the first try. It works great calling a cell phone. I haven’t tried the video chat yet.
Richard
openSUSE 11.3 - KDE
Can I safely use YAST instead of zypper?
I am not finding libopenssl 0.9.8 in the repos I have installed.
Hi
I’ve updated the rpm to pull in libopenssl so there should be no issues using YaST to install, here is the new version;
http://www.muppetwifi.homeunix.net/openSUSE/google-talkplugin-1.4.1.0-2.src.rpm
http://www.muppetwifi.homeunix.net/openSUSE/google-talkplugin-1.4.1.0-2.i586.rpm
http://www.muppetwifi.homeunix.net/openSUSE/google-talkplugin-1.4.1.0-2.x86_64.rpm
If using zypper it should show it pulling it in, just have to ignore the dependency;
sudo zypper in google-talkplugin-1.4.1.0-2.i586.rpm
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: nothing provides libcrypto.so.0.9.8(OPENSSL_0.9.8) needed by google-talkplugin-1.4.1.0-2.i586
Solution 1: do not install google-talkplugin-1.4.1.0-2.i586
Solution 2: break google-talkplugin by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c): 2
Resolving dependencies...
Resolving package dependencies...
The following NEW packages are going to be installed:
google-talkplugin libopenssl0_9_8
2 new packages to install.
Overall download size: 4.8 MiB. After the operation, additional 19.2 MiB will
be used.
Continue? [y/n/?] (y):
@FlameBait it should pull it in now, so just select the option to ignore in YaST and the version will be pulled in, it’s part of the openSUSE OSS standard repository so you shouldn’t have a problem.