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: 5
Popularity: 0.95
First Submitted: 2020-11-09 15:48 (UTC)
Last Updated: 2024-07-17 07:59 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

kauron commented on 2021-11-09 15:01 (UTC) (edited on 2021-11-09 15:20 (UTC) by kauron)

Hi there! It seems that python-sqlalchemy >= 1.4 breaks this package, with the following error message (this happened after upgrading from 1.3.23-1 to 1.4.25-1; downgrading fixed it). I don't know what the root cause of this problem is, or if it should be reported upstream.

As always, it is a user error: thanks @noctux.

BrainDamage commented on 2021-09-13 16:23 (UTC) (edited on 2021-09-13 16:23 (UTC) by BrainDamage)

@sdfg: I've used upstream values, the problem is exactly the one in comment of the pkgbuild. The small range makes tracking releases a nightmare, pinning a single version would make the problem worse, not better. In this case by increasing the range to allow version 1.23 of telethon we're going against upstream's values, so if it breaks, it's on our own; for other libraries they don't seem to break the api, but those two in particular they routinely do, so just allowing arbitrary ranges produces all sorts of breakages ...

@nocctux: fixed, thanks.

noctux commented on 2021-09-07 19:33 (UTC)

Thank you for packaging this program (especially the really helpful .install notes!).

However, for me the current version did not build because the folder under srcdir was not called src/mautrix-telegram-0.10.1, but instead src/telegram-0.10.1, so I did require the following patch (in addition to bumping telethon to <1.24 as mentioned by @sdfg):

diff --git a/PKGBUILD b/PKGBUILD
index 902cef7..b01c41a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,5 +1,6 @@
 # Maintainer: BrainDamage
 pkgname=mautrix-telegram
+_pkgname=telegram
 pkgver=0.10.1
 pkgrel=2
 pkgdesc="A Matrix-Telegram hybrid puppeting/relaybot bridge."
@@ -34,7 +35,7 @@ install="${pkgname}.install"


 prepare() {
-       cd "${srcdir}/${pkgname}-${pkgver}"
+       cd "${srcdir}/${_pkgname}-${pkgver}"
        # the author makes liberal usage of max version for requirements without a real need
        # we'll strip them and re-introduce in the deps/optdeps array if truly necessary
        # to prevent a nightmare during updates while tracking stable releases
@@ -48,12 +49,12 @@ prepare() {
 }

 build() {
-       cd "${srcdir}/${pkgname}-${pkgver}"
+       cd "${srcdir}/${_pkgname}-${pkgver}"
        python setup.py build
 }

 package() {
-       cd "${srcdir}/${pkgname}-${pkgver}"
+       cd "${srcdir}/${_pkgname}-${pkgver}"

        _shared_dir="/usr/share/${pkgname}"

It's a bit strange as I seem to be the only one with this problem(?), so sorry to bother you if this was a problem on my end.

sdfg commented on 2021-09-06 09:12 (UTC)

Updates to package versions again

mautrix>=0.10.5,<0.11 telethon>=1.22,<1.24

Might be worth just version restricting them.

julianuu commented on 2021-06-16 13:36 (UTC)

No need to apologize, thanks a lot and for maintaining the package and for the quick fix!

The checksums still need to be updated though ;)

BrainDamage commented on 2021-06-16 12:38 (UTC) (edited on 2021-06-16 12:39 (UTC) by BrainDamage)

@julianuu

that was my mistake, I forgot to set the homedir for the user in the package file, and since I've used my installation which already had homedir set to test it, I've never caught the problem

the command would've been right ... for few versions ago, I forgot to update the installation instructions after upstream changed the method from a wrapper launcher to a pure module, again, I didn't notice because I've used my working installation to test the package and it already had a valid registration file

I apologize for all the issues

istobic commented on 2021-06-16 10:22 (UTC) (edited on 2021-06-16 10:23 (UTC) by istobic)

@julianuu: Same issue I'm facing. I think WorkingDirectory=~ only works, if the home path in mautrix-telegram.sysusers would be pointing there acordingly.

julianuu commented on 2021-06-16 10:22 (UTC) (edited on 2021-06-16 10:26 (UTC) by julianuu)

Also could it be that there is a typo in mautrix-telegram.install? In order to generate the registration I have to run python -m mautrix_telegram -b /usr/share/mautrix-telegram/example-config.yaml -c /etc/mautrix-telegram/config.yaml -r /etc/mautrix-telegram/registration.yaml -g, but in mautrix-telegram.service it says mautrix-telegram for the python module.

Or maybe I am misunderstanding that line in mautrix-telegram.install.

julianuu commented on 2021-06-16 10:19 (UTC)

I have to set WorkingDirectory=/var/lib/mautrix-telegram in the service file, otherwise it complains about permission. I tried deleting /var/lib/mautrix-telegram and the user mautrix-telegram and reinstalling the bridge, but it didn't help.

« First ‹ Previous 1 2 3 4 Next › Last »