{"id":99305,"date":"2021-03-02T10:22:55","date_gmt":"2021-03-02T08:22:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/mejntejnery-fedora-i-gentoo-otkazalis-ot-soprovozhdeniya-paketov-s-telegram-desktop"},"modified":"2021-03-02T10:22:55","modified_gmt":"2021-03-02T08:22:55","slug":"mejntejnery-fedora-i-gentoo-otkazalis-ot-soprovozhdeniya-paketov-s-telegram-desktop","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/mejntejnery-fedora-i-gentoo-otkazalis-ot-soprovozhdeniya-paketov-s-telegram-desktop","title":{"rendered":"The maintainers of Fedora and Gentoo have discontinued support for packages with Telegram Desktop","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The maintainer of the Telegram Desktop packages for Fedora and RPM Fusion has announced the removal of the packages from the repositories. A day prior, the maintainer for Gentoo also announced the discontinuation of support for Telegram Desktop. In both cases, there is a willingness to return the packages to the repositories if a new maintainer can be found who is ready to take over the maintenance. <\/p>\n
The reasons cited for the withdrawal of support for Telegram Desktop by its current maintainers include the developers' unwelcoming and hostile attitude, as they do not even attempt to address the errors that lead to issues with building their source code in Linux distributions. Reports of such errors are immediately closed with a \"WONTFIX\" label and a recommendation to use semi-proprietary binary builds from the official website. <\/p>\n
The situation is exacerbated by the fact that problems preventing the building of packages regularly arise in new releases, and all attempts to address shortcomings in upstream result in statements that the developers only support their own static builds and all problems when creating custom builds should be resolved independently. For example, support for builds with Qt versions beyond 5.15 has recently been discontinued, and all inquiries with suggestions on how to address the resulting issue have simply been ignored. <\/p>\n
It is also noted that the overall confusion in the organization of the Telegram Desktop build complicates maintenance. The project is divided into four different repositories (the application, the library for WebRTC, scripts for the CMake build system, and the library for audio processing), but only one repository produces releases, while the other three are merely updated as development progresses without fixing their state. Additionally, building is complicated by dependency conflicts that arise when trying to support Wayland and x11, PulseAudio and ALSA, OpenSSL and LibreSSL. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"