Installation script fails on distributions that use busybox

  • Done
  • quality assurance status badge
Details
2 participants
  • conses
  • Maxim Cournoyer
Owner
unassigned
Submitted by
conses
Severity
normal
C
C
conses wrote on 28 Oct 2022 22:30
(address . bug-guix@gnu.org)
86k04jsnb2.fsf@conses.eu
Hi,

Following the instructions in the manual, I attempted to install the
package manager in Alpine Linux via the official installation
script. However, after completing the first prompts I got the error
"mktemp: (null): Invalid argument". Upon closer inspection of the script
and busybox's `mktemp' help page, which states the following:

TEMPLATE must end with XXXXXX (e.g. [/dir/]nameXXXXXX)

It's clear that the script should be modified to account for this with
at least 6 "X" characters in the template, and this wouldn't pose a
problem with GNU's `mktemp' because it takes "at least" 3 of them.

--
Best regards,
conses
M
M
Maxim Cournoyer wrote on 16 Nov 2022 22:30
(name . conses)(address . contact@conses.eu)(address . 58858-done@debbugs.gnu.org)
87fseiio3d.fsf@gmail.com
Hi,

conses <contact@conses.eu> writes:

Toggle quote (14 lines)
> Hi,
>
> Following the instructions in the manual, I attempted to install the
> package manager in Alpine Linux via the official installation
> script. However, after completing the first prompts I got the error
> "mktemp: (null): Invalid argument". Upon closer inspection of the script
> and busybox's `mktemp' help page, which states the following:
>
> TEMPLATE must end with XXXXXX (e.g. [/dir/]nameXXXXXX)
>
> It's clear that the script should be modified to account for this with
> at least 6 "X" characters in the template, and this wouldn't pose a
> problem with GNU's `mktemp' because it takes "at least" 3 of them.

Thanks for the investigation and solution. Applied in 6aa5d1dc24, which
should now be live at https://guix.gnu.org/install.sh.

--
Thanks,
Maxim
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 58858@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 58858
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch