The automated build on GitHub Actions is no longer working. It seems unrelated to this particular package -- some permissions bug related buildah/fakeroot/overlayfs/something.
If anyone can help figure it out, thanks!
Search Criteria
Package Details: telegram-desktop-userfonts-bin 4.16.8-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/telegram-desktop-userfonts-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | telegram-desktop-userfonts-bin |
| Description: | Official Telegram Desktop client, with your fonts as set by fontconfig |
| Upstream URL: | https://desktop.telegram.org/ |
| Licenses: | GPL3 |
| Conflicts: | telegram-desktop |
| Provides: | telegram-desktop |
| Submitter: | andykluger |
| Maintainer: | andykluger |
| Last Packager: | andykluger |
| Votes: | 5 |
| Popularity: | 0.28 |
| First Submitted: | 2020-10-29 04:24 (UTC) |
| Last Updated: | 2024-04-21 06:29 (UTC) |
Dependencies (25)
- abseil-cpp (abseil-cpp-gitAUR)
- ffmpeg (ffmpeg-intel-full-gitAUR, ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-gitAUR, ffmpeg-cudaAUR, ffmpeg-decklinkAUR, ffmpeg-amd-fullAUR, ffmpeg-full-gitAUR, ffmpeg-nocudaAUR, ffmpeg-ffplayoutAUR, ffmpeg-obsAUR, ffmpeg-amd-full-gitAUR, ffmpeg-fullAUR, ffmpeg-headlessAUR, ffmpeg-libfdk_aacAUR)
- 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)
- openssl (openssl-gitAUR, openssl-staticAUR)
- pipewire (pipewire-common-gitAUR, pipewire-full-gitAUR, pipewire-gitAUR)
- protobuf (protobuf-gitAUR)
- qt6-imageformats
- qt6-svg
- Show 5 more dependencies...
Required by (2)
- purpose-git (requires telegram-desktop) (optional)
- tmulti-git (requires telegram-desktop)
Sources (1)
andykluger commented on 2024-02-11 16:34 (UTC)
akshettrj commented on 2024-01-30 07:50 (UTC)
Hi, the binary cannot launch because the major libvpx version was recently bumped in Arch Linux repos. Hence, the binary needs to be rebuilt. Thanks in advance.
akshettrj commented on 2023-12-01 21:34 (UTC)
The binary for version 4.11.8 is not able to launch and I think it is due to incompatibility with latest QT6 version. Can you please bump the version to 4.12.2 (latest) and trigger the rebuild on GitHub.
I tried building it and it successfully compiled and launched just a few minutes ago
hydrocryo01 commented on 2023-07-13 01:59 (UTC) (edited on 2023-07-13 02:00 (UTC) by hydrocryo01)
When I run telegram-desktop in my terminal it returns an not-found error
telegram-desktop: error while loading shared libraries: libprotobuf-lite.so.32: cannot open shared object file: No such file or directory
Am I missing something here? I have protobuf installed, but what's in /usr/lib was libprotobuf-lite.so.23
gutmunchies commented on 2023-04-17 16:02 (UTC)
Maybe a dumb question, but how come this depends on ttf-opensans if it's supposed to use my fontconfig?
blacksuan19 commented on 2022-09-26 16:12 (UTC)
I have build the latest telegram-desktop with required patches for userfonts, the binary package can be found on github releases
https://github.com/Blacksuan19/archbuilder_telegram-desktop-userfonts
inator commented on 2022-07-26 16:35 (UTC)
telegram-desktop: error while loading shared libraries: libabsl_strings.so.2111.0.0: cannot open shared object file: No such file or directory
This was fixed in telegram-desktop, according to this bug report: https://bugs.archlinux.org/task/75380
Please see the two commits on July 20 on the telegram-desktop PKGBUILD: https://github.com/archlinux/svntogit-community/commits/packages/telegram-desktop/trunk
andykluger commented on 2022-02-04 15:10 (UTC)
The reason this one hasn't caught up to 3.5.0 is because the following bug breaks the automated build:
Pinned Comments
andykluger commented on 2024-02-11 16:34 (UTC)
The automated build on GitHub Actions is no longer working. It seems unrelated to this particular package -- some permissions bug related buildah/fakeroot/overlayfs/something.
If anyone can help figure it out, thanks!