Bug 5497

Summary:	Telegram requires a rebuild for Fedora 31 testing
Product:	Fedora	Reporter:	James <fedora>
Component:	telegram-desktop	Assignee:	Vitaly <vitaly>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	adhisimon
Priority:	P1
Version:	f31
Hardware:	x86_64
OS:	GNU/Linux
namespace:

Description James 2019-12-27 10:34:29 CET

Fedora 31 testing repo has moved to QT 5.13, which is incompatible with the latest telegram-desktop build.

 Problem 1: package telegram-desktop-1.8.15-2.fc31.x86_64 requires qt5-qtbase(x86-64) = 5.12.5, but none of the providers can be installed
  - cannot install both qt5-qtbase-5.13.2-1.fc31.x86_64 and qt5-qtbase-5.12.5-2.fc31.x86_64
  - cannot install both qt5-qtbase-5.12.5-2.fc31.x86_64 and qt5-qtbase-5.13.2-1.fc31.x86_64
  - cannot install both qt5-qtbase-5.12.5-1.fc31.x86_64 and qt5-qtbase-5.13.2-1.fc31.x86_64
  - cannot install the best update candidate for package telegram-desktop-1.8.15-2.fc31.x86_64
  - cannot install the best update candidate for package qt5-qtbase-5.12.5-2.fc31.x86_64
 Problem 2: problem with installed package telegram-desktop-1.8.15-2.fc31.x86_64
  - package telegram-desktop-1.8.15-2.fc31.x86_64 requires libQt5Gui.so.5(Qt_5.12.5_PRIVATE_API)(64bit), but none of the providers can be installed
  - cannot install both qt5-qtbase-gui-5.13.2-1.fc31.x86_64 and qt5-qtbase-gui-5.12.5-2.fc31.x86_64
  - cannot install both qt5-qtbase-gui-5.12.5-2.fc31.x86_64 and qt5-qtbase-gui-5.13.2-1.fc31.x86_64
  - cannot install both qt5-qtbase-gui-5.12.5-1.fc31.x86_64 and qt5-qtbase-gui-5.13.2-1.fc31.x86_64
  - cannot install the best update candidate for package qt5-qtbase-gui-5.12.5-2.fc31.x86_64

Comment 1 Vitaly 2019-12-27 13:33:53 CET

Thanks for report, but we can rebuild Telegram Desktop only when Qt 5.13.2 will reach stable.

Comment 2 James 2020-01-09 23:05:08 CET

QT 5.13.2 has now been pushed to stable.

Comment 3 Vitaly 2020-01-09 23:23:34 CET

Fixed in telegram-desktop-1.9.3-1.fc31.

Comment 4 Vitaly 2020-01-14 09:13:03 CET

*** Bug 5518 has been marked as a duplicate of this bug. ***