From: Vagrant Cascadian <vagrant@debian.org>
To: 74659-done@debbugs.gnu.org
Cc: "Josselin Poiret" <dev@jpoiret.xyz>,
"Simon Tournier" <zimon.toutoune@gmail.com>,
"Vagrant Cascadian" <vagrant@debian.org>,
"Mathieu Othacehe" <othacehe@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>,
"Tobias Geerinckx-Rice" <me@tobias.gr>,
"Christopher Baines" <guix@cbaines.net>,
"Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Subject: bug#74659: Update guile-ssh to 0.18.0
Date: Mon, 09 Dec 2024 12:17:24 -0800 [thread overview]
Message-ID: <87bjxkvcff.fsf@wireframe> (raw)
In-Reply-To: <875xnvrxir.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
On 2024-12-07, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
>
>> The attached patch updates guile-ssh to 0.18.0.
>>
>> This allows it to build successfully with libssh 0.11.x, which is not
>> yet in guix master but paves the way for an easier upgrade of libssh.
>
> Nice.
>
>> From 1630e401c11aa956e459a5320951935e80602511 Mon Sep 17 00:00:00 2001
>> From: Vagrant Cascadian <vagrant@debian.org>
>> Date: Mon, 2 Dec 2024 13:38:06 -0800
>> Subject: [PATCH] gnu: guile-ssh: Update to 0.18.0.
>>
>> * gnu/packages/ssh.scm (guile-ssh): Update to 0.18.0.
>> [source]: Drop patch, fixed upstream.
>> * gnu/packages/patches/guile-ssh-rename-bool.patch: Remove patch.
>> * gnu/local.mk (dist_patch_DATA): Update with removed patch.
>
> LGTM! :-)
Pushed as da3c8a963f83c044568d99921480259eaa26a923.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-12-09 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 23:57 [bug#74659] Update guile-ssh to 0.18.0 Vagrant Cascadian
2024-12-04 22:37 ` Vagrant Cascadian
2024-12-07 21:30 ` Ludovic Courtès
2024-12-09 20:17 ` Vagrant Cascadian [this message]
2024-12-09 20:24 ` Artyom V. Poptsov
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=87bjxkvcff.fsf@wireframe \
--to=vagrant@debian.org \
--cc=74659-done@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=poptsov.artyom@gmail.com \
--cc=zimon.toutoune@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).