[solved] google-talkplugin PKGBUILD issues...

xtian · 2014-11-25 18:48:15

Installing the google-talkplugin (for Firefox, and wot wot)
https://aur.archlinux.org/packages/google-talkplugin/

I read Matthew_Moore's 11-22-2014 comment and updated the URL and SHA. The url seemed to work, but the SHA failed verification.
Where in the world do you find the SHA string? It's not in any of the sub-directories of the URL.

[xtian@MasterShake google-talkplugin]$ sudo  makepkg --asroot -s
==> Making package: google-talkplugin 5.38.6.0-1 (Tue Nov 25 14:19:19 EST 2014)
==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for inter-conflicts...

Packages (1): lsb-release-1.4-14

Total Download Size:    0.01 MiB
Total Installed Size:   0.04 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
 lsb-release-1.4-14-any     6.7 KiB  3.27M/s 00:00 [#########################] 100%
(1/1) checking keys in keyring                     [#########################] 100%
(1/1) checking package integrity                   [#########################] 100%
(1/1) loading package files                        [#########################] 100%
(1/1) checking for file conflicts                  [#########################] 100%
(1/1) checking available disk space                [#########################] 100%
(1/1) installing lsb-release                       [#########################] 100%
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading license.html...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 19289    0 19289    0     0   178k      0 --:--:-- --:--:-- --:--:--  179k
  -> Downloading google-talkplugin_current_x86_64.rpm...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 7140k  100 7140k    0     0  2125k      0  0:00:03  0:00:03 --:--:-- 2125k
==> Validating source files with sha1sums...
    license.html ... Skipped
    google-talkplugin_current_x86_64.rpm ... FAILED
==> ERROR: One or more files did not pass the validity check!

Last edited by xtian (2014-11-26 19:26:50)

Scimmia · 2014-11-25 18:50:59

This is why using links to "current" binaries is a bad idea.

Anyway, if upstream doesn't provide checksums, you need to generate them yourself. Simplest way is to just run updpkgsums. Pretty much eliminates any protection the checksum provides, though.

Edit: BTW, running makepkg --asroot is a bad idea as well. It will even be removed as an option soon.

Last edited by Scimmia (2014-11-25 18:56:37)

xtian · 2014-11-25 19:06:27

"Edit: BTW, running makepkg --asroot is a bad idea as well. It will even be removed as an option soon."

Don't I know it. I still can't get root access on my headless CentOS server after a crashed SSH session.

I've generally installed all apps not specifically installed for a single user as root. As the only user, I've been lazy about permissions. I should change the permissions of all my AUR files to a non-root users then?

Scimmia · 2014-11-25 19:10:47

You should be building the packages as a non-root user, but then you install them as root. The non-root user only needs access to the dirs your building in.

xtian · 2014-11-25 19:24:59

Here's the WIKI page for Installing packages. Suppose we could edit it to reflect that informatin?

Installing packages from the AUR is a relatively simple process. Essentially:
Acquire the tarball which contains the PKGBUILD and possibly other required files, like systemd-units and patches (but often not the actual code).
Extract the tarball (preferably in a folder set aside just for builds from the AUR) with tar -xvf foo.tar.gz.
[MAYBE HERE? Build your package as non-root user...]
Run makepkg in the directory where the files are saved (makepkg -s will automatically resolve dependencies with pacman). This will download the code, compile it and pack it. [or MAYBE HERE?]
Look for a README file in src/, as it might contain information needed later on.
Install the resulting package with pacman:
# pacman -U /path/to/pkg.tar.xz
AUR helpers add seamless access to the AUR. They vary in their features but can ease in searching, fetching, building, and installing from PKGBUILDs found in the AUR. All of these scripts can be found in the AUR.
Warning: There is not and will never be an official mechanism for installing build material from the AUR. All AUR users should be familiar with the build process.
[HERE AS ASIDE..FOR YOUR OWN SAKE, DON"T JUST INSTALL --AS-ROOT...

Last edited by xtian (2014-11-25 19:25:51)

Scimmia · 2014-11-25 21:32:39

We could, but since pacman 4.2 will remove the --as-root option anyway, it will soon be a moot point. 4.2 is in a code freeze pending release, so it won't be long.

themax · 2014-11-25 21:33:56

Do you even need google-talkplugin?
Last time I tried, google Hangouts used WebRTC (I think) with html5 video. I don't have the plugin installed.

xtian · 2014-11-26 14:10:42

Scimmia, Why is a moot point? In fact, making these suggested additions would reflect the changes exactly, No?

Scimmia · 2014-11-26 14:58:02

Because there's no reason to tell people to build as a non-root user when that's the only option.

xtian · 2014-11-26 15:15:35

At some point someone will have to explain changing permissions within /var for a non-root user. That's not the default installation.

For example in here...

[xtian@MasterShake google-talkplugin]$ makepkg 
==> ERROR: You do not have write permission to create packages in /var/abs/local/google-talkplugin.
    Aborting...

I suppose the new instructions could be added here, to the makepkg command. But that's outside of my expertise. I'm only talking about the WIKI...

[xtian@MasterShake google-talkplugin]$ sudo makepkg 
==> ERROR: Running makepkg as root is a BAD idea and can cause permanent,
catastrophic damage to your system. If you wish to run as root, please
use the --asroot option.

Scimmia · 2014-11-26 15:22:55

makepkg runs on the current dir, using /var is your choice.

xtian · 2014-11-26 15:29:42

Now I'm curious.
I don't recall actually noticing this, because I'm the only user on my system, but is there any directory outside of /home which installs under any user other than root?
Or are you suggesting its common practice to install apps in /home when you're the only system user?

Scimmia · 2014-11-26 15:33:38

*sigh* Again, we're not talking about installing apps, we're talking about building apps. Where you build them has no bearing at all on how and where they're installed.

xtian · 2014-11-26 15:36:30

So I guess that's a No. I don't want to help you improve the instructions. *sheesh*

clfarron4 · 2014-11-26 15:42:24

OK, so are your PKGBUILD issues sorted with the SHA string?

Trilby · 2014-11-26 15:58:09

xtian you really need to read the forum guidelines carefully. And you need to read all wiki pages more carefully, clarifications on how/where to build packages are already in the right places. I agree with Scimmia, the edits you propose seem very much out of place. At very least they seem out of place for discussion in this thread which was about getting the google-talkplugin PKGBUILD to work.

(closed thread reopened after email exchange with OP)

xtian · 2014-11-26 19:26:34

clfarron4, Scimmia help was instrumental to helping me understand yet another thing I didn't know about building packages and installing them. Learn something new every day, dammit.

themax, "Do you even need google-talkplugin?"
Yes. For Firefox I found it was necessary. After applying the sha script to sort out a an incorrect SHA from a comment sections of the AUR page, the installer makes available in Firefox two plugins: Google Talk Plugin and Google Talk Plugin Video Renderer. The first plugin did provide the talk function and was recognized by the browser. I have another post in Kernel and Hardware sorting out my iSight camera, so I don't know yet about this feature. I noticed there were issues raised here, but I'll get to them in time.

Thanks for all the responses. I will mark this as solved.

Arch Linux

#1 2014-11-25 18:48:15

[solved] google-talkplugin PKGBUILD issues...

#2 2014-11-25 18:50:59

Re: [solved] google-talkplugin PKGBUILD issues...

#3 2014-11-25 19:06:27

Re: [solved] google-talkplugin PKGBUILD issues...

#4 2014-11-25 19:10:47

Re: [solved] google-talkplugin PKGBUILD issues...

#5 2014-11-25 19:24:59

Re: [solved] google-talkplugin PKGBUILD issues...

#6 2014-11-25 21:32:39

Re: [solved] google-talkplugin PKGBUILD issues...

#7 2014-11-25 21:33:56

Re: [solved] google-talkplugin PKGBUILD issues...

#8 2014-11-26 14:10:42

Re: [solved] google-talkplugin PKGBUILD issues...

#9 2014-11-26 14:58:02

Re: [solved] google-talkplugin PKGBUILD issues...

#10 2014-11-26 15:15:35

Re: [solved] google-talkplugin PKGBUILD issues...

#11 2014-11-26 15:22:55

Re: [solved] google-talkplugin PKGBUILD issues...

#12 2014-11-26 15:29:42

Re: [solved] google-talkplugin PKGBUILD issues...

#13 2014-11-26 15:33:38

Re: [solved] google-talkplugin PKGBUILD issues...

#14 2014-11-26 15:36:30

Re: [solved] google-talkplugin PKGBUILD issues...

#15 2014-11-26 15:42:24

Re: [solved] google-talkplugin PKGBUILD issues...

#16 2014-11-26 15:58:09

Re: [solved] google-talkplugin PKGBUILD issues...

#17 2014-11-26 19:26:34

Re: [solved] google-talkplugin PKGBUILD issues...

Board footer