all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Cc: 52975@debbugs.gnu.org
Subject: [bug#52975] [PATCH] gnu: guile-ssh: Update to 0.15.0
Date: Mon, 28 Feb 2022 11:45:07 +0100	[thread overview]
Message-ID: <87ee3nfex8.fsf@gnu.org> (raw)
In-Reply-To: <87r18882io.fsf@gmail.com> (Artyom V. Poptsov's message of "Sat,  12 Feb 2022 19:37:19 +0300")

Hi Artyom,

"Artyom V. Poptsov" <poptsov.artyom@gmail.com> skribis:

> It seems that I fixed the error.
>
> $ cd guix
> $ guix shell -D guix
> $ ./pre-inst-env guix package --no-offload -f ../../projects/guile-ssh/guix.scm
> $ ./pre-inst-env guix offload test
> [...]
> guix offload: successfully imported '/gnu/store/bf73m6ns9d2v6m4173y0ls5jz9fcxfhv-import-test' [...]
>
> Please check this branch:
>   https://github.com/artyom-poptsov/guile-ssh/tree/fix-segfault-on-remote-close
>
> and let me know if it works for you.

It does!  I tested a few things manually and everything is working as
expected AFAICS (I built Guix with ‘guix build guix
--with-branch=guile-ssh=fix-segfault-on-remote-close’ and then used
‘guix offload test’ and ‘guix copy’ from there.)

Let me know when the new release is out and we can upgrade at that
point.

Thank you!

Ludo’.




  reply	other threads:[~2022-02-28 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 11:06 [bug#52975] [PATCH] gnu: guile-ssh: Update to 0.15.0 Artyom V. Poptsov
2022-01-06 11:37 ` Ludovic Courtès
2022-01-26 14:44   ` Ludovic Courtès
2022-02-12 16:37     ` Artyom V. Poptsov
2022-02-28 10:45       ` Ludovic Courtès [this message]
2022-02-28 20:00         ` Artyom V. Poptsov
2022-03-01 17:27           ` bug#52975: " Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=87ee3nfex8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=52975@debbugs.gnu.org \
    --cc=poptsov.artyom@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.