unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Patched shebangs in Autoconf-provided scripts
Date: Mon, 30 Aug 2021 22:47:53 -0400	[thread overview]
Message-ID: <87bl5ejpnq.fsf@gmail.com> (raw)
In-Reply-To: <87a6kya5xa.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Tue, 31 Aug 2021 01:06:41 +0200")

Hi Ludo,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> There was a problem where these files had embedded file names:
>>
>> guix-1.3.0rc2.5207-ce515/build-aux/config.guess:#!/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh
>> guix-1.3.0rc2.5207-ce515/build-aux/config.sub:#!/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh
>> guix-1.3.0rc2.5207-ce515/build-aux/install-sh:#!/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh
>> error: store file names embedded in the distribution
>>
>> I had not seen this issue and it'll need to be investigated.  For now I
>> disabled the check to get the dist archive produced.
>
> These three files are installed by ‘autoreconf -i’ (unless already
> present), and I’m afraid our automake/autoconf packages ship them with
> those shebangs:
>
> $ head -1 $(find $(guix build autoconf) -name config.guess)
> #!/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh
> $ head -1 $(find $(guix build autoconf) -name config.sub)
> #!/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh
> $ head -1 $(find $(guix build automake) -name install-sh)
> #!/bin/sh
>
> So automake is good thanks to its ‘unpatch-shebangs’ phase (maybe your
> ‘install-sh’ file predates that fix?), but autoconf is not.  Reported!

Thanks for reporting the issue :-).  It'll be one to fix before the
release.

> Anyway, the simple solution is to manually edit those three files so
> they read #!/bin/sh and you’ll be fine!

Yep, the purpose of the test here was simply producing a dist archive to
see what was in so it was not critical, but it'll come back in the
picture as soon as we enter release mode :-).

Thanks,

Maxim


      reply	other threads:[~2021-08-31  2:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 20:22 GNU Guix 1.3.0rc2 available for testing! Maxim Cournoyer
2021-05-09 16:25 ` Leo Famulari
2021-05-10  0:46   ` Maxim Cournoyer
2021-05-10 14:49   ` Leo Famulari
2021-05-12 11:03 ` Chris Marusich
2021-05-14 16:07   ` Maxim Cournoyer
2021-06-03  8:46     ` Chris Marusich
2021-08-03 14:41       ` Maxim Cournoyer
2021-08-27 19:00       ` Maxim Cournoyer
2021-08-30 23:06         ` Patched shebangs in Autoconf-provided scripts Ludovic Courtès
2021-08-31  2:47           ` Maxim Cournoyer [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=87bl5ejpnq.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).