UPDATE: net/telegram-purple

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

UPDATE: net/telegram-purple

Giovanni Bechis-7
Update to latest version, atm it is BROKEN-powerpc, can anybody try if it hash been fixed ?

 Giovanni

telegram-purple-1.4.2.diff (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: UPDATE: net/telegram-purple

Charlene Wendling
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].
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

Reply | Threaded
Open this post in threaded view
|

Re: UPDATE: net/telegram-purple

Giovanni Bechis-7
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 ?

> 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
>

Reply | Threaded
Open this post in threaded view
|

Re: UPDATE: net/telegram-purple

Charlene Wendling
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.

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
> >
>

Reply | Threaded
Open this post in threaded view
|

Re: UPDATE: net/telegram-purple

Giovanni Bechis-7
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
>>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: UPDATE: net/telegram-purple

chohag
Giovanni Bechis writes:

> 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 message
> s 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.

There has been some discussion on the telegram-purple group regarding
a bug that has been recently introduced which likely affects all
architectures. In summary, after receiving a certain type of message,
reportedly an image or video, subsequent incoming messages are not
delivered.

https://github.com/majn/telegram-purple/issues/517

Matthew

Reply | Threaded
Open this post in threaded view
|

Re: UPDATE: net/telegram-purple

Stuart Henderson
In reply to this post by Charlene Wendling
On 2019/10/22 18:51, Charlene Wendling wrote:
> 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.

GH_* variables are for auto generated tarballs (/archive/ URLs) not for
things with a proper release.

As Makefile.template says:

# github:
# /releases/ -> preferred. ignore GH_*, just use MASTER_SITES and DISTNAME.
# /archive/ ->  GH_ACCOUNT and GH_PROJECT, plus either GH_TAGNAME or GH_COMMIT.

Reply | Threaded
Open this post in threaded view
|

Re: UPDATE: net/telegram-purple

Stuart Henderson
In reply to this post by Giovanni Bechis-7
On 2019/10/20 16:02, Giovanni Bechis wrote:
> @@ -34,6 +28,4 @@ share/pixmaps/pidgin/protocols/22/
>  share/pixmaps/pidgin/protocols/22/telegram.png
>  share/pixmaps/pidgin/protocols/48/
>  share/pixmaps/pidgin/protocols/48/telegram.png
> -share/purple/server.tglpub
>  @sample ${SYSCONFDIR}/telegram-purple/
> -@sample ${SYSCONFDIR}/telegram-purple/server.tglpub

Is there any need for ${SYSCONFDIR}/telegram-purple/ if server.tglpub
has been removed?