Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

[Felix R.]

Package: telegram-desktop
Followup-For: Bug #1001016

Hi,

+1 to not shipping a incompatible version by default.

This also applies to ubuntu-lts and probably other downstream distros.

Any idea why the version got that outdated in the firstplace?

cheers
Felix

Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

[Paul Gevers]

Hi Mattia,

On 19-12-2021 10:15, Mattia Rizzolo wrote:
While thinking this, please also consider that this is the first time 
ever that telegram broke its API in such strong backward incompatible way.


In the past it only added features that, at most, prevented old clients 
to display the newest type of messages, hardly something RC.


Please don't be too quick in judging telegram not stable-worthy just for 
one breaking APi change.


I said: "if I read you correctly". Apparently I didn't do that. So lets 
not remove the package from testing for this reason.


That said, if the package in stable and oldstable is non-functional and 
can't be updated without jumping to a much never version, it's probably 
best to request its removal from stable and oldstable.


On Sat, 18 Dec 2021, 10:33 pm Paul Gevers, > wrote:

Also, if I read you correctly I think we should stop shipping
telegram-desktop in testing as it seems you can't support it for
long in
any Debian stable release. Maybe you should look for supporting the
users via https://fasttrack.debian.net/ 

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

[Mattia Rizzolo]

While thinking this, please also consider that this is the first time ever
that telegram broke its API in such strong backward incompatible way.

In the past it only added features that, at most, prevented old clients to
display the newest type of messages, hardly something RC.

Please don't be too quick in judging telegram not stable-worthy just for
one breaking APi change.

On Sat, 18 Dec 2021, 10:33 pm Paul Gevers,  wrote:

> Dear Nicholas,
>
> On Fri, 03 Dec 2021 20:11:10 +0300 Nicholas Guriev 
> wrote:
> > Release managers do not happy with huge updates after Debian freeze.
>
> And for good reasons (also remember that upgrades only come every two
> months or so, even longer for oldstable).
>
> If telegram-desktop is useless in stable and isn't supportable in
> stable, you should request it's removal from stable ($(reportbug
> release.debian.org)).
>
> Also, if I read you correctly I think we should stop shipping
> telegram-desktop in testing as it seems you can't support it for long in
> any Debian stable release. Maybe you should look for supporting the
> users via https://fasttrack.debian.net/
>
> Paul
>
> PS: the argument about firefox-esr is valid, but we consider that an
> unavoidable exception (not shipping a web-browser sounds like a bad idea).
>

Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

[Paul Gevers]

Dear Nicholas,

On Fri, 03 Dec 2021 20:11:10 +0300 Nicholas Guriev  
wrote:

Release managers do not happy with huge updates after Debian freeze.


And for good reasons (also remember that upgrades only come every two 
months or so, even longer for oldstable).


If telegram-desktop is useless in stable and isn't supportable in 
stable, you should request it's removal from stable ($(reportbug 
release.debian.org)).


Also, if I read you correctly I think we should stop shipping 
telegram-desktop in testing as it seems you can't support it for long in 
any Debian stable release. Maybe you should look for supporting the 
users via https://fasttrack.debian.net/


Paul

PS: the argument about firefox-esr is valid, but we consider that an 
unavoidable exception (not shipping a web-browser sounds like a bad idea).


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

[Ralf Neubauer]

Hi,

ok, your mail arrived while I wrote my last one and I only saw it after
sending.

I am upgrading to 2.9.2+ds-1~bpo11+1 now -- one machine is done, the
others will follow (the messages in the 'Telegram' channel confusingly
also appear in the up-to-date iOS app so I will have to update all
clients). I think I will see tomorrow or in the next couple of days if I
still get these messages. Or faster -- the message box appeared again,
maybe it is set every couple of minutes?

Wasn't there a similar problem with firefox where a solution was worked
out to follow upstream more closely?

Thank you so far!

Ralf

On Fri, Dec 03, 2021 at 08:11:10PM +0300, Nicholas Guriev wrote:
> Hello!
> 
> Could you test version 2.9.2 from backports? Does the message appear
> there?
> For a backports guide see: https://backports.debian.org/Instructions/
> 
> If even this version is considered ancient, I could backport 3.1.1 from
> testing. I am sure it still is working.
> 
> From what I know, versions older that 3.1.1 are unable to operate for
> newly registered users whose UIDs do not fit signed 32bit. However, the
> older versions continue to work for already existing users.
> 
> As a maintainer I can only offer you to switch to backports repository.
> Release managers do not happy with huge updates after Debian freeze.
> Telegram team in their turn is primarily focused on implementing new
> features. The goals seem contradictory, and users stuck between a rock
> and a hard place.
> 



-- 
  72 61 6c 66 40 73 74 72 : 63 6d 70 2e 64 65 0a r...@strcmp.de. 

Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

[Nicholas Guriev]

Hello!

