The package was flagged as out-of-date due to 2.1.16 (now .17); that is however a beta release, thus the '-dev' packages will be updated but not this one.
Search Criteria
Package Details: telegram-desktop-dev 5.7.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/telegram-desktop-dev.git (read-only, click to copy) |
---|---|
Package Base: | telegram-desktop-dev |
Description: | Official Telegram Desktop client - development release |
Upstream URL: | https://desktop.telegram.org/ |
Licenses: | GPL3 |
Conflicts: | telegram-desktop |
Provides: | telegram-desktop |
Submitter: | hexchain |
Maintainer: | ItachiSan |
Last Packager: | ItachiSan |
Votes: | 8 |
Popularity: | 0.000029 |
First Submitted: | 2015-10-29 04:14 (UTC) |
Last Updated: | 2024-11-10 12:18 (UTC) |
Dependencies (46)
- abseil-cpp (abseil-cpp-gitAUR)
- ada
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-ffplayoutAUR, ffmpeg-amd-full-gitAUR, ffmpeg-cudaAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR, ffmpeg-libfdk_aacAUR, ffmpeg-fullAUR, ffmpeg-decklinkAUR, ffmpeg-headlessAUR, ffmpeg-obsAUR, ffmpeg-amd-fullAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- hunspell (hunspell-gitAUR)
- kcoreaddons (kcoreaddons-gitAUR)
- libdispatch (libdispatch-gitAUR)
- libsigc++-3.0
- libxcomposite
- libxdamage
- libxrandr (libxrandr-gitAUR)
- libxtst
- lz4 (lz4-gitAUR)
- minizip (minizip-gitAUR)
- openal (openal-gitAUR)
- openh264 (openh264-gitAUR)
- openssl (openssl-gitAUR, openssl-staticAUR)
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR)
- protobuf (protobuf-gitAUR)
- Show 26 more dependencies...
Required by (2)
- purpose-git (requires telegram-desktop) (optional)
- tmulti-git (requires telegram-desktop)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3
ItachiSan commented on 2020-07-06 14:29 (UTC)
ItachiSan commented on 2020-06-16 10:14 (UTC)
Given the logs I cannot say what is the issue. On my test machine everything worked fine.
aminvakil commented on 2020-06-04 15:52 (UTC) (edited on 2020-06-04 15:55 (UTC) by aminvakil)
I've faced this error during building:
ItachiSan commented on 2019-08-12 08:02 (UTC)
Hi @everyone, Was on a business trip until Saturday. Will update the package ASAP.
Pinned Comments
ItachiSan commented on 2024-02-25 17:35 (UTC)
Hi, Just wanted to inform you that I am unable to build the package due to the incredibly high RAM usage at linking phase; with a bare boot of 800MB RAM, 16GB available and 6GB of swap I am unable to link the final binary.
I will report upstream the issue and link it here, however as of today until any improvement happens I won't be able to verify the building of the package e.g. see that the final binary is linked and packaged.