From: Vagrant Cascadian <vagrant@debian.org>
To: 65642@debbugs.gnu.org
Subject: [bug#65642] Update lcrq to 0.1.1
Date: Wed, 30 Aug 2023 17:57:47 -0700 [thread overview]
Message-ID: <87v8cwt4dw.fsf@wireframe> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 151 bytes --]
The attached patch updates lcrq to 0.1.1.
The two dependent packages, librecast and lcsync both build fine with
the newer lcrq.
live well,
vagrant
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-gnu-lcrq-Update-to-0.1.1.patch --]
[-- Type: text/x-diff, Size: 1231 bytes --]
From e8525bb82f35c6251991130f4a64fc99f0bba69f Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@debian.org>
Date: Wed, 30 Aug 2023 17:54:09 -0700
Subject: [PATCH] gnu: lcrq: Update to 0.1.1.
* gnu/packages/networking.scm (lcrq): Update to 0.1.1.
---
gnu/packages/networking.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/networking.scm b/gnu/packages/networking.scm
index f4ecd85009..936d249565 100644
--- a/gnu/packages/networking.scm
+++ b/gnu/packages/networking.scm
@@ -256,7 +256,7 @@ (define-public axel
(define-public lcrq
(package
(name "lcrq")
- (version "0.1.0")
+ (version "0.1.1")
(source (origin
(method git-fetch)
(uri (git-reference
@@ -265,7 +265,7 @@ (define-public lcrq
(file-name (git-file-name name version))
(sha256
(base32
- "13mfg866scvy557zrvjxjhkzam39h8d07s2w3fqbwhw6br6axkxk"))))
+ "09dnr3hmhkd7frd5w0mds6069damshn9hrrvmwasrppr4hfydxqs"))))
(build-system gnu-build-system)
(arguments
`(#:parallel-tests? #f
base-commit: d6966b8a5b4f2ddda2bc685b9642e7a1c2cbe17c
--
2.39.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2023-08-31 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 0:57 Vagrant Cascadian [this message]
[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 ` bug#65642: " Maxim Cournoyer
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=87v8cwt4dw.fsf@wireframe \
--to=vagrant@debian.org \
--cc=65642@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 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).