Package Details: mautrix-telegram 0.15.2-3

Git Clone URL: https://aur.archlinux.org/mautrix-telegram.git (read-only, click to copy)
Package Base: mautrix-telegram
Description: Matrix-Telegram hybrid puppeting/relaybot bridge
Upstream URL: https://github.com/tulir/mautrix-telegram
Licenses: AGPLv3
Submitter: BrainDamage
Maintainer: BrainDamage
Last Packager: BrainDamage
Votes: 9
Popularity: 0.174129
First Submitted: 2020-11-09 15:48 (UTC)
Last Updated: 2024-07-17 07:59 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4

kauron commented on 2021-01-29 15:59 (UTC)

I had to manually install python-pip, as it wasn't listed as make dependency. Could you add it to the PKGBUILD?

BrainDamage commented on 2021-01-20 01:21 (UTC)

the error is intentional, the package on the aur won't work with the current release of python-telethon, either build yourself a lower version, wait for a new release, or switch to the -git package

istobic commented on 2021-01-19 19:01 (UTC) (edited on 2021-01-19 19:07 (UTC) by istobic)

Installation fails with:

==> ERROR: Could not resolve all dependencies.
error making: mautrix-telegram

BubuIIC commented on 2020-12-11 17:15 (UTC)

There's now another package called mautrix-telegram, which packages the same thing. I think they should probably be merged?

L0ric0 commented on 2020-11-09 13:09 (UTC) (edited on 2020-11-09 13:10 (UTC) by L0ric0)

It would be nice if you could set a user in the service file, so that the bridge isn't running with root permissions.

If you don't want to add a system user for this you can set DynamicUser=yes.

Here is a write up of the feature: http://0pointer.net/blog/dynamic-users-with-systemd.html

BubuIIC commented on 2020-06-12 09:44 (UTC) (edited on 2020-06-12 09:46 (UTC) by BubuIIC)

I have a few suggestions for improving the package. Some of those might be hard to do as an upgrade path, not sure currently.

Instead of moving the example config to /etc/mautrix-telegram/example-config.yaml I'd link it instead from the package dir. The bridge needs the example config at runtime and it will automatically find it there. (The package currently uses the user generated config also as "example config" in the service file which only works as long as you do manual config migrations on every update.)

I added the alembic upgrade head call to the systemd service file as an ExecStartPre command:

ExecStartPre=/usr/bin/alembic -c /etc/mautrix-telegram/alembic.ini -x config=/etc/mautrix-telegram/config.yaml upgrade head (When the working dir is also changed as below, the alembic.ini needs to be edited to point to the absolute path /etc/mautrix-telegram/alembic/ dir.)

I also enabled systemd's DynamicUser feature with this:

ExecStart=/usr/bin/mautrix-telegram -c /etc/mautrix-telegram/config.yaml -r /etc/mautrix-telegram/registration.yaml
WorkingDirectory=/var/lib/mautrix-telegram/
DynamicUser=true
ConfigurationDirectory=mautrix-telegram
StateDirectory=mautrix-telegram

sakaru commented on 2020-02-05 13:31 (UTC)

I see that you have a post_remove function to rm -rf /etc/mautrix-telegram/. I think it's better to instead declare /etc/mautrix-telegram/config.yaml (and perhaps /etc/mautrix-telegram/registration.yaml) as specify them as backup files (which will rename them with a .pacsave suffix). See how nginx specified backup files as an example.

« First ‹ Previous 1 2 3 4