Package Details: telegram-purple 1.4.7-1

Git Clone URL: https://aur.archlinux.org/telegram-purple.git (read-only, click to copy)
Package Base: telegram-purple
Description: Adds support for Telegram to Pidgin, Adium, Finch and other Libpurple based messengers.
Upstream URL: https://github.com/majn/telegram-purple
Licenses: GPL
Conflicts: telegram-purple-git
Submitter: wzyboy
Maintainer: wzyboy
Last Packager: wzyboy
Votes: 133
Popularity: 1.00
First Submitted: 2015-03-21 13:17 (UTC)
Last Updated: 2021-05-15 20:16 (UTC)

Latest Comments

gpc commented on 2020-01-22 14:33 (UTC) (edited on 2020-04-18 11:12 (UTC) by gpc)

[Below problems are fixed in version 1.4.3. Images sent via "gallery" don't load, but don't interrupt further messages.]

Anyone else had sent images not display in pidgin, and result in further messages in that conversation not display? They were sent by send media option, but sending them via send file option works. (I can see everything display correctly in Android client.)

Also, since my friend sent a location to me, both pidgin and finch segfault on startup unless I disable telegram plugin. A workaround for me is to delete the location message in the Android client, then telegram-purple works again.

pidgin/libpurple 2.13.0-9, telegram-purple 1.4.2-1

Above problems appear to be reported upstream: https://github.com/majn/telegram-purple/issues/517 https://github.com/majn/telegram-purple/issues/522

SanskritFritz commented on 2019-11-24 21:15 (UTC)

This now crashes pidgin 2.13.0-9 here. No indication is given about the problem, pidgin dumps a core and exits. Pidgin works without the telegram plugin.

Strykar commented on 2019-11-11 07:26 (UTC) (edited on 2019-11-11 18:07 (UTC) by Strykar)

Currently, this crashes Bitlbee, I've raised an issue upstream but telegram-libpurple is stripping symbols.

Upstream suggests you should not be stripping symbols - https://github.com/majn/telegram-purple/issues/525#issuecomment-552521563 However, this will increase size by approximately 3.24 MB.

Recommend adding options=(!strip) to PKGBUILD.

wzyboy commented on 2019-10-25 07:45 (UTC) (edited on 2019-10-25 07:45 (UTC) by wzyboy)

@Grandma I see that the author has already corrected the link to 1.4.2. The PKGBUILD is now working without issues :-)

Grandma commented on 2019-10-25 07:06 (UTC) (edited on 2019-10-25 07:08 (UTC) by Grandma)

Hi, @wzboy!

Can you please check this issue out? I think it's better to rollback PKGBUILD for now before the "real" release happen.

vasya commented on 2019-10-24 08:23 (UTC)

Interesting. Apparently there's quite a number of typos (version mismatches) in the last entry of the releases page: https://github.com/majn/telegram-purple/releases/

Main title says "1.4.2", but the tag is "1.4.1".. This package needs a version downgrade apparently.

P.S. On the other hand, I personally stopped using telegram from pidgin, so I'll unsubscribe.

Fraterius commented on 2019-10-24 08:17 (UTC)

I'm getting:

ERROR: Failure while downloading https://github.com/majn/telegram-purple/releases/download/v1.4.2/telegram-purple_1.4.2.orig.tar.gz

and as I can see it's not there:

https://github.com/majn/telegram-purple/releases

wzyboy commented on 2019-09-01 14:01 (UTC)

@vasya Thanks. I have fixed that error.

vasya commented on 2019-09-01 11:46 (UTC) (edited on 2019-09-01 11:49 (UTC) by vasya)

Hi wzyboy. Can you please fix the PKGBUILD typo: the bash array for conflicts should be conflicts, not conflict.

Shameless plug: I've found this error via RUA (that I develop), specifically the shellcheck option of it.

You can confirm the variable name in man PKGBUILD.

wzyboy commented on 2018-08-27 07:14 (UTC)

