| Summary: | Our telegram-cli is not working anymore; it needs updating to a newer upstream (forked) version | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jybz <j.biernacki+mga> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | andrewsfarm, davidwhodgins, geiger.david68210, lewyssmith, ouaurelien, sysadmin-bugs |
| Version: | 7 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7-64-OK | ||
| Source RPM: | telegram-cli-1.0.2-0.20140908git8c2069.10.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Jybz
2020-08-13 20:42:28 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 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*
package updated on Cauldron with telegram-cli-20200106-1.mga8. CC:
(none) =>
geiger.david68210 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 And now updated for mga7 with telegram-cli-20200106-1.mga7 in Core/Updates_testing repo! Please test it. 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.) 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
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 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 Confirming OK with a clean install. Validating. Advisory in Comment 9. Keywords:
(none) =>
validated_update
Aurelien Oudelet
2020-08-21 11:44:55 CEST
CC:
(none) =>
ouaurelien An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2020-0190.html Resolution:
(none) =>
FIXED |