Package Details: mautrix-whatsapp 0.10.9-1

Git Clone URL: https://aur.archlinux.org/mautrix-whatsapp.git (read-only, click to copy)
Package Base: mautrix-whatsapp
Description: A Matrix-WhatsApp puppeting bridge
Upstream URL: https://github.com/tulir/mautrix-whatsapp
Licenses: AGPL
Submitter: L0ric0
Maintainer: sukanka
Last Packager: sukanka
Votes: 10
Popularity: 0.20
First Submitted: 2020-12-31 15:10 (UTC)
Last Updated: 2024-07-16 12:26 (UTC)

Latest Comments

1 2 3 Next › Last »

marcool04 commented on 2024-06-29 09:02 (UTC) (edited on 2024-06-29 09:03 (UTC) by marcool04)

@Sir-Photch your comment is perfectly justified. I maintain the mautrix-whatsapp-bin package, and I have also made the mistake of bumping that to 0.10.8, which is not a good idea as you have said. However, in my and @sukanka's defence, the notification email which github sent our about the new release didn't say anything about it being pre-release, nor was that notice on it:

v0.10.8

Repository: mautrix/whatsapp · Tag: v0.10.8 · Commit: f0b06fa · Released by: tulir

Added proxying options to config.
Updated fallback message for live locations and polls to clarify the user should open the native WhatsApp app.
—
This release has 7 assets:

mautrix-whatsapp-amd64
mautrix-whatsapp-arm
mautrix-whatsapp-arm64
mautrix-whatsapp-darwin-arm64
sha256sums.txt
Source code (zip)
Source code (tar.gz)
Visit the release page to download them.

—
You are receiving this because you are watching this repository.
View it on GitHub or unsubscribe from all notifications for this repository.

I would imagine that what happened is upstream release 0.10.8 as a normal release, and realised after there were problems, so added the notice. However, by then, we had already published these 0.10.8 AUR PKGBUILDs, so we are a bit stuck now.

It's possible to push a "fake" 0.10.8-2 which is in fact 0.10.7 in disguise, that would be fine for anybody still on 0.10.7 or below, or new installations, but as you say that could cause issues for anybody who did install 0.10.8, if the program doesn't support downgrades and the databases get messed up.

Not sure what to do on my end. We'll have 0.10.9 in a couple weeks, I think I might just leave the broken 0.10.8 up in the interim...

Sir-Photch commented on 2024-06-29 08:24 (UTC) (edited on 2024-06-29 08:37 (UTC) by Sir-Photch)

v0.10.8 is marked upstream as a pre-release, with regressions explicitly noted in the release notes. Why did you update the PKGBUILD to that? I am exactly experiencing the issues described in the release notes. Eager people might as well use mautrix-whatsapp-git. This really makes for a bad experience when upstream does not support downgrades...

jkhsjdhjs commented on 2024-02-06 23:28 (UTC)

The PKGBUILD creates /etc/mautrix-whatsapp with mode 755, but tmpfiles define it as 750. This causes warnings on every update:

warning: directory permissions differ on /etc/mautrix-whatsapp/
filesystem: 750  package: 755

Can you make this consistent?

Sir-Photch commented on 2023-09-29 22:05 (UTC) (edited on 2023-09-29 22:05 (UTC) by Sir-Photch)

Also, if you add -n as a runtime argument in the systemd unit, the bot will not try to write the config file, which would take care of misleading warnings in the log. The bot functions fine with only read access to the config.

Sir-Photch commented on 2023-09-27 04:22 (UTC)

the logpath patch needs to change to /var/log/mautrix-whatsapp/mautrix-whatsapp.log, as specified in ReadWritePaths

marcool04 commented on 2023-04-23 14:32 (UTC)

Hi. Just a question: is there any reason you know of not to use the binary files that are on the release pages of mautrix/whatsapp github repo? I made a mautrix-whatsapp-bin PKGBUILD which basically copies yours but just downloads the binaries in stead of doing any building, and it seems to work. Do you know of any limitations? Thanks for your thoughts.

Morta commented on 2023-04-23 09:22 (UTC) (edited on 2023-04-23 09:22 (UTC) by Morta)

Adding this to prepare fix the building issue

go mod tidy -e

go get -t

podiki commented on 2023-04-14 16:22 (UTC) (edited on 2023-04-14 16:23 (UTC) by podiki)

Looks like the hash for log-path.diff is wrong?

==> Validating source files with sha256sums...
    v0.8.3.tar.gz ... Passed
    sysusers-mautrix-whatsapp.conf ... Passed
    mautrix-whatsapp.tmpfiles ... Passed
    mautrix-whatsapp.service ... Passed
    log-path.diff ... FAILED
==> ERROR: One or more files did not pass the validity check!

L0ric0 commented on 2023-04-10 09:49 (UTC)

Well as far as I know the service itself should not write to /etc/mautrix-whatsapp but on creation of the registration file one would have to. Which should be ok as one needs to change the permissions of that file anyway.

I have incorporated the changes please tell me if it is still not working.

TheStochasticMan commented on 2023-03-28 22:49 (UTC) (edited on 2023-03-29 15:39 (UTC) by TheStochasticMan)

I just uninstalled, and got it to work after editing tmpfiles with the /etc/ lines changed as follows:

d /etc/mautrix-whatsapp 0750 root mautrix-whatsapp
z /etc/mautrix-whatsapp/* 0640 mautrix-whatsapp mautrix-whatsapp -

Is it expected that the application writes to /etc/mautix-whatsapp/ aside from possibly the YAML file? If not, this seems like this could be a way to go about it.

1 2 3 Next › Last »