Bug 29992

Summary: Policy question package/download: telegram-desktop
Product: Mageia Reporter: Nikolay Sabelnikov <79625490833>
Component: New RPM package requestAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: davidwhodgins, fri, lewyssmith, mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://github.com/telegramdesktop/tdesktop
Whiteboard:
Source RPM: telegram-desktop CVE:
Status comment:

Description Nikolay Sabelnikov 2022-02-04 07:19:06 CET
Why don't you build from source?
Comment 1 sturmvogel 2022-02-04 08:19:52 CET
We have already have a get-telegram package which downloads and install the actual telegram version from the github site. And it updates itself.

https://madb.mageia.org/package/show/name/get-telegram/arch/x86_64
Comment 2 Lewis Smith 2022-02-04 09:36:18 CET
(In reply to Nikolay Sabelnikov from comment #0)
> new pkg building: telegram-desktop
> Why don't you build from source?
Not sure what you mean by this. Presumably (since you classed the bug as "New RPM package request") that you want us to offer it.
Thank you yet again sturmvogel for your explanation: we do in effect offer it.

If you, Nikolay, had searched Add/Install Software for 'telegram', you would have found it:
"Name       : get-telegram
Summary     : Download and Install Telegram Desktop
Description : This is a downloader script for Telegram Desktop.
This package does not contain any program files. By installing this
package you'll get the option to download and install Telegram from
desktop.telegram.org.
Removing this package won't uninstall Telegram from your system. You
can do this manually by removing "~/.TelegramDesktop/application"
directory."

Resolution: (none) => INVALID
Status: NEW => RESOLVED
CC: (none) => lewyssmith

Comment 3 Morgan Leijström 2022-02-04 11:00:12 CET
The question is _why_ we chose this approach in this case - and answer not given.

For the sake of understanding our policies this is an important question.

The general approach in Mageia is to package compiled software.

Voices against external download, Appimage, Flatpak, external repos etc are that integration, reliability, security etc may suffer.

Some applications that are much wanted by users but we we are not allowed to ship due to licenses, we sometimes instead make an rpm that downloads it when used on users system.  We used to do this with skype, and also other packages i now have forgot.

For telegram client i found no licensing obstacle, it is GNU GPLv2 or GPLv3 

Just guessing, is this choice maybe because it can update itself?

Resolution: INVALID => (none)
CC: (none) => fri
Status: RESOLVED => REOPENED

Morgan Leijström 2022-02-04 11:01:23 CET

Summary: new pkg building: telegram-desktop => Policy question package/download: telegram-desktop

Comment 4 Morgan Leijström 2022-02-04 12:59:31 CET
CC packager

Hi Sander

This is not critisism, just curiosity :)

Why user side downloading instead of normal package?

PS  Nikolay is new and may be interested in packaging  DS

CC: (none) => mageia

Comment 5 Nikolay Sabelnikov 2022-02-04 13:21:19 CET
Sorry for asking a lot of questions.
Comment 6 Morgan Leijström 2022-02-04 13:46:30 CET
Please do ask so you know :)
And other learn something too.

Later you can guide other people :)
Comment 7 Nikolay Sabelnikov 2022-02-04 13:48:58 CET
(In reply to Morgan Leijström from comment #6)
> Please do ask so you know :)
> And other learn something too.
> 
> Later you can guide other people :)

It can be safely sealed, especially since in this way you can control the quality of versions.
Comment 8 Morgan Leijström 2022-02-04 13:53:10 CET
Absolutely, packaged is usually the best.

- Just we have enough manpower to keep up when security updates and the likes are needed.

I can compare to syncthing which we packaged before, but had to drop because of some problem with some dependency, and lack of manpower.

I now run a manually downloaded syncthing, that updates itself.
Comment 9 Nikolay Sabelnikov 2022-02-04 14:08:01 CET
Next week I will register in your system as a builder packages, and then, maybe I will work more closely with you as a Russian-speaking builder. I like your attitude towards others and the system itself.
Comment 10 Morgan Leijström 2022-02-04 14:36:00 CET
You are much welcome :)

I suggest to register for dev mailing list https://ml.mageia.org/l/info/dev
Present yourself and that you are looking for a packaging mentor.
There are procedures to follow, to ensure quality.
With your energy i think you will advance quickly :)


There are also other Russian speaking people here.
Example recently Alex Kotov working on android-tools in Bug 28860.
Try entering .ru in the "Add" field in this bug form for a long listing.
Note that many are not active, people join and leave.



All lists https://wiki.mageia.org/en/Mailing_lists
IRC https://wiki.mageia.org/en/Mageia_IRC_Channels_Liberachat

https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
https://wiki.mageia.org/en/Packagers_Mentoring_Howto
Comment 11 Dave Hodgins 2022-02-04 16:39:41 CET
On 2015-04-11, Sander posted in the dev mailing list ...

"Telegram is developing their protocol pretty fast and Cutegram is unable to keep up with
that pace + I can't update/upgrade that application so often. So, to provide the latest
features to our users I've created a downloader script for the official client."

So it was packager's choice to create the get-telegram script instead of adding
the package.

Any packager that is willing to maintain the package can add the actual
telegram package.

CC: (none) => davidwhodgins

Comment 12 Dave Hodgins 2022-02-04 16:43:47 CET
Closing the bug as invalid since it isn't a problem with Mageia packages or
infrastructure, etc. Discussions such as this are best handled on the dev
mailing list. where more people will see it.

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

Comment 13 Morgan Leijström 2022-02-04 16:52:52 CET
Thanks Dave for that find
I thought it was something like that  :)