(Please provide enough information to help the release team
to judge the request efficiently. E.g. by filling in the
sections below.)

[ Reason ]
Telegram migrated from 32-bit user identifiers to 64-bit introducing
backward
incompatible changes in their API. Because of that, a version of the
package
currently in bullseye almost cases to work.
Then I was asked several times to propose an update of the package.

[ Impact ]
Users cannot login. And the package in stable is unusable.

[ Tests ]
This update was already uploaded to backports some time ago. And no
significant
issues have been reported about that version.

[ Risks ]
Many. There is a huge amount of new code. But alternative would be to
delete
the package entirely. Although this is leaf package, any issues do not
affect
other software.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [ ] I reviewed all changes and I approve them
  [x] attach *compressed* debdiffes against the package in stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
New upstream release brings many new features besides support of new API
layer.
In the meanwhile there are no difference between a backported version
and this
proposed version except of d/changelog.

[ Other info ]
This package should be updated along with libtgowt, custom WebRTC fork
built as
static library. Respective debdiff is also attached.

For convince, you can see the changes in Git repositories.

https://salsa.debian.org/debian/libtgowt/-/compare/f11fccc569d0aca79bac3e67a008b8209e624cbd...7b455f6c43394142dd7f49dec662a7733a5a0ea7
https://salsa.debian.org/debian/telegram-desktop/-/compare/cb6c7c5f38d65280fc03cae65b25f5c5b2ca1440...813047b7353acc23408b9230821cc5670afa99d5

Control: tag -1 confirmed
Unfortunate, but I guess we don't have much of a choice, so go ahead.

How often do such incompatible changes happen, historically?

Cheers,
Julien

Hello!

Okay. I've uploaded the telegram-desktop package and its build
dependency, libtgowt, to proposed-updates (bullseye).

This was the first such incompatible change since I've been maintaining
the package for 5 years.

Although, Telegram often implements new features which can't be
displayed in old clients They show "please update" message instead. But
most of the features weren't affecting ability to connect to servers
until 3.1.1 version.

package release.debian.org
tags 1003713 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==============

Package: telegram-desktop
Version: 3.1.1+ds-1~deb11u2

Explanation: new upstream stable release, restoring functionality

package release.debian.org
tags 1003713 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==============

Package: telegram-desktop
Version: 3.1.1+ds-1~deb11u2

Explanation: new upstream stable release, restoring functionality

package release.debian.org
tags 1003713 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==============

Package: libtgowt
Version: 0~git20210627.91d836d+dfsg-3~deb11u1

Explanation: new upstream stable release, to support newer telegram-desktop

package release.debian.org
tags 1003713 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==============

Package: libtgowt
Version: 0~git20210627.91d836d+dfsg-3~deb11u1

Explanation: new upstream stable release, to support newer telegram-desktop

(re-sending with fixed bug numbers)

Hi,

The updates discussed in these bugs were included in today's bullseye
point release.

Regards,

Adam