I have updated the PKGBUILD to include the -w CLFAGS as @itoffshore suggested.

itoffshore commented on 2018-08-26 19:57 (UTC)

The correct way to set CFLAGS in configure is:

./configure --prefix=/usr CFLAGS="$CFLAGS -w"

which on 64bit gives CFLAGS of:

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -w"

stefnix commented on 2018-07-23 18:28 (UTC)

This package will not build without changing the following line ./configure --prefix=/usr

to

./configure --prefix=/usr CFLAGS="-w"

alien2003 commented on 2018-07-12 07:56 (UTC)

cc1: all warnings being treated as errors make[1]: [Makefile:60: objs/queries.o] Error 1 make[1]: Waiting for unfinished jobs.... make[1]: Leaving directory '/tmp/makepkg/telegram-purple/src/telegram-purple/tgl' make: *** [Makefile:87: tgl/libs/libtgl.a] Error 2

to7m commented on 2018-06-10 22:35 (UTC)

As best I can tell, something in the build process is using -Werror, which is bad. Sticking -Wno-error in the pkgbuild isn't enough to override this, but -w is. So I replace

./configure --prefix=/usr

with

./configure --prefix=/usr CFLAGS="-w"

. No idea if that's dangerous, but it works!

to7m commented on 2018-06-07 22:26 (UTC)

When running makepkg, is anyone else getting an error starting with the following?:

queries.c: In function ‘_tgl_do_send_photo’: queries.c:2132:10: error: cast between incompatible function types from ‘void ()(struct tgl_state , void , int, struct tgl_message )’ to ‘void ()(struct tgl_state , void , int)’ [-Werror=cast-function-type] ((void ()(struct tgl_state , void , int))callback) (TLS, callback_extra, 0);

wzyboy commented on 2017-05-03 05:27 (UTC)

@jevv Thanks. I've bumped pkgrel.

je-vv commented on 2017-05-03 02:09 (UTC)

There's no need to move to development version, neither git version. Just re-building works fine. Perhaps the upgrade of libwebp (0.5.2-1 -> 0.6.0-1) affected telegram-purple: % ldd /usr/lib/purple-2/telegram-purple.so | grep libwebp libwebp.so.7 => /usr/lib/libwebp.so.7 (0x00007fc2fc991000) Perhaps a new AUR release (*-2) might automate a rebuild for those unaware... BTW, if using the other versions, the same should have happened, :-)

Ghul commented on 2017-05-02 09:58 (UTC)

@vasya I switched to dev package, it builds 1.4.0 and protocol works fine now thnx

vasya commented on 2017-05-02 08:34 (UTC)

