From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: 36673@debbugs.gnu.org
Subject: [bug#36673] Update telegram-purple
Date: Mon, 15 Jul 2019 20:01:03 +0200 [thread overview]
Message-ID: <4c5960ee-0401-ac2c-886e-012f9dad675e@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-telegram-purple-Update-to-1.4.1.patch --]
[-- Type: text/x-patch; name="0001-gnu-telegram-purple-Update-to-1.4.1.patch", Size: 1343 bytes --]
From 98cf4fbcf48c70cc85673f0ea7ea18372833fb89 Mon Sep 17 00:00:00 2001
From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Date: Mon, 15 Jul 2019 19:51:01 +0200
Subject: [PATCH] gnu: telegram-purple: Update to 1.4.1.
* gnu/packages/messaging.scm (telegram-purple): Update to 1.4.1.
---
gnu/packages/messaging.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm
index 503781a9eb..afe62eb680 100644
--- a/gnu/packages/messaging.scm
+++ b/gnu/packages/messaging.scm
@@ -1855,7 +1855,7 @@ messaging that aren’t available to clients that connect over XMPP.")
(define-public telegram-purple
(package
(name "telegram-purple")
- (version "1.3.1")
+ (version "1.4.1")
(home-page "https://github.com/majn/telegram-purple")
(source (origin
(method git-fetch)
@@ -1865,7 +1865,7 @@ messaging that aren’t available to clients that connect over XMPP.")
(recursive? #t)))
(sha256
(base32
- "0p93jpjpx7hszwffzgixw04zkrpsiyzz4za3gfr4j07krc4771fp"))
+ "0xlmqnlp2dqkgsq052d6dwgvqbwch2w0dnwpjslk5na4ih3lfr7k"))
(modules '((guix build utils)))
(snippet
'(begin
--
2.22.0
next reply other threads:[~2019-07-15 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 18:01 Jonathan Brielmaier [this message]
2019-07-17 13:15 ` bug#36673: Update telegram-purple Ludovic Courtès
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=4c5960ee-0401-ac2c-886e-012f9dad675e@web.de \
--to=jonathan.brielmaier@web.de \
--cc=36673@debbugs.gnu.org \
/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.