emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#69778: closed ([PATCH gnome-team] gnu: telegram: Build with glibmm@2


From: GNU bug Tracking System
Subject: bug#69778: closed ([PATCH gnome-team] gnu: telegram: Build with glibmm@2.76.)
Date: Sat, 16 Mar 2024 11:07:03 +0000

Your message dated Sat, 16 Mar 2024 11:04:27 +0000
with message-id <877ci2sahu.fsf@cbaines.net>
and subject line Re: [bug#69778] [PATCH gnome-team v2 0/2] Make the glibmm-2.76 
variable public in (gnu packages glib)
has caused the debbugs.gnu.org bug report #69778,
regarding [PATCH gnome-team] gnu: telegram: Build with glibmm@2.76.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
69778: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=69778
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH gnome-team] gnu: telegram: Build with glibmm@2.76. Date: Wed, 13 Mar 2024 17:45:07 +0100 User-agent: Evolution 3.48.4
* gnu/packages/telegram.scm (glibmm-for-telegram-desktop): New variable.
(telegram-desktop): Use glibmm-for-telegram-desktop instead of glibmm.

Change-Id: I0ec4ebc549dd867db22d68ee6317d1630cf1bfd8
---

Dear Guix,

While we are waiting for the telegram-desktop update in #67493, here is a
minimally intrusive way to keep it working on gnome-team, by using an older
version of glibmm.

Best regards,

Vivien

 gnu/packages/telegram.scm | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/telegram.scm b/gnu/packages/telegram.scm
index 7d02824efa..16d36b2c7c 100644
--- a/gnu/packages/telegram.scm
+++ b/gnu/packages/telegram.scm
@@ -74,7 +74,9 @@ (define-module (gnu packages telegram)
   #:use-module ((guix licenses) #:prefix license:)
   #:use-module (guix packages)
   #:use-module (guix gexp)
+  #:use-module (guix download)
   #:use-module (guix git-download)
+  #:use-module (guix utils)
   #:use-module (guix build-system cmake)
   #:use-module (guix build-system copy)
   #:use-module (guix build-system glib-or-gtk)
@@ -267,6 +269,21 @@ (define tgcalls-for-telegram-desktop
      (base32
       "193m2gkvipijqbfd6a8mhg9nd63wlnshzgspk3pip57vk21l709z"))))
 
+(define-public glibmm-for-telegram-desktop
+  (hidden-package
+   (package
+     (inherit glibmm)
+     (name "glibmm-for-telegram-desktop")
+     (version "2.76.0")
+     (source (origin
+               (method url-fetch)
+               (uri (string-append "mirror://gnome/sources/glibmm/"
+                                   (version-major+minor version)
+                                   "/glibmm-" version ".tar.xz"))
+               (sha256
+                (base32
+                 "1cia8vrpwzn8zwalws42mga5hi965840m5s8dvfzv55xx86dhdw6")))))))
+
 (define-public webrtc-for-telegram-desktop
   (let ((commit "0532942ac6176a66ef184fb728a4cbb02958fc0b")
         (revision "389"))
@@ -500,7 +517,7 @@ (define-public telegram-desktop
            fcitx5-qt
            ffmpeg
            glib
-           glibmm
+           glibmm-for-telegram-desktop
            gtk+
            hime
            hunspell

base-commit: 2ee54513196bad8e663e78ac695b6ffa0da49051
-- 
2.41.0



--- End Message ---
--- Begin Message --- Subject: Re: [bug#69778] [PATCH gnome-team v2 0/2] Make the glibmm-2.76 variable public in (gnu packages glib) Date: Sat, 16 Mar 2024 11:04:27 +0000 User-agent: mu4e 1.10.8; emacs 29.1
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Donnerstag, dem 14.03.2024 um 19:06 +0100 schrieb Vivien Kraus:
>> Dear Guix,
>> 
>> Telegram-desktop wants to be built with glibmm@2.76. I originally
>> added it to (gnu packages telegram), but in this revision, I add it
>> to (gnu packages glib).  What do you think?
>
> I won't be able to build it on my machine, but assuming you tested it
> LGTM.

Thanks both, I've pushed this to gnome-team as
aa9aebce615f014070797e7068baca40b4f25c37.

Chris

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]