@Ghul, I had this problem, too. Re-compiling the latest development version helped though. (The non-development version might work as well, I'm just saying how it was for me.)

Ghul commented on 2017-05-02 08:28 (UTC)

telegram protocol isn't detected now be libpurple, it's reported as unknown both by pidgin and bitlbee

chinz commented on 2017-03-19 19:13 (UTC)

There is a missing depenency this will not build unless you also install 'pkg-config'.

fincan commented on 2016-08-27 20:34 (UTC)

Finally I ve just found the problem with LC_ALL=en_US makepkg -si there is no problem!

fincan commented on 2016-08-16 10:18 (UTC)

In file included from mtproto-common.h:39:0, from mtproto-common.c:45: auto/constants.h:205:29: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_update_message_��_d 0x4e90bfd6 ^ auto/constants.h:228:34: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_update_read_history_��nbox 0x9961fd5c ^ auto/constants.h:236:34: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_update_read_channel_��nbox 0x4214f37f ^ auto/constants.h:245:25: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_update_bot_��nline_query 0xc01eea08 ^ auto/constants.h:326:33: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_document_attribute_��mage_size 0x6c37c15c ^ auto/constants.h:351:31: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_account_password_��nput_settings 0xbcfc532c ^ auto/constants.h:354:19: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_chat_��nvite_empty 0x69df3769 ^ auto/constants.h:355:19: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_chat_��nvite_exported 0xfc2e05bc ^ auto/constants.h:355:0: hata: "CODE_chat_" yeniden tanımlanmış [-Werror] #define CODE_chat_ınvite_exported 0xfc2e05bc auto/constants.h:354:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_chat_ınvite_empty 0x69df3769 auto/constants.h:356:19: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_chat_��nvite_already 0x5a686d7c ^ auto/constants.h:356:0: hata: "CODE_chat_" yeniden tanımlanmış [-Werror] #define CODE_chat_ınvite_already 0x5a686d7c auto/constants.h:355:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_chat_ınvite_exported 0xfc2e05bc auto/constants.h:357:19: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_chat_��nvite 0x93e99b60 ^ auto/constants.h:357:0: hata: "CODE_chat_" yeniden tanımlanmış [-Werror] #define CODE_chat_ınvite 0x93e99b60 auto/constants.h:356:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_chat_ınvite_already 0x5a686d7c auto/constants.h:359:32: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_input_sticker_set_��_d 0x9de7a269 ^ auto/constants.h:364:18: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_bot_��nfo_empty 0xbb2e37ce ^ auto/constants.h:365:18: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_bot_��nfo 0x09cf585d ^ auto/constants.h:365:0: hata: "CODE_bot_" yeniden tanımlanmış [-Werror] #define CODE_bot_ınfo 0x09cf585d auto/constants.h:364:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_bot_ınfo_empty 0xbb2e37ce auto/constants.h:380:29: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_message_entity_��talic 0x826f8b60 ^ auto/constants.h:416:24: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_input_bot_��nline_message_media_auto 0x2e43e587 ^ auto/constants.h:417:24: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_input_bot_��nline_message_text 0xadf0df71 ^ auto/constants.h:417:0: hata: "CODE_input_bot_" yeniden tanımlanmış [-Werror] #define CODE_input_bot_ınline_message_text 0xadf0df71 auto/constants.h:416:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_input_bot_ınline_message_media_auto 0x2e43e587 auto/constants.h:418:24: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_input_bot_��nline_result 0x2cbbe15a ^ auto/constants.h:418:0: hata: "CODE_input_bot_" yeniden tanımlanmış [-Werror] #define CODE_input_bot_ınline_result 0x2cbbe15a auto/constants.h:417:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_input_bot_ınline_message_text 0xadf0df71 auto/constants.h:419:18: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_bot_��nline_message_media_auto 0xfc56e87d ^ auto/constants.h:419:0: hata: "CODE_bot_" yeniden tanımlanmış [-Werror] #define CODE_bot_ınline_message_media_auto 0xfc56e87d auto/constants.h:365:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_bot_ınfo 0x09cf585d auto/constants.h:420:18: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_bot_��nline_message_text 0xa56197a9 ^ auto/constants.h:420:0: hata: "CODE_bot_" yeniden tanımlanmış [-Werror] #define CODE_bot_ınline_message_text 0xa56197a9 auto/constants.h:419:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_bot_ınline_message_media_auto 0xfc56e87d auto/constants.h:421:18: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_bot_��nline_media_result_document 0xf897d33e ^ auto/constants.h:421:0: hata: "CODE_bot_" yeniden tanımlanmış [-Werror] #define CODE_bot_ınline_media_result_document 0xf897d33e auto/constants.h:420:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_bot_ınline_message_text 0xa56197a9 auto/constants.h:422:18: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_bot_��nline_media_result_photo 0xc5528587 ^ auto/constants.h:422:0: hata: "CODE_bot_" yeniden tanımlanmış [-Werror] #define CODE_bot_ınline_media_result_photo 0xc5528587 auto/constants.h:421:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_bot_ınline_media_result_document 0xf897d33e auto/constants.h:423:18: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_bot_��nline_result 0x9bebaeb9 ^ auto/constants.h:423:0: hata: "CODE_bot_" yeniden tanımlanmış [-Werror] #define CODE_bot_ınline_result 0x9bebaeb9 auto/constants.h:422:0: bilgi: burası evvelki tanımın yapıldığı yer #define CODE_bot_ınline_media_result_photo 0xc5528587 auto/constants.h:434:24: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_auth_sign_��n 0xbcd51581 ^ auto/constants.h:437:24: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_auth_send_��nvites 0x771c1d97 ^ auto/constants.h:521:35: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_messages_export_chat_��nvite 0x7d885289 ^ auto/constants.h:522:34: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_messages_check_chat_��nvite 0x3eadb1bb ^ auto/constants.h:523:35: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_messages_import_chat_��nvite 0x6c50051c ^ auto/constants.h:538:27: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_messages_get_��nline_bot_results 0x9324600d ^ auto/constants.h:539:27: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_messages_set_��nline_bot_results 0x3f23ec12 ^ auto/constants.h:540:28: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_messages_send_��nline_bot_result 0xb16e06fe ^ auto/constants.h:555:23: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_help_get_��nvite_text 0xa4a95186 ^ auto/constants.h:560:27: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_channels_get_��mportant_history 0xddb929cb ^ auto/constants.h:582:30: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_channels_export_��nvite 0xc7560885 ^ auto/constants.h:618:25: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_binlog_our_��d 0x68a870e8 ^ auto/constants.h:632:29: hata: ISO C99 makro isminden sonra boşluk gerektirir [-Werror] #define CODE_binlog_set_msg_��d 0x3c873416 ^ cc1: all warnings being treated as errors make[1]: *** [Makefile:54: objs/mtproto-common.o] Error 1 make[1]: Leaving directory '/home/cihat/Aur/telegram-purple/src/telegram-purple/tgl' make: *** [Makefile:82: submade] Error 2 ==> HATA: build() içinde bir hata oluştu. Çıkılıyor...

Blake commented on 2016-04-21 11:12 (UTC)

It's possible do add supergroups support (Telegram)?

Stunts commented on 2016-03-22 23:16 (UTC)

Unfortunately I'm still getting the same error... Could this be some package update that broke build()?

Shirx commented on 2016-03-22 18:39 (UTC)

@wzyboy I'm confused now... Giving your new PKGBUILD a try worked perfectly and there was no compilation error. Now I do have a working installation, so thanks so far =): aur/telegram-purple 1.2.6-3 (65, 11.82) [installed] But now (few minutes later after rebooting and maybe doing things I'm not aware of), running your PKGBUILD again (actually for no reason) gives the same compilation errors as reported by Stunts.

