unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonas Freimuth <jonas.freimuth@posteo.de>
To: 58417@debbugs.gnu.org
Subject: bug#58417: Installer script no longer works with `yes` utility
Date: Mon, 10 Oct 2022 15:33:44 +0000	[thread overview]
Message-ID: <9e3dc221-9013-d58a-402b-696b117a99a6@posteo.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Package: guix

Version: 1.4.0

Severity: important

Heyo,

I use the github `guix-install-action` 
(https://github.com/PromyLOPh/guix-install-action), which internally 
runs the `guix-install.sh` script non-interactively, via the yes utility:

```{bash}

bash -c 'yes | bash guix-install.sh'

```

However, since commit `6a2e303d3a49baf7c222a70b91f453e9efd456c6` 
(https://git.savannah.gnu.org/cgit/guix.git/commit/etc/guix-install.sh?id=6a2e303d3a49baf7c222a70b91f453e9efd456c6), 
this apparently causes the entire action to hang (leading to eventual 
termination by github).

I confirmed this behaviour by running the "Download", "Fetch Key", and 
"Install Guix" steps of the `guix-install-action` as root on a WSL2 
instance of Ubuntu20.04 (using todays wsl rootfs from 
https://cloud-images.ubuntu.com/focal/current/).

Running

```{bash}

sudo --preserve-env=GUIX_BINARY_FILE_NAME -- bash -c 'bash guix-install.sh'

```

instead of

```{bash}

sudo --preserve-env=GUIX_BINARY_FILE_NAME -- bash -c 'yes | bash 
guix-install.sh'

```

i.e. running the script interactively works fine.

Is this intended, or is there another suggested way to run the 
`guix-install.sh` script non-interactively?

Best wishes,

Jonas

[-- Attachment #2: Type: text/html, Size: 2258 bytes --]

             reply	other threads:[~2022-10-10 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 15:33 Jonas Freimuth [this message]
2022-10-11 16:04 ` bug#58417: Installer script no longer works with `yes` utility 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=9e3dc221-9013-d58a-402b-696b117a99a6@posteo.de \
    --to=jonas.freimuth@posteo.de \
    --cc=58417@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).