Bug 2222901
Summary: | glibmm2.68-2.77.0 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | glibmm2.68 | Assignee: | Kalev Lember <klember> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | klember, vitaly |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glibmm2.68-2.77.0-1.fc39 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-07-24 11:24:48 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Upstream Release Monitoring
2023-07-14 12:02:26 UTC
Please update to 2.77.0 in all stable Fedora branches as Telegram Desktop now require this version: https://github.com/telegramdesktop/tdesktop/pull/26419 https://github.com/desktop-app/cmake_helpers/pull/286 No, sorry, we don't update glib2 to new major releases in stable Fedora branches. glib follows GNOME release schedule and both glib and GNOME stick to the same major release that was at release time. glibmm packages are C++ bindings for glib and follow the same versioning and cannot (usually) be updated without updating glib first. I understand this is a major headache for you, but I am not sure I can help. MAYBE we could do an exception this cycle and update glib and its bindings in F38 to 2.78.x once the stable releases are out (2.77.x are development snapshots and definitely not suitable for stable Fedoras), but that could earliest happen in September when the stable GNOME 45 release is scheduled. Some ideas: Can you put the new telegram version in rawhide and keep using older version in stable branches? Alternatively, you could bundle both glib and glibmm in a private directory (/usr/lib64/telegram/ or something, together with adding RPATH that points to the private directory) so that telegram picks up the new version, but the system-wide glib2/glibmm2.68 packages stay at the stable versions. Another idea would be to talk to upstream telegram and ask if they could stick with using stable glib 2.76.x API for now until 2.78.x is actually released. |