From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 25304-done@debbugs.gnu.org, ng0@libertad.pw
Subject: bug#25304: Seeking advice: preparing releases on GuixSD.
Date: Tue, 31 Jan 2017 22:03:14 +0100 [thread overview]
Message-ID: <87y3xrdjsd.fsf@gnu.org> (raw)
In-Reply-To: <878tqx7zzj.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 31 Dec 2016 00:34:40 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> “ltmain.sh” is instantiated from a template by libtool. It originally
>> contains a /bin/sh shebang, and I think it should not be patched when
>> installed to
>>
>> /gnu/store/…-libtool-2.4.6/share/libtool/build-aux/ltmain.sh
>>
>> This seems like a bug to me.
>
> Definitely:
>
> $ head -1 $(find $(guix build libtool) -name ltmain.sh)
> #!/gnu/store/qkw4zrwfybxww8f56nkb6hggxambk89b-bash-4.4.0/bin/sh
>
> Opening a new bug now. This is with v0.12.0-176-ge087671.
This was fixed by ng0 in 98341757c8c45fca8d2b53f9972f5c6a32cf2c95.
Ludo’.
next prev parent reply other threads:[~2017-01-31 21:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 13:35 Seeking advice: preparing releases on GuixSD ng0
2016-12-23 17:04 ` Alex Kost
2016-12-23 17:34 ` ng0
2016-12-24 10:13 ` Ricardo Wurmus
2016-12-24 14:45 ` ng0
2016-12-24 15:32 ` Ricardo Wurmus
2016-12-24 16:13 ` ng0
2016-12-24 16:23 ` Ricardo Wurmus
2016-12-24 16:34 ` ng0
2016-12-26 13:58 ` Ricardo Wurmus
2016-12-26 14:27 ` ng0
2016-12-30 23:34 ` Ludovic Courtès
2017-01-31 21:03 ` Ludovic Courtès [this message]
2017-04-21 14:30 ` bug#25304: Libtool’s ltmain.sh still contains a /gnu/store shebang Ludovic Courtès
2020-11-13 15:32 ` Miguel Ángel Arruga Vivas
2020-11-15 11:08 ` Ludovic Courtès
2020-11-16 16:17 ` Miguel Ángel Arruga Vivas
2016-12-24 22:26 ` Seeking advice: preparing releases on GuixSD ng0
2016-12-25 12:37 ` Ricardo Wurmus
2016-12-26 12:41 ` ng0
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=87y3xrdjsd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25304-done@debbugs.gnu.org \
--cc=ng0@libertad.pw \
--cc=rekado@elephly.net \
/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.