Re: telegram desktop 1.5 on buster warning it will be out of date and stop working soon

[Carsten Schoenert <c.schoenert@t-online.de>]

Hello Jan,

Am 04.12.21 um 16:25 schrieb Jan Groenewald:

> I still see 2.9 in buster-backports-sloppy, is this correct?

yes.

> $ rmadison telegram-desktop
> telegram-desktop | 1.1.23-1~bpo9+1    | stretch-backports                | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> telegram-desktop | 1.1.23-1~bpo9+1    | stretch-backports-debug          | source
> telegram-desktop | 1.5.11-1           | oldstable                        | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> telegram-desktop | 2.2.0+ds-2~bpo10+1 | buster-backports                 | source, armel
> telegram-desktop | 2.2.0+ds-2~bpo10+1 | buster-backports-debug           | source
> telegram-desktop | 2.6.1+ds-1~bpo10+1 | buster-backports                 | source, amd64, arm64, armhf, i386, mips64el, ppc64el
> telegram-desktop | 2.6.1+ds-1~bpo10+1 | buster-backports-debug           | source
> telegram-desktop | 2.6.1+ds-1+deb11u1 | stable                           | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el
> telegram-desktop | 2.6.1+ds-1+deb11u1 | stable-debug                     | source
> telegram-desktop | 2.9.2+ds-1~bpo10+1 | oldstable-backports-sloppy       | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el
> telegram-desktop | 2.9.2+ds-1~bpo10+1 | oldstable-backports-sloppy-debug | source
> telegram-desktop | 2.9.2+ds-1~bpo11+1 | bullseye-backports               | source, mips64el, mipsel
> telegram-desktop | 2.9.2+ds-1~bpo11+1 | bullseye-backports-debug         | source
> telegram-desktop | 3.1.1+ds-1~bpo10+1 | backports-policy                 | source
> telegram-desktop | 3.1.1+ds-1~bpo11+1 | buildd-bullseye-backports        | source, amd64, arm64, armel, armhf, i386, ppc64el
> telegram-desktop | 3.1.1+ds-1~bpo11+1 | bullseye-backports               | source, amd64, arm64, armel, armhf, i386, ppc64el
> telegram-desktop | 3.1.1+ds-1~bpo11+1 | bullseye-backports-debug         | source
> telegram-desktop | 3.1.1+ds-1         | testing                          | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el
> telegram-desktop | 3.1.1+ds-1         | unstable                         | source, mipsel
> telegram-desktop | 3.1.1+ds-1         | unstable-debug                   | source
> telegram-desktop | 3.1.8+ds-1         | unstable                         | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el
> telegram-desktop | 3.1.8+ds-1         | unstable-debug                   | source

You can see the uploaded version 3.1.1+ds-1~bpo10+1 within the 
backports-policy queue.
This means that the admins of the backports infrastructure will need to 
give that package an o.k. for getting in the archive. As long this isn't 
happen you can't install the backported version.

You can see "your" package of interest and other too within the NEW 
queue for backports.

https://ftp-master.debian.org/backports-new.html

--
Regards
Carsten