Package Details: telegram-desktop-bin-dev 1.5.15-1

Git Clone URL: (read-only)
Package Base: telegram-desktop-bin-dev
Description: Official desktop version of Telegram messaging app - Static binaries, developement version
Upstream URL:
Licenses: GPL3
Conflicts: telegram-desktop, telegram-desktop-bin
Provides: telegram-desktop
Replaces: telegram-bin
Submitter: ItachiSan
Maintainer: ItachiSan
Last Packager: ItachiSan
Votes: 27
Popularity: 0.002016
First Submitted: 2015-07-22 10:53
Last Updated: 2019-02-18 21:04

Dependencies (10)

Required by (0)

Sources (11)

Latest Comments

1 2 Next › Last »

ItachiSan commented on 2018-12-31 12:01

@everyone 1.5.6 is a Mac OSX only release, so I am going to ignore it.

DDoSolitary commented on 2018-08-09 02:14

Hello, the package is broken because the .desktop and .protocol files have wrong SHA hashes.

eaburto commented on 2017-12-30 02:13

Hello, I've created an AUR package that use the GitHub API to install the latest released or prereleased version from the official repo without changing the PKGBUILD. I still think to bump the version in AUR frequently, but you don't need to rely in me to have the latest version. The package is called telegram-desktop-bin-latest if someone is interested! :)

eaburto commented on 2017-12-19 03:39

Hello, new versions of stable and dev versions have been released lately and seems like you could use some help maintaining. Can I help you and comaintain these packages?

realmain commented on 2017-12-13 06:18

New version:

AlexWayfer commented on 2017-12-07 09:27

Why is version 1.1.23 displayed in application?

$ pacman -Qs telegram
local/telegram-desktop-bin-dev 1.1.26-1
    Official desktop version of Telegram messaging app - Static binaries, developement version

UPD: It's updating on the next day, everything is OK.

Faralai commented on 2017-12-07 07:45

New version 64


ItachiSan commented on 2017-05-29 19:55

@lybin I am using them, downloaded from the official website.

lybin commented on 2017-05-27 11:06

May be better use these pre-releases ?

hashworks commented on 2017-01-12 22:01

The sha256sums of the icon[0-9]{2,3}.png files have changed:

sha256sum icon16.png icon32.png icon48.png icon64.png icon128.png icon256.png icon512.png
fc052d1e28b68761bfb6c30ff012e54a4bba0311fc3fc470c728d028c33e9d9f icon16.png
8ae874ada23687c95cbcfe7cfa4cbe1c37f097d9c96e5a836c20109d976a86c7 icon32.png
57d9c71074a619dbe6c361e49f4bee60b1b8c574d8b223d75e61b3744b660ed1 icon48.png
10507a1ddc379b00230c6f6e2bd9f94ea0c7caff9cae05335a66b4d10b7571eb icon64.png
83e3e8eeecadcb3429704626d4ac80ef61ef4e06ba2c6ca2b105a4a436f33032 icon128.png
871f2a6d3bd9d657f8379196e51fd3117c1586e0042e9e993ae138f78b2bcd76 icon256.png
a9eb77ca5a428b32f6e01f62b859cce788c4c9a170dc2cd080800a9de59faa3d icon512.png

PKGBUILD adjustment:

However, do we REALLY need to check the checksum of the icon files?