Package Details: purple-gowhatsapp-git 1.21.0_396_20260216124546-1

Git Clone URL: https://aur.archlinux.org/purple-gowhatsapp-git.git (read-only, click to copy)
Package Base: purple-gowhatsapp-git
Description: A libpurple/Pidgin plugin for WhatsApp, powered by whatsmeow
Upstream URL: https://github.com/hoehermann/purple-gowhatsapp
Keywords: chat libpurple library pidgin plugin purple whatsapp
Licenses: GPLv3
Conflicts: purple-gowhatsapp
Provides: purple-gowhatsapp
Submitter: Network_Jack
Maintainer: hoehermann
Last Packager: hoehermann
Votes: 11
Popularity: 0.071672
First Submitted: 2019-11-03 21:33 (UTC)
Last Updated: 2026-02-16 23:03 (UTC)

Dependencies (9)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

Mr.Tao commented on 2026-02-27 15:59 (UTC)

I think the package should conflict with ${_pkgnam}-debug as well. I have just switched from purple-gowhatsapp to this package. At the end of the process, it correctly asked to remove purple-gowhatsapp, but the installation process failed because the file /usr/lib/debug/usr/lib/purple-2/libwhatsmeow.so.debug already existed in the file system.

hoehermann commented on 2026-02-16 23:16 (UTC)

Dear dreieck, thank you for letting me know. I did not check the vercmp documentation diligently and thought all non-numeric characters would be regarded as separators, but it is all non-alphanumeric. I removed the "r". I want to keep using underscores do separate the semantic version from the revision number and the library date, though. I put the full version string into the metadata. I hope this makes updating less cumbersome. 🙂

dreieck commented on 2026-01-03 11:13 (UTC)

Ahoj,

please fix $pkgver:

  • Add a . before the .r. Currently, $pkgver is 1.21.0r373_20251217143725. It should be 1.21.0.r373_20251217143725. (Also, considering changing _ to ..)
  • The package version in the AUR metadata is just 1.21.0. The update logic of yay does consider this to be higher than 1.21.0r373_20251217143725, always trying to update. Please make the package version in the AUR metadata to be actual one package version generated by pkgver() at some point with the same versioning scheme that the package currently uses.

Regards and thanks for the package!

hoehermann commented on 2026-01-02 22:07 (UTC)

Dear sotitrox, pidgin-hg is Pidgin 3. It is not supported by this plug-in. In case I ever start supporting it, I would create a new package called purple3-whatsmeow. Check https://github.com/hoehermann/purple-gowhatsapp/issues/54 for details.

Dear astehlik, thank you for your comment. I updated the PKGBUILD accordingly.

sotitrox commented on 2026-01-02 14:08 (UTC) (edited on 2026-01-02 14:08 (UTC) by sotitrox)

This work with pidgin-hg??

Get this error on build when pidgin-hg is present:

==> Iniciando build()...
[  5%] Generating libwhatsmeow.a, libwhatsmeow.h
[ 10%] Built target libwhatsmeow
[ 15%] Building C object glue/CMakeFiles/whatsmeow.dir/__/bridge.c.o
En el fichero incluido desde /home/user/.cache/aurutils/sync/purple-gowhatsapp-git/src/purple-gowhatsapp/bridge.c:1:
/home/user/.cache/aurutils/sync/purple-gowhatsapp-git/src/purple-gowhatsapp/bridge.h:3:10: error fatal: purple.h: No existe el fichero o el directorio
    3 | #include <purple.h> // for PurpleAccount, PurpleXfer
      |          ^~~~~~~~~~
compilación terminada.
make[2]: *** [glue/CMakeFiles/whatsmeow.dir/build.make:135: glue/CMakeFiles/whatsmeow.dir/__/bridge.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:205: glue/CMakeFiles/whatsmeow.dir/all] Error 2
make: *** [Makefile:156: all] Error 2
==> ERROR: Se produjo un fallo en build().
    Cancelando...

astehlik commented on 2025-09-18 16:32 (UTC) (edited on 2025-09-18 16:34 (UTC) by astehlik)

Go seems to install its module files by default with non writable permissions 0444.

This causes issues with the cache cleanup of AUR Helpers like yay - for example yay tries to remove ~/.cache/yay/purple-gowhatsapp-git/src/purple-gowhatsapp/build/_go/pkg/mod/google.golang.org/protobuf@v1.36.9/runtime/protolazy/protolazy.go - which fails.

I looked around a bit and other packages solve this problem by adding the modcacherw flag (see https://go.dev/ref/mod#build-commands) to the download commands (for example yay itsself: https://github.com/Jguer/yay/blob/next/Makefile#L27)

I was able to solve this in the purple-gowhatsapp-git by setting an env variable in line 31 of the PKGBUILD file:

GOFLAGS=-modcacherw cmake --build build --target download-modules

I'm not sure if this is the best solution or if this is something that should be integrated in the cmake config.

PS, thank you for your lightspeed merge of my PR and maintaining this package :)

hoehermann commented on 2022-07-13 20:25 (UTC)

Thank you for the report, sotitrox. The issue has been fixed upstream.

sotitrox commented on 2022-07-13 17:15 (UTC)

I got this in the build process

...

    go: downloading github.com/google/go-cmp v0.5.5
    go: downloading golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543
    go: downloading github.com/mdp/qrterminal v1.0.1
    [ 23%] Generating purple-go-whatsapp.a, purple-go-whatsapp.h
    # command-line-arguments
    ./send_message.go:53:107: cannot use ts (variable of type whatsmeow.SendResponse) as type time.Time in argument to purple_display_text_message
    make[2]: *** [src/go/CMakeFiles/purple-go-whatsapp.dir/build.make:87: src/go/purple-go-whatsapp.a] Error 2
    make[1]: *** [CMakeFiles/Makefile2:143: src/go/CMakeFiles/purple-go-whatsapp.dir/all] Error 2
    make: *** [Makefile:136: all] Error 2
    ==> ERROR: Se produjo un fallo en build().
        Cancelando...

gpc commented on 2022-03-01 14:20 (UTC)

The whatsmeow branch is now the main branch, with this PKGBUILD provided:

https://github.com/hoehermann/purple-gowhatsapp/blob/whatsmeow/PKGBUILD

1 2 3 Next › Last »