From: Efraim Flashner <efraim@flashner.co.il>
To: BonfaceKilz <me@bonfacemunyoki.com>
Cc: 45977@debbugs.gnu.org
Subject: [bug#45977] [PATCH 0/1] gnu: guile-redis: Update to 2.0.0.
Date: Tue, 19 Jan 2021 21:26:14 +0200 [thread overview]
Message-ID: <YAcyViXJdogyaDvI@3900XT> (raw)
In-Reply-To: <20210118223926.184363-1-me@bonfacemunyoki.com>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Tue, Jan 19, 2021 at 01:39:25AM +0300, BonfaceKilz wrote:
> Hi! Find attached an update to guile-redis that adds proper support for Redis
> Pub/Sub.
>
> BonfaceKilz (1):
> gnu: guile-redis: Update to 2.0.0.
>
> gnu/packages/guile-xyz.scm | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
This update breaks guile2.0-redis. The configure script still checks for
2.0 so I'm not sure if that's intentional. Can you look into it?
Alternatively, I'm not seeing guile2.0-redis used by any packages in
guix, but I'm not sure about just dropping it.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-19 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 22:39 [bug#45977] [PATCH 0/1] gnu: guile-redis: Update to 2.0.0 BonfaceKilz
2021-01-18 22:39 ` [bug#45976] [PATCH 1/1] " BonfaceKilz
2021-01-19 19:26 ` Efraim Flashner [this message]
2021-01-20 6:47 ` [bug#45977] [PATCH 0/1] " Bonface Munyoki K.
2021-01-26 10:42 ` [bug#45977] [PATCH v2 0/2] " BonfaceKilz
2021-01-26 10:42 ` [bug#45977] [PATCH v2 1/2] " BonfaceKilz
2021-01-26 10:42 ` [bug#45977] [PATCH v2 2/2] gnu: guile2.0-redis: Revert to 1.3.0 BonfaceKilz
2021-01-27 9:21 ` bug#45977: [PATCH v2 0/2] gnu: guile-redis: Update to 2.0.0 Efraim Flashner
2021-01-27 9:40 ` [bug#45977] " Bonface Munyoki K.
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=YAcyViXJdogyaDvI@3900XT \
--to=efraim@flashner.co.il \
--cc=45977@debbugs.gnu.org \
--cc=me@bonfacemunyoki.com \
/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.