wzyboy commented on 2016-03-22 14:45 (UTC)

@Shirx @Stunts The package builds on my laptop well, I cannot re-produce your issues. However, as I find the upstream author now provides tarballs optimized for packagers, I use the tarball as source instead of git clone + submodule. Could you check the new PKGBUILD now solves your issues? Thanks.

Stunts commented on 2016-03-22 14:18 (UTC)

Build is also failing for me with the following error: queries.c: In function ‘tgl_do_send_document’: queries.c:2014:13: error: ‘x.peer_type’ may be used uninitialized in this function [-Werror=maybe-uninitialized] f->avatar = avatar; ^ queries.c:2082:17: note: ‘x.peer_type’ was declared here tgl_peer_id_t x; ^ queries.c:2014:13: error: ‘x.access_hash’ may be used uninitialized in this function [-Werror=maybe-uninitialized] f->avatar = avatar; ^ queries.c:2082:17: note: ‘x.access_hash’ was declared here tgl_peer_id_t x; ^ cc1: all warnings being treated as errors Makefile:54: recipe for target 'objs/queries.o' failed make[1]: *** [objs/queries.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory '/tmp/yaourt-tmp-francisco/aur-telegram-purple-git/src/telegram-purple/tgl' Makefile:83: recipe for target 'tgl/libs/libtgl.a' failed make: *** [tgl/libs/libtgl.a] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Maybe there is a missing dependency somewhere? Thanks for looking into it.

Shirx commented on 2016-03-18 11:47 (UTC)

build() fails for me with some compile errors: tg-mime-types.c:13:25: error: ‘mime_types’ undeclared (first use in this function) tg-mime-types.c:14:23: error: ‘mime_types_len’ undeclared (first use in this function) ==> ERROR: A failure occurred in build(). However, manually compiling git version works with: git submodule update --init --recursive ./configure make Thanks, and sorry if this is not because of your PKBUILD.

droserasprout commented on 2016-01-31 14:27 (UTC)

Please add to PKBUILD conflict with git version of this package.

wzyboy commented on 2016-01-15 00:38 (UTC)

@majn89 Dependencies in parenthesises are shown there because they declare that they "provide" corresponding packages. They are not listed nor controlled by me. I will make changes that declare this package explicitly requires libgcrypt>=1.6.0 in PKGBUILD anyway. Then libgcrypt15-git shall not be shown. Thank you.

majn89 commented on 2016-01-14 15:49 (UTC)

One last tiny issue: telegram-purple needs libgcrypt >= v1.60, therefore libgcrypt15-git wouldn't work (1.5.4) as a an optional (?) dependency. Since we *really* use some of the functions that changed with 1.60 it would probably be better to remove that entry altogether ;)

wzyboy commented on 2016-01-14 03:00 (UTC)

@majn89 Thanks for reminding. I have checked, and am happy to see that telegram-purple already links against libgcrypt. So I made changes to the PKGBUILD file to declare that this package now depends on libgcrypt instead of openssl.

majn89 commented on 2016-01-13 22:59 (UTC)

I just noticed that you are still listing openssl as dependency, but the default crypto library is libgcrypt >= 1.60 since version 1.2.1. Please double-check if it actually links against libgcrypt, Do not use --disable-gcrypt, distributing binaries with openssl is a GPL violation since Pidgin doesn't have the openssl exception. Its why we had to switch to libgcrypt.

wzyboy commented on 2016-01-05 02:39 (UTC)

@majn89 Thanks, original author :-)

