Package Details: purple-matrix-git r207.1d23385-2

Git Clone URL: (read-only, click to copy)
Package Base: purple-matrix-git
Description: Libpurple protocol plugin for matrix.
Upstream URL:
Licenses: GPL2
Conflicts: purple-matrix
Provides: purple-matrix
Submitter: go2sh
Maintainer: livvy
Last Packager: livvy
Votes: 15
Popularity: 0.002471
First Submitted: 2015-12-21 14:39 (UTC)
Last Updated: 2021-01-15 00:36 (UTC)

Dependencies (7)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

livvy commented on 2021-01-15 00:37 (UTC)

@Atomisirsi: done

Atomisirsi commented on 2021-01-10 20:42 (UTC)

Please replace libolm-git by libolm from community. libolm-git points to same release and is orphaned.

livvy commented on 2020-06-06 20:45 (UTC) (edited on 2020-06-06 20:46 (UTC) by livvy)

Going to adopt this for what it's worth as I might try and hack on upstream.

@EndlessEden: Will add optional E2E support with libolm-git but the flag has already been added to the makefile:

EndlessEden commented on 2020-06-01 08:13 (UTC)

please add libolm-git, for e2e support.

i also recommend, @aashiks recommendation of removing deprecation warning "-DGLIB_DISABLE_DEPRECATION_WARNINGS" from the makefile

aashiks commented on 2019-11-29 06:25 (UTC)

I modified the PKGBUILD's "build" section to look like this

build() { cd "$srcdir/${pkgname%-git}" sed -i '7iCFLAGS += -DGLIB_DISABLE_DEPRECATION_WARNINGS' Makefile make MATRIX_NO_E2E=1 }

Thanks @jjbeard

brycec commented on 2019-11-13 02:24 (UTC)

"until libpurple can bump the API"

Or until the workaround is merged into purple-matrix (

jjbeard commented on 2019-11-13 00:41 (UTC)

The deprecation errors of GParameter can be suppressed by adding the following in the src Makefile (doesn't really matter where, I put after line 7):


Apparently1 this is in the libpurple headers, so it has to be worked around like this until libpurple can bump the API.

brycec commented on 2018-08-06 03:29 (UTC)

Note: The bump to r182.5a7166a-0 has no E2E (libolm) support, at least for now.

brycec commented on 2017-05-23 13:46 (UTC)

Yes the original author made a mistake. Yes I didn't catch it. And yes I could just remove it ( @GI_Jack You don't have to be rude about it.