unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 65642-done@debbugs.gnu.org
Subject: bug#65642: Update lcrq to 0.1.2
Date: Tue, 05 Sep 2023 20:51:33 -0400	[thread overview]
Message-ID: <87edjcf7je.fsf_-_@gmail.com> (raw)
In-Reply-To: <87il8uu8u9.fsf@wireframe> (Vagrant Cascadian's message of "Thu,  31 Aug 2023 15:48:30 -0700")

Hello,

Vagrant Cascadian <vagrant@debian.org> writes:

> And in the meantime, upstream snuck in a new release with some minor
> fixes. May as well update to that!
>
> Both lcsync and librecast still build fine!
>
> live well,
>   vagrant
>
> From 3454b360a107aba20ee00e7d5fc0d56177704d58 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagrant@debian.org>
> Date: Thu, 31 Aug 2023 15:43:14 -0700
> Subject: [PATCH] gnu: lcrq: Update to 0.1.2.
>
> * gnu/packages/networking.scm (lcrq): Update to 0.1.2.
> ---

Installed!

-- 
Thanks,
Maxim




      reply	other threads:[~2023-09-06  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  0:57 [bug#65642] Update lcrq to 0.1.1 Vagrant Cascadian
     [not found] ` <handler.65642.B.169344350313166.ack@debbugs.gnu.org>
2023-08-31 22:48   ` [bug#65642] Update lcrq to 0.1.2 Vagrant Cascadian
2023-09-06  0:51     ` Maxim Cournoyer [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edjcf7je.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=65642-done@debbugs.gnu.org \
    --cc=vagrant@debian.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).