From: Vagrant Cascadian <vagrant@debian.org>
To: David Pflug <david@pflug.io>
Cc: 74095@debbugs.gnu.org
Subject: [bug#74095] [PATCH] gnu: fish: Update to 3.7.1.
Date: Tue, 29 Oct 2024 16:30:39 -0700 [thread overview]
Message-ID: <87ttcu7ahs.fsf@wireframe> (raw)
In-Reply-To: <cf23be511ef2ef3419b459c305d466b2359e76c9.1730235498.git.david@pflug.io>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
On 2024-10-29, David Pflug wrote:
> * gnu/packages/shells.scm (fish): Update to 3.7.1.
Tested locally, and works for me! Thanks!
I also tried building the dependent packages for x86_64-linux, and it
introduced no new failures; python-numba and related dependents do not
build with or without this patch applied.
I could push in a couple days if nobody else finds any issue.
live well,
vagrant
> Change-Id: Ife28992a9a66ee94be2e4ef5db25a65b7a6dd65e
> ---
> gnu/packages/shells.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/shells.scm b/gnu/packages/shells.scm
> index 43a1fbb540..733da2129b 100644
> --- a/gnu/packages/shells.scm
> +++ b/gnu/packages/shells.scm
> @@ -137,7 +137,7 @@ (define-public dash
> (define-public fish
> (package
> (name "fish")
> - (version "3.7.0")
> + (version "3.7.1")
> (source
> (origin
> (method url-fetch)
> @@ -145,7 +145,7 @@ (define-public fish
> "releases/download/" version "/"
> "fish-" version ".tar.xz"))
> (sha256
> - (base32 "1c9slg6azhc9jn1sb75wip4hl9zyibjy9nay505nkw0lnxw766yz"))))
> + (base32 "0l5jlg0vplqln7ijqwirp1xl4j9npimzm58k77grj1yd8db9yk31"))))
> (build-system cmake-build-system)
> (inputs
> (list fish-foreign-env ncurses pcre2
>
> base-commit: 653121e1abe7e5400d39b326522ea327d90c9e58
> --
> 2.41.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2024-10-29 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 20:58 [bug#74095] [PATCH] gnu: fish: Update to 3.7.1 David Pflug
2024-10-29 23:30 ` Vagrant Cascadian [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=87ttcu7ahs.fsf@wireframe \
--to=vagrant@debian.org \
--cc=74095@debbugs.gnu.org \
--cc=david@pflug.io \
/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).