Could you test version 2.9.2 from backports? Does the message appear
there?
For a backports guide see: https://backports.debian.org/Instructions/

If even this version is considered ancient, I could backport 3.1.1 from
testing. I am sure it still is working.

From what I know, versions older that 3.1.1 are unable to operate for
newly registered users whose UIDs do not fit signed 32bit. However, the
older versions continue to work for already existing users.

As a maintainer I can only offer you to switch to backports repository.
Release managers do not happy with huge updates after Debian freeze.
Telegram team in their turn is primarily focused on implementing new
features. The goals seem contradictory, and users stuck between a rock
and a hard place.



signature.asc
Description: This is a digitally signed message part

Bug#1001016: telegram-desktop: Version in stable (2.6.1) becoming unusable

[Ralf Neubauer]

Package: telegram-desktop
Version: 2.6.1+ds-1+deb11u1
Severity: grave
Justification: renders package unusable

Hi,

I got a message in the 'Telegram' channel on telegram: "Please update your app 
to the latest version. The version you are using is out of date and will stop 
working soon."

There is a 3.1.1 in testing but I won't upgrade the whole system from
stable to testing for that. How can I upgrade to a version that won't
stop working soon?

Shouldn't there be a policy in the telegram team to support old clients
as long as they are in current stable versions of distributions? Is the
version of telegram-desktop in debian stable supported at all, does it
get security updates and backported security fixes?

Ralf


-- Package-specific info:

-- System Information:
Debian Release: 11.1
  APT prefers proposed-updates
  APT policy: (800, 'proposed-updates'), (800, 'stable'), (799, 'oldstable'), 
(750, 'testing-proposed-updates'), (750, 'testing'), (300, 'unstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telegram-desktop depends on:
ii  libavcodec58  7:4.3.3-0+deb11u1
ii  libavformat58 7:4.3.3-0+deb11u1
ii  libavutil56   7:4.3.3-0+deb11u1
ii  libc6 2.31-13+deb11u2
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1
ii  libgcc-s1 10.2.1-6
ii  libgdk-pixbuf-2.0-0   2.42.2+dfsg-1
ii  libglib2.0-0  2.66.8-1
ii  libgtk-3-03.24.24-4
ii  libhunspell-1.7-0 1.7.0-3
ii  libjpeg62-turbo   1:2.0.6-4
ii  libkf5waylandclient5  4:5.78.0-2
ii  liblz4-1  1.9.3-2
ii  liblzma5  5.2.5-2
ii  libminizip1   1.1-8+b1
ii  libopenal11:1.19.1-2
ii  libopus0  1.3.1-0.1
ii  libqrcodegencpp1  1.6.0-1
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-9
ii  libqt5dbus5   5.15.2+dfsg-9
ii  libqt5gui55.15.2+dfsg-9
ii  libqt5network55.15.2+dfsg-9
ii  libqt5waylandclient5 [qtwayland-client-abi-5-15-  5.15.2-3
ii  libqt5widgets55.15.2+dfsg-9
ii  librlottie0-1 0.1+dfsg-2
ii  libssl1.1 1.1.1k-1+deb11u1
ii  libstdc++610.2.1-6
ii  libswresample37:4.3.3-0+deb11u1
ii  libswscale5   7:4.3.3-0+deb11u1
ii  libx11-6  2:1.7.2-1
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-record01.14-3
ii  libxcb-screensaver0   1.14-3
ii  libxcb1   1.14-3
ii  libxxhash00.8.0-2
ii  qt5-image-formats-plugins 5.15.2-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans  1.11-1.1

telegram-desktop suggests no packages.

-- no debconf information

-- debsums errors found:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 144653 
package 'musepack-decoder':
 'Version' field value 'sv7.15+1.95z67-1': version number does not start with 
digit
dpkg-divert: warning: parsing file '/var/lib/dpkg/status' near line 144653 
package 'musepack-decoder':
 'Version' field value 'sv7.15+1.95z67-1': version number does not start with 
digit
[2021.12.02 15:38:37] Launched version: 2006001, install beta: [FALSE], alpha: 
0, debug mode: [FALSE]
[2021.12.02 15:38:37] Executable dir: /usr/bin/, name: telegram-desktop
[2021.12.02 15:38:37] Initial working dir: /home/wu/
[2021.12.02 15:38:37] Working dir: /home/wu/.local/share/TelegramDesktop/
[2021.12.02 15:38:37] Command line: telegram-desktop
[2021.12.02 15:38:37] Executable path before check: /usr/bin/telegram-desktop
[2021.12.02 15:38:37] Logs started
[2021.12.02 15:38:37] Launcher filename: telegramdesktop.desktop
[2021.12.02 15:38:37] Getting DE, XDG_CURRENT_DESKTOP: ''
[2021.12.02 15:38:37] Getting DE, DESKTOP_SESSION: ''
[2021.12.02 15:38:37] Getting DE,