Version 2.5.2 is released 15 days ago and still it's not in portage trees. Reproducible: Always
please create one ticket per package next time, so we can close what is done.
Ok sorry I'm new to gentoo
Add also x86 keyword. I tried to build this package for x86 arch, and it works without any problems. I also added this in my /etc/portage/package.accept_keywords to emerge telegram-desktop: net-im/telegram-desktop ** media-libs/libtgvoip ** media-libs/tg_owt ** dev-cpp/range-v3 **
https://github.com/telegramdesktop/tdesktop/releases 2.5.2 is not a Release but a Pre-Release, that is why the -bin was not bumped and will not be for Pre-Releases. If there is a fix in a Pre-Release that you are waiting for, you might want to ask upstream to prepare a Release. (which they sometimes do on a daily basis ...) My guess is that Georgy has similar reasons to not bump.
Yes, sorry v2.5.2 is pre-release but 2.5.1 is stable released. It was my mistake. Latest version on repo is 2.4.7, I'm running 2.5.1 using custom ebuild.
*** Bug 764818 has been marked as a duplicate of this bug. ***
I'm just lacking time, I usually only avoid alphas, not betas. but stabilize only release versions. I'll try to bump to whatever latest versions is soon, but not sure when exatly.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5c9fc1812e0f19b6c730883c4a74f6e01e90909a commit 5c9fc1812e0f19b6c730883c4a74f6e01e90909a Author: Esteve Varela Colominas <esteve.varela@gmail.com> AuthorDate: 2021-03-25 17:34:05 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2021-03-25 19:29:48 +0000 net-im/telegram-desktop: Take maintainership, bump to 2.7.1 Bug: https://bugs.gentoo.org/763522 Closes: https://github.com/gentoo/gentoo/pull/20117 Signed-off-by: Esteve Varela Colominas <esteve.varela@gmail.com> Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> net-im/telegram-desktop/Manifest | 1 + .../telegram-desktop/files/fix-tgcalls-gcc10.patch | 34 ++++++ net-im/telegram-desktop/metadata.xml | 9 +- .../telegram-desktop/telegram-desktop-2.7.1.ebuild | 132 +++++++++++++++++++++ 4 files changed, 175 insertions(+), 1 deletion(-)
Both packages are bumped.
This doesn't build for me, failing on a cmake check. -- Checking for module 'glibmm-2.4' -- Package 'glibmm-2.4', required by 'virtual:world', not found CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:556 (message): A required package was not found Thinking it was a missing dependency, I installed dev-cpp/glibmm manually but it still fails. The tree only provides 2.64.2 and 2.68.0. Not sure if Telegram requires 2.4 explicitly here. Building with USE="X dbus gtk hunspell pulseaudio spell -enchant (-libressl) -wayland (-lto%*) (-webrtc%)".
(In reply to Petr Šabata from comment #10) > This doesn't build for me, failing on a cmake check. > > -- Checking for module 'glibmm-2.4' > -- Package 'glibmm-2.4', required by 'virtual:world', not found > CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:556 (message): > A required package was not found > > Thinking it was a missing dependency, I installed dev-cpp/glibmm manually > but it still fails. The tree only provides 2.64.2 and 2.68.0. Not sure if > Telegram requires 2.4 explicitly here. > > Building with USE="X dbus gtk hunspell pulseaudio spell -enchant (-libressl) > -wayland (-lto%*) (-webrtc%)". Can you file a new bug please with the full logs?
(In reply to Sam James from comment #11) > (In reply to Petr Šabata from comment #10) > > This doesn't build for me, failing on a cmake check. > > > > -- Checking for module 'glibmm-2.4' > > -- Package 'glibmm-2.4', required by 'virtual:world', not found > > CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:556 (message): > > A required package was not found > > > > Thinking it was a missing dependency, I installed dev-cpp/glibmm manually > > but it still fails. The tree only provides 2.64.2 and 2.68.0. Not sure if > > Telegram requires 2.4 explicitly here. > > > > Building with USE="X dbus gtk hunspell pulseaudio spell -enchant (-libressl) > > -wayland (-lto%*) (-webrtc%)". > > Can you file a new bug please with the full logs? Sure, submitted as #778290.
