From: Vagrant Cascadian <vagrant@debian.org>
To: 54165@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Taylan Kammer" <taylan.kammer@gmail.com>,
"Felix Lechner" <felix.lechner@lease-up.com>
Subject: [bug#54165] Update guile-bytestructures to 2.0.2.
Date: Tue, 20 Aug 2024 12:11:46 -0700 [thread overview]
Message-ID: <87seuzj9fx.fsf@wireframe> (raw)
In-Reply-To: <c48b47ba696a8068fda077c9a8e2a167bc21c677.1717767896.git.felix.lechner@lease-up.com>
[-- Attachment #1.1: Type: text/plain, Size: 435 bytes --]
The attached patch updates to guile-bytestructures 2.0.2.
I am not sure if the other previously suggested changes are still
needed; I did successfully build most of the packages listed by "guix
refresh --list-dependent" other than guix-jupyter... though I only
tested on x86_64. Hopefully QA picks this up and gives us better
information.
FWIW, the updated guile-bytestructures seems to work fine in Debian. :)
live well,
vagrant
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-gnu-guile-bytestructures-Update-to-2.0.2.patch --]
[-- Type: text/x-diff, Size: 1548 bytes --]
From 56dd4f2f1635c450bd62138c9c0e92f77427576f Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@debian.org>
Date: Tue, 20 Aug 2024 11:57:29 -0700
Subject: [PATCH] gnu: guile-bytestructures: Update to 2.0.2.
* gnu/packages/guile.scm (guile-bytestructures): Update to 2.0.2.
[source]: Adjust tag used to fetch git commit.
---
gnu/packages/guile.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
index e8705dc7d2..581f188dbe 100644
--- a/gnu/packages/guile.scm
+++ b/gnu/packages/guile.scm
@@ -786,17 +786,17 @@ (define-public guile2.2-sqlite3
(define-public guile-bytestructures
(package
(name "guile-bytestructures")
- (version "1.0.10")
+ (version "2.0.2")
(home-page "https://github.com/TaylanUB/scheme-bytestructures")
(source (origin
(method git-fetch)
(uri (git-reference
(url home-page)
- (commit version)))
+ (commit (string-append "v" version))))
(file-name (git-file-name name version))
(sha256
(base32
- "14k50jln32kkxv41hvsdgjkkfj6xlv06vc1caz01qkgk1fzh72nk"))))
+ "1dyhf39s16q3fvps0mfb65xrlcb8rk8m5kc82ngkwhzmf1svalpc"))))
(build-system gnu-build-system)
(arguments
`(#:make-flags '("GUILE_AUTO_COMPILE=0") ;to prevent guild warnings
base-commit: bef48dd553aef3c8fb3bc48143739debb629c825
--
2.39.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-08-20 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 20:51 [bug#54165] [PATCH] gnu: guile-bytestructures: Update to 2.0.1 Taylan Kammer
2022-03-01 11:38 ` Ludovic Courtès
2024-06-07 13:44 ` [bug#54165] [PATCH v2 1/2] " Felix Lechner via Guix-patches via
2024-08-20 19:11 ` Vagrant Cascadian [this message]
2024-06-07 13:44 ` [bug#54165] [PATCH v2 2/2] gnu: guile-bytestructures: add patch. (Closes: #54165) Felix Lechner 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
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=87seuzj9fx.fsf@wireframe \
--to=vagrant@debian.org \
--cc=54165@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=ludo@gnu.org \
--cc=taylan.kammer@gmail.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 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).