Package Details: mautrix-whatsapp 0.10.7-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: 8
Popularity: 0.000029
First Submitted: 2020-12-31 15:10 (UTC)
Last Updated: 2024-04-16 14:13 (UTC)

Latest Comments

1 2 3 Next › Last »

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.

TheStochasticMan commented on 2023-03-28 22:30 (UTC) (edited on 2023-03-28 22:58 (UTC) by TheStochasticMan)

The mx-puppet-discord-git package does something similar yet doesn't seem to have an issue, so I checked what that package does. It looks like that one has a slightly different permissions for /etc/... in tmpfiles

L0ric0 commented on 2023-03-25 19:34 (UTC)

The problem is that at the first install of the package the user mautrix-whatsapp is not known to the system and is only created when the sysusers file is parsed. That means that the uid of the user is not know and can not be set in the PKGBUILD. I could set the uid of the mautrix-whatsapp user to a hard value but that has the posibility to not only show an error but also to break systems when a user with the uid already exists.

1 2 3 Next › Last »