majn89 commented on 2016-01-05 00:34 (UTC)

This needs to include version 1.2.4, which is a hotfix for some crashes: 1.2.4 ----- - Fix crash on unknown media type - Fix crash on logout after cancelling a file transfer

wzyboy commented on 2015-05-18 13:38 (UTC)

@pl_m Thanks! I've swapped the order in PKGBUILD. The change will be reflected in the next build.

pl_m commented on 2015-05-18 13:34 (UTC)

> are you suggestting swapping the order of "git checkout" and "git submodule"? What does this achieve please? it is only for theoretical situation, when in code branches (and it tags, of course) using different submodules (differently from the master submodules). today -- this is not a problem :-) . fix -- for theoretical situations only

wzyboy commented on 2015-04-30 13:46 (UTC)

@pl_m Hi, are you suggestting swapping the order of "git checkout" and "git submodule"? What does this achieve please?

pl_m commented on 2015-04-30 13:41 (UTC)

today, in PKGBUILD there is fragment: prepare() { cd "${srcdir}/${pkgname}" git submodule update --init --recursive git checkout $_pkgver } may be need change it to: prepare() { cd "${srcdir}/${pkgname}" git checkout $_pkgver git submodule update --init --recursive } ? thanks!

wzyboy commented on 2015-03-21 13:20 (UTC)

I don't like the uncertainty brought by VCS packages, so this is a release version of telegram-purple. Though the source is cloned from Git, the PKGBUILD will checkout a specific tag before building. PKGBUILD is maintained here: https://github.com/wzyboy/PKGBUILDs/blob/master/telegram-purple/PKGBUILD . Pull requests are welcome.