Package Details: maubot 0.4.2-1

Git Clone URL: https://aur.archlinux.org/maubot.git (read-only, click to copy)
Package Base: maubot
Description: A plugin-based Matrix bot system
Upstream URL: https://github.com/maubot/maubot
Licenses: AGPL3
Submitter: noobping
Maintainer: jkhsjdhjs (noobping)
Last Packager: jkhsjdhjs
Votes: 1
Popularity: 0.000022
First Submitted: 2022-10-14 20:01 (UTC)
Last Updated: 2024-03-01 02:17 (UTC)

Latest Comments

« First ‹ Previous 1 2

jkhsjdhjs commented on 2022-11-08 18:47 (UTC)

@jahway603 That only shows that you have nodejs-lts-gallium installed, but that doesn't seem to be the nodejs version that is actually used. Can you check again with node -v?

@noobping I don't think adding nodejs as a dependency would change anything, as yarn (which is a make dependency) already depends on nodejs.

noobping commented on 2022-11-08 18:38 (UTC) (edited on 2022-11-09 13:07 (UTC) by noobping)

@jahway603 I see that you have a different nodejs (I have nodejs 19.0.1-1). Does this Dockerfile work for you? Also, please use something like pastebin for your logs.

~I could also add nodejs as a dependency...~

jkhsjdhjs commented on 2022-11-07 15:44 (UTC)

@jahway603 Your version of nodejs is outdated.

jkhsjdhjs commented on 2022-11-03 17:15 (UTC)

@noobping Yeah, line 35 won't make a difference anymore. Thanks for the quick update, works fine now. I also hope they do a new release of python-aiohttp soon.

noobping commented on 2022-11-03 17:04 (UTC)

@jkhsjdhjs Thanks for the explenation. It seems it doesn't matter if I delete or keep line 35. I can't wait for the next release of python-aiohttp.

jkhsjdhjs commented on 2022-11-03 15:26 (UTC) (edited on 2022-11-03 15:29 (UTC) by jkhsjdhjs)

@noobping Ah, it seems there has been a misunderstanding. I wasn't referring to the version pinning of the make dependencies, but the version pinning that is done upstream:
https://github.com/maubot/maubot/blob/master/requirements.txt
https://github.com/maubot/maubot/blob/master/optional-requirements.txt

You can add an sed line to the prepare() function of the PKGBUILD that removes version numbers from the requirements, similar to the one I linked in my comment below. For example:

sed -i -E "s/([0-9a-z_.-]+).=.*/\1/" requirements.txt optional-requirements.txt

Then you also don't need the other sed command on line 35 anymore: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=maubot#n35

noobping commented on 2022-11-03 14:02 (UTC)

Thank you for your comment! I removed the version pinning in de PKGBUILD file.

jkhsjdhjs commented on 2022-11-02 23:10 (UTC) (edited on 2022-11-02 23:16 (UTC) by jkhsjdhjs)

Hey, thanks for creating this package! I'm unable to run the mbc command because of the version pinning done in maubot. Most of the packages in the arch repositories are of a newer version than the one required by maubot, e.g. maubot requires SQLAlchemy<1.4, but the repositories have 1.4.42:

pkg_resources.DistributionNotFound: The 'SQLAlchemy<1.4,>=1' distribution was not found and is required by maubot

$ pacman -Q python-sqlalchemy
python-sqlalchemy 1.4.42-1

Thus I had to remove all the version pinning from /usr/lib/python3.10/site-packages/maubot-0.3.1-py3.10.egg-info/requires.txt. It would be cool if the version pinning could be removed in the PKGBUILD directly. The version pinning isn't useful anyways, because the repositories only contain one version of each package anyways. Thus, the program either works with the available packages or it doesn't. Because the version pinning has also be removed for some other repository packages [1], I think it's fine to do it here as well.

After the version pinning here has been removed there's only one more issue with python-aiohttp, which currently requires charset-normalizer<3.0. This has already been reported [2] and fixed upstream [3], but we'll have to wait for the next release it seems.

[1] https://github.com/archlinux/svntogit-community/blob/9557ae058bb6fc3697c62ddf4da922d1dda8bd69/trunk/PKGBUILD#L62
[2] https://bugs.archlinux.org/task/76326
[3] https://github.com/aio-libs/aiohttp/issues/7050

« First ‹ Previous 1 2