Arch Linux User Repository

Sorry for the delay, @Mr.Tao I have applied your changes and updated the package. I don't use this anymore so added you as comaintainer and can disown the package if you want to take it over.

Follow-up: duplicate-message fix submitted upstream

The duplicate MESSAGE_POSTED fix is now submitted upstream as purple-googlechat PR #110, and upstream review has started.

I prepared and fully built r592.e6da490-3 containing the complete current PR head (b3f1941), rather than only the initial deduplication commit. It therefore also includes the review follow-ups that:

• validate the nested protobuf message fields, safely handle a missing text body, and limit local-echo suppression to MESSAGE_POSTED so edits are not swallowed;
• close formatting annotations that end exactly at the end of a message.

The immutable combined diff from upstream base e6da490 through PR head b3f1941 is available here. Its SHA-1 is:

da04bb478ea4d6c8c41c1f2d8ae660f64872ff4b

An immediately usable source entry is:

'deduplicate-message-posted-events.patch::https://github.com/Mr-Tao/purple-googlechat/compare/e6da4905b9ac31cbf261ac2f897de012c5b1db6a...b3f194188cf0921e2490e537291c0b99fc9687e6.diff'

Apply it in prepare() with patch -Np1, add the SHA-1 above, and bump pkgrel to 3 after applying the metadata update from my previous comment.

Validation completed:

• makepkg --verifysource --skippgpcheck
• clean makepkg -Csf --noconfirm --skippgpcheck --log
• patched source compared byte-for-byte with PR head for all three changed files
• pacman -Qip and namcap (only the usual implicit glibc notice)

The AUR package is still published as r501.dfdd9c9-1, and I still do not have push access to this packagebase. Please apply the updates above, or add Mr.Tao as a co-maintainer so I can maintain them directly.

Hi, I ran into a Google Chat/Pidgin history issue that is fixed by rebuilding this package from current upstream.

Symptom: after sending the first message in a restored/reopened Google Chat conversation, the message reached the other side and appeared in the official client, but did not appear in Pidgin's local conversation history. I also saw occasional local-only duplicate sent messages in similar flows.

Relevant upstream context:

• https://github.com/EionRobb/purple-googlechat/issues/85 reports the same "first sent message is not shown in pidgin/history" issue.
• https://github.com/EionRobb/purple-googlechat/issues/88 reports sent messages visible on Android but missing in Pidgin.
• Users in #85 reported the missing-first-message case fixed after https://github.com/EionRobb/purple-googlechat/commit/59b6466d6cbbfefbb3f6779c84273c6b7cba8298.
• https://github.com/EionRobb/purple-googlechat/issues/12 is the older duplicate-sent-message issue; that one may not be fully fixed upstream.

I built current upstream master (r592.e6da490) and installed it locally with pidgin 2.14.14-5 / libpurple 2.14.14-5. Initial testing indicates that the missing sent-message-in-history issue is fixed.

I prepared the following git am patch. It bumps the VCS package metadata to the current upstream revision, switches the license to SPDX syntax, and adds explicit zlib because namcap detects libz.so.1.

Validation:

• makepkg --verifysource --skippgpcheck
• makepkg -Csf --noconfirm --skippgpcheck --log
• makepkg -Rf --noconfirm --log
• pacman -Qip
• git diff --check
• namcap (only the usual implicit glibc warning remains)

I do not have push access to this packagebase, but I can help co-maintain it if that would be useful.

From 303542d04fbf9fd1775a39b0c2bd435274d4aa2d Mon Sep 17 00:00:00 2001
From: "Mr. Tao" <tao@post.cz>
Date: Sun, 23 Aug 2026 15:22:43 +0200
Subject: [PATCH] Update to latest upstream snapshot

---
 .SRCINFO | 5 +++--
 PKGBUILD | 6 +++---
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/.SRCINFO b/.SRCINFO
index 87dee55..6392ea1 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,18 +1,19 @@
 pkgbase = purple-googlechat
    pkgdesc = A Pidgin plugin to support the proprietary protocol used by Google for the Google Chat service
-   pkgver = r501.dfdd9c9
+   pkgver = r592.e6da490
    pkgrel = 1
    url = https://github.com/EionRobb/purple-googlechat
    arch = i686
    arch = x86_64
    arch = armv6h
    arch = aarch64
-   license = GPLv3+
+   license = GPL-3.0-or-later
    makedepends = git
    depends = libpurple
    depends = glib2
    depends = json-glib
    depends = protobuf-c
+   depends = zlib
    provides = purple-googlechat
    conflicts = purple-googlechat-git
    source = purple-googlechat::git+https://github.com/EionRobb/purple-googlechat.git
diff --git a/PKGBUILD b/PKGBUILD
index 3b392c4..49bad28 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -5,12 +5,12 @@ pkgname=purple-googlechat
 pkgdesc="A Pidgin plugin to support the proprietary protocol used by Google for the Google Chat service"
 url='https://github.com/EionRobb/purple-googlechat'
 arch=('i686' 'x86_64' 'armv6h' 'aarch64') 
-pkgver=r501.dfdd9c9
+pkgver=r592.e6da490
 pkgrel=1
-license=('GPLv3+')
+license=('GPL-3.0-or-later')
 provides=($pkgname)
 conflicts=($pkgname-git)
-depends=('libpurple' 'glib2' 'json-glib' 'protobuf-c')
+depends=('libpurple' 'glib2' 'json-glib' 'protobuf-c' 'zlib')
 makedepends=('git')
 source=('purple-googlechat::git+https://github.com/EionRobb/purple-googlechat.git')
 sha1sums=('SKIP')
-- 
2.55.0

This package downloads the latest state from a git repository.

So you must rename it to purple-googlechat-git (with the -git suffix), and change the purple-googlechat-git conflicts entry to purple-googlechat.

Regards and thanks for the package!

After installing the package, pidgin (2.14) picks up the library (/usr/lib/purple-2/libgooglechat.so) and adds account type "Google chat". No other configuration needed. pidgin-hg not tested. After last changes in package, it might be necessary to remove purple-googlechat-git and install purple-googlechat.

Are there further steps after building, to get Pidgin to pick up the plugin?

It seems to build to /usr/lib/purple-2/libgooglechat.so - Ive tried copying to ~/.purple/plugins but still Pidgin isn't showing it in the Plugin list

No reason at all. Just helper variable, didn't realize it is reserved. Corrected.

Any reason for modifying the pkgbase ? Quoting from the wiki : "When building regular packages, this variable should not be explicitly declared in the PKGBUILD: its value defaults to that of #pkgname. "

(This apparently does not work too well with aurutils :/)