On 10/22/19 6:51 PM, Charlene Wendling wrote:
> On Tue, 22 Oct 2019 08:54:42 +0200
> Giovanni Bechis wrote:
>
>> On 10/21/19 4:25 PM, Charlene Wendling wrote:
>>> Hi,
>>>
>>> On Sun, 20 Oct 2019 16:02:09 +0200
>>> Giovanni Bechis wrote:
>>>
>>>> Update to latest version, atm it is BROKEN-powerpc, can anybody try
>>>> if it hash been fixed ?
>>>
>>> I did try, and the issue is still here, as seen on sparc64 as well
>>> [0].
>> Do you think we should mark it as BROKEN-spark64 as well then ?
>
> IMHO, we either mark the two archs broken or none at all.
>
> By the way, i've tested it on amd64 with an old telegram account, it
> connects fine. It appears that i've no more contacts on it though, so i
> can't fully test it.
>
after some more tests it seems not much reliable, with 1.4.x it seems that some
messages are lost.
messages from bots do not work any more but I think it is due to some Telegram
changes.
I will retest some future updates and resubmit.
> Port-wise, it looks good to me, even though i guess some of us would
> prefer using GH_* variables instead of MASTER_SITES/{PKG,DIST}NAME.
>
>>> FreeBSD had a *very* interesting patch [1], but it has been
>>> upstreamed in 1.4.2. I don't think i'll be able to fix it as well.
>>>
>>> Charlène.
>>>
>>> [0]
>>> http://build-failures.rhaalovely.net/sparc64/2019-10-11/net/telegram-purple.log
>>> [1]
>>> https://github.com/freebsd/freebsd-ports/blob/master/net-im/telegram-purple/files/patch-tgl_tl-parser_portable__endian.h
>>>
>>
