Bug 27106 - Our telegram-cli is not working anymore; it needs updating to a newer upstream (forked) version
Summary: Our telegram-cli is not working anymore; it needs updating to a newer upstrea...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2020-08-13 20:42 CEST by Jybz
Modified: 2020-08-22 21:28 CEST (History)
6 users (show)

See Also:
Source RPM: telegram-cli-1.0.2-0.20140908git8c2069.10.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Jybz 2020-08-13 20:42:28 CEST
Hello,

the upstream of telegram-cli ( https://github.com/vysheng/tg ) has no update since 2016. There is a fork more actively maintained https://github.com/kenorb-contrib/tg 

The problem is, the current upstream is not working anymore, failing to connect to the telegram server.

Changes I do on mageia's SPEC :

> %global	checkout	3da0e4a54c3a63cee11aae3c23f2077adfc4949d
> %global librarycheckout 57f1bc41ae13297e6c3e23ac465fd45ec6659f50
> %global	date		20140908
> %global gitowner    kenorb-contrib
> %define	_version	%{date}git%(echo %{checkout} | cut -c-6)
> 
> Name:		telegram-cli
> Version:	20200106
> Release:	%mkrel -c %{_version} 12
> Summary:	Linux Command-line interface for Telegram
> Group:		Networking/Instant messaging
> License:	GPLv2+ and LGPLv2+
> URL:		https://github.com/%{gitowner}/tg
> Source0:	https://github.com/%{gitowner}/tg/archive/%{checkout}.tar.gz#/tg-%{checkout}.tar.gz
> Source1:    https://github.com/kenorb-contrib/tgl/archive/%{librarycheckout}.tar.gz#/tgl.tar.gz
...
> %prep
> %setup -q -n tg-%{checkout}
> %setup -n tg-%{checkout} -a 1
> rm -r tgl
> ln -s ./tgl-%{librarycheckout} ./tgl
Comment 1 Lewis Smith 2020-08-13 21:12:58 CEST
Thank you for the report.
The bug is for M7; can you confirm that it applies equally to M8/Cauldron? I think it does, there is no sign of any significant Cauldron change since M7. If so, please change Version to Cauldron, and my MGA8TOO Whiteboard to MGA7TOO.
Also, please confirm that the newer forked version *does* work.

Supported software not working matters; and if it is cured by a more recent - albeit slightly different - upstream source, then I think this can be classed as an update to the existing SRPM rather than a new package request or enhancement.

This bug is raised for Mageia 7; I have put the Mageia 8 SRPM ID since it is what I am seeing, and I do not think anything has evolved since M7.

This package has no particular maintainer, so assignçng this globally.

CC: (none) => lewyssmith
Whiteboard: (none) => MGA8TOO
Summary: telegram-cli is upstream is not working anymore, suggestion : a fork => Our telegram-cli is not working anymore; it needs updating to a newer upstream (forked) version
Assignee: bugsquad => pkg-bugs
Source RPM: telegram-cli => telegram-cli-1.0.2-0.20140908git8c2069.12.mga8.src.rpm

Comment 2 Jybz 2020-08-13 22:51:15 CEST
I don't have Mga8 currently.

I build the newer version and currently using it, I confirm, it works.

I also add the the spec :
add in the %install section:
install -p telegram.1 %{buildroot}%{_mandir}/man1/
add in the %file section:
%{_mandir}/man1/telegram.1*
Comment 3 David GEIGER 2020-08-14 07:24:11 CEST
package updated on Cauldron with telegram-cli-20200106-1.mga8.

CC: (none) => geiger.david68210

Comment 4 Lewis Smith 2020-08-15 21:43:13 CEST
Thank you for doing this, David. Is it possible for Mageia 7, which still has some time to run ? Then we could ask Jybz to test the 'new' Mageia package.

Source RPM: telegram-cli-1.0.2-0.20140908git8c2069.12.mga8.src.rpm => telegram-cli-1.0.2-0.20140908git8c2069.10.mga7.src.rpm
Whiteboard: MGA8TOO => MGA7TOO
Version: 7 => Cauldron

Comment 5 David GEIGER 2020-08-17 15:46:30 CEST
And now updated for mga7 with telegram-cli-20200106-1.mga7 in Core/Updates_testing repo!

Please test it.
Comment 6 Jybz 2020-08-17 16:17:37 CEST
I confirm on Mga7 :
> [root@localhost build (master)]# urpme telegram-cli  
> désinstallation de telegram-cli-20200106-0.20140908git3da0e4.12.mga7.x86_64
> désinstallation du paquetage telegram-cli-20200106-0.20140908git3da0e4.12.mga7.x86_64
>       1/1: désinstallation de telegram-cli-20200106-0.20140908git3da0e4.12.mga7.x86_64
>                                  #####################################################################################################################################
> 
> [root@localhost build (master)]# urpmi --media Core\ Updates\ Testing telegram-cli 
> Pas de paquetage nommé telegram-cli
> 
> [root@localhost build (master)]# urpmi.update --media "Core Updates Testing"
> Unknown option: media
>     http://mirrors.mageia.org/api/mageia.7.x86_64.list: media/core/updates_testing/media_info/20200817-025521-synthesis.hdlist.cz
> média « Core Updates Testing » mis à jour
> 
> [root@localhost build (master)]# urpmi --media "Core Updates Testing" telegram-cli 
>     http://mirrors.mageia.org/api/mageia.7.x86_64.list: media/core/updates_testing/telegram-cli-20200106-1.mga7.x86_64.rpm
> installation de telegram-cli-20200106-1.mga7.x86_64.rpm depuis /var/cache/urpmi/rpms                                                                                   
> Préparation...                   #####################################################################################################################################
>       1/1: telegram-cli          #####################################################################################################################################

> [jybz@localhost rpmbuild]$ telegram-cli
> Telegram-cli version 1.4.1, Copyright (C) 2013-2015 Vitaly Valtman
> Telegram-cli comes with ABSOLUTELY NO WARRANTY; for details type `show_license'.
> This is free software, and you are welcome to redistribute it
> under certain conditions; type `show_license' for details.
> Telegram-cli uses libtgl version 2.1.0
> Telegram-cli includes software developed by the OpenSSL Project
> for use in the OpenSSL Toolkit. (http://www.openssl.org/)
> I: config dir=[/home/jybz/.telegram-cli]
> > version
> Telegram-cli version 1.4.1 (uses tgl version 2.1.0)
> uses libopenssl for encryption

it works !

Thank you David !

(I think it works also on Mga8, no reason not to.)
Comment 7 Jybz 2020-08-17 16:18:11 CEST
fixed

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 8 Dave Hodgins 2020-08-17 16:38:07 CEST
Reopening until an advisory for the Mageia 7 update has been added to svn
and the update pushed from updates testing to updates.

Adding the ok tag based on comment 6.

Status: RESOLVED => REOPENED
CC: (none) => davidwhodgins
Whiteboard: MGA7TOO => MGA7TOO MGA7-64-OK
Resolution: FIXED => (none)

Dave Hodgins 2020-08-17 16:39:12 CEST

Assignee: pkg-bugs => qa-bugs

David Walser 2020-08-18 04:37:26 CEST

Version: Cauldron => 7
Whiteboard: MGA7TOO MGA7-64-OK => MGA7-64-OK

Comment 9 David GEIGER 2020-08-18 17:32:24 CEST
Assigning to QA now,


Advisory:
========================

Our current telegram-cli package is a quite old now (released 2014-09-08) and is not working anymore, failing to connect to the telegram server.
So this updates telegram-cli to a more recent and maintained upstream release.

========================

Packages in 7/core/updates_testing:
========================
telegram-cli-20200106-1.mga7.i586.rpm
telegram-cli-20200106-1.mga7.x86_64.rpm

Source RPM: 
========================
telegram-cli-20200106-1.mga7.src.rpm
Comment 10 Thomas Andrews 2020-08-21 02:56:06 CEST
Confirming OK with a clean install. Validating. Advisory in Comment 9.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

Aurelien Oudelet 2020-08-21 11:44:55 CEST

CC: (none) => ouaurelien
Keywords: (none) => advisory

Comment 11 Mageia Robot 2020-08-22 21:28:15 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0190.html

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.