From: Saku Laesvuori via Guix-patches via <guix-patches@gnu.org>
To: Distopico <distopico@riseup.net>
Cc: rg@raghavgururajan.name, 64748@debbugs.gnu.org, hako@ultrarare.space
Subject: [bug#64748] [PATCH] gnu: webrtc-for-telegram-desktop: Update to a45d8b8
Date: Thu, 20 Jul 2023 22:33:53 +0300 [thread overview]
Message-ID: <20230720193353.gb75xe2ywl6nfvnr@X-kone> (raw)
In-Reply-To: <20230720171841.31901-1-distopico@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
> Fixes telegram-desktop call not working with openSSL 3
>
> see: https://github.com/telegramdesktop/tdesktop/issues/26108
>
> * gnu/packages/telegram.scm (webrtc-for-telegram-desktop): Update to a45d8b8 revision commit
You should probably mention adding `libsrtp-for-telegram-desktop` in the
ChangeLog.
> @@ -96,6 +97,21 @@ (define libyuv-for-telegram-desktop
> (base32
> "0mm56p8iapfild2xdw4w8zi35c3xm06fgagiali644gnxdmnym6c")))))
>
> +(define libsrtp-for-telegram-desktop
> + (let ((commit "a566a9cfcd619e8327784aa7cff4a1276dc1e895")
> + (revision "1494"))
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/cisco/libsrtp")
> + (commit commit)))
> + (file-name (git-file-name
> + "libsrtp-for-telegram-desktop"
> + (git-version "0" revision commit)))
> + (sha256
> + (base32
> + "1ichw2v9s2mggi5p2wbbmlg55q4r48dxi3ks7ykfcfkmh7pb1w1s")))))
> +
Have you tried using the libsrtp version packaged in Guix as an input to
`webrtc-for-telegram-desktop` instead of bundling it? If that doesn't
work, have you tried packaging libsrtp 2.5.0 and using it as an input?
It would probably be relatively easy with record inheriting.
I'm quite new to Guix (and couldn't push changes even if they were
perfect) so someone else might have more comments on this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-20 19:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 17:18 [bug#64748] [PATCH] gnu: webrtc-for-telegram-desktop: Update to a45d8b8 Distopico
2023-07-20 19:33 ` Saku Laesvuori via Guix-patches via [this message]
2023-07-20 20:21 ` Distopico
2023-07-20 21:06 ` Saku Laesvuori via Guix-patches via
2023-07-20 23:09 ` Distopico
2023-07-21 7:22 ` Saku Laesvuori via Guix-patches via
2023-07-22 6:36 ` Raghav Gururajan via Guix-patches via
2023-07-22 8:25 ` Saku Laesvuori via Guix-patches via
2023-07-24 17:07 ` Distopico
2023-07-24 20:17 ` Raghav Gururajan via Guix-patches via
2023-07-26 7:24 ` Saku Laesvuori via Guix-patches via
2023-07-26 18:54 ` Distopico
2023-07-20 23:26 ` [bug#64748] [PATCH v2] " Distopico
2023-07-26 18:54 ` [bug#64748] [PATCH v3] " Distopico
2023-07-26 19:13 ` Saku Laesvuori via Guix-patches via
2023-07-26 19:22 ` Distopico
2023-07-26 19:21 ` [bug#64748] [PATCH v4] " Distopico
2023-07-26 20:09 ` Saku Laesvuori via Guix-patches via
2023-08-05 2:59 ` [bug#64748] [PATCH] " Distopico
2023-08-07 9:38 ` Hilton Chain via Guix-patches via
2023-08-07 12:26 ` Hilton Chain via Guix-patches via
2023-08-28 13:30 ` [bug#64748] [PATCH v6 0/2] gnu: webrtc-for-telegram-desktop: Update to 0-389.0532942 Hilton Chain via Guix-patches via
2023-08-28 13:31 ` [bug#64748] [PATCH v6 1/2] gnu: libyuv-for-telegram-desktop: Update to 0-2439.77c2121 Hilton Chain via Guix-patches via
2023-08-28 13:31 ` [bug#64748] [PATCH v6 2/2] gnu: webrtc-for-telegram-desktop: Update to 0-389.0532942 Hilton Chain via Guix-patches via
2023-08-28 14:56 ` [bug#64748] [PATCH v7 0/2] " Hilton Chain via Guix-patches via
2023-08-28 15:00 ` [bug#64748] [PATCH v7 1/2] gnu: libyuv-for-telegram-desktop: Update to 0-2439.77c2121 Hilton Chain via Guix-patches via
2023-08-28 15:00 ` [bug#64748] [PATCH v7 2/2] gnu: webrtc-for-telegram-desktop: Update to 0-389.0532942 Hilton Chain via Guix-patches via
2023-08-29 18:13 ` Distopico
2023-09-01 9:01 ` bug#64748: " Hilton Chain via Guix-patches via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230720193353.gb75xe2ywl6nfvnr@X-kone \
--to=guix-patches@gnu.org \
--cc=64748@debbugs.gnu.org \
--cc=distopico@riseup.net \
--cc=hako@ultrarare.space \
--cc=rg@raghavgururajan.name \
--cc=saku@laesvuori.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.