Commit Graph

65 Commits

Author SHA1 Message Date
Michael Reilly
84cf00f980
treewide: Per RFC45, remove all unquoted URLs 2020-04-10 17:54:53 +01:00
Maximilian Bosch
1c54edcf8d
mautrix-telegram: 0.7.1 -> 0.7.2
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.2
2020-04-04 22:35:42 +02:00
Maximilian Bosch
89d13541e5
mautrix-telegram: 0.7.0 -> 0.7.1
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.1
2020-02-04 22:28:15 +01:00
Maximilian Bosch
975a6b7b1d mautrix-telegram: mark as broken on darwin
Tests currently fail like this:

```
/nix/store/yslk7x7iw3hka6d33kmnba9sxaia4492-python3.7-mautrix-0.4.0/lib/python3.7/site-packages/mautrix/util/manhole.py:9: in <module>
    from socket import SOL_SOCKET, SO_PEERCRED
E   ImportError: cannot import name 'SO_PEERCRED' from 'socket' (/nix/store/81qani7sdir46gjwf3a3jr2cv1aggkz1-python3-3.7.5/lib/python3.7/socket.py)
!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!
=============================== 1 error in 1.73s ===============================
```

Those values don't seem to be available on the MacOS-version of that
module. As there's no workaround implemented in the source, I assume
that upstream doesn't intend to support darwin-alike platforms atm.
2019-12-29 19:56:05 -08:00
Maximilian Bosch
95ee079ae6 mautrix-telegram: 0.6.1 -> 0.7.0
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.0
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.0-rc4
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.0-rc3
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.0-rc2
https://github.com/tulir/mautrix-telegram/releases/tag/v0.7.0-rc1
2019-12-29 19:56:05 -08:00
Jonathan Ringer
051c67dc4c mautrix-telegram: fix build 2019-12-24 11:30:01 -08:00
Maximilian Bosch
22470fff35
mautrix-telegram: fix build
With updating `pluggy` to `0.13.0`[1] the way how python modules are
imported during pytest changed which broke all modules that had a
`coding: future_fstrings` annotation at the top which used to be needed
for python <=3.5. This only affected the tests, deploying a
`mautrix-telegram` from master with `doCheck = false;` works fine.

I applied a patch for `mautrix-telegram` which drops python 3.5 compat
(this package is intended to be used as application with python 3.7, so this
should be fine on master/unstable) and modified `mautrix-appservice`
accordingly as a lot of things on master changed since their last
release, so applying a patch didn't work there.

Resolves #71996

[1] faf8cfba4e
2019-10-26 10:58:56 +02:00
Maximilian Bosch
ae293ad45e
mautrix-telegram: 0.6.0 -> 0.6.1
https://github.com/tulir/mautrix-telegram/releases/tag/v0.6.1
2019-09-20 23:35:14 +02:00
Maximilian Bosch
54752cd3c4
mautrix-telegram: fix startup
`setuptools` isn't propagated automatically anymore, see also #68314.
2019-09-12 11:22:17 +02:00
nyanloutre
baddb2ac89
mautrix-telegram: 0.5.2 -> 0.6.0 2019-07-09 18:55:37 +02:00
nyanloutre
024c1c3d2a
mautrix-telegram: 0.5.1 -> 0.5.2 2019-06-01 17:37:32 +02:00
Maximilian Bosch
0a94f89fca
mautrix-telegram: patch away alembic dependency
`alembic`[1] is a database migration tool which is invoked from the CLI
when installing the telegram bridge, but never needed during the
runtime.

The reason why `alembic` is required here is to ensure that it
exists in the Python environment when deploying the bridge. However
`alembic` requires `mautrix-telegram` in its environment to create a
database schema from the Python models.

Such a dependency relation may be possible with tools like virtualenv,
however it'll result in an infinite recursion at evaluation time in Nix.

With this patch, `mautrix-telegram` doesn't depend on `alembic` anymore
and provides a patched alembic (`pkgs.mautrix-telegram.alembic`) which
has `mautrix-telegram` in its path.

[1] https://alembic.sqlalchemy.org/en/latest/
2019-05-24 09:35:39 +02:00
nyanloutre
2f69e363a5 mautrix-telegram: 0.5.0 -> 0.5.1 2019-03-21 14:57:26 +01:00
nyanloutre
3fa5e2bab6 mautrix-telegram: 0.4.0.post1 -> 0.5.0 2019-03-20 11:42:27 +01:00
nyanloutre
53fddad692 mautrix-telegram: init at 0.4.0.post1 2019-01-31 09:55:55 +01:00