From: "Ludovic Courtès" <ludo@gnu.org>
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
Cc: 25304@debbugs.gnu.org
Subject: bug#25304: Libtool’s ltmain.sh still contains a /gnu/store shebang
Date: Sun, 15 Nov 2020 12:08:26 +0100 [thread overview]
Message-ID: <87v9e6andh.fsf@gnu.org> (raw)
In-Reply-To: <87v9e9z30r.fsf@gmail.com> ("Miguel Ángel Arruga Vivas"'s message of "Fri, 13 Nov 2020 16:32:04 +0100")
Hi!
Miguel Ángel Arruga Vivas <rosen644835@gmail.com> skribis:
> I was looking through the lists because I have a patch that does exactly
> what you describe here. I guess this goes to core updates, so this
> version is on top of it. WDYT?
Yes, looks like a change for ‘core-updates’.
> From 145273418d3131bcf3b73d416d19f641645cf3f8 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?=
> <rosen644835@gmail.com>
> Date: Fri, 13 Nov 2020 15:24:46 +0100
> Subject: [PATCH] gnu: libtool: Restore shebangs on all libtoolize files.
You can add “Fixes <https://bugs.gnu.org/25304>.”
> * gnu/packages/autotools.scm (libtool)[restore-build-aux-shebang]: New
> phase after install.
> [restore-ltmain-shebang]: Remove phase, it is now performed by the phase
> restore-build-aux-shebang.
LGTM, thanks for digging through old bugs!
Ludo’.
next prev parent reply other threads:[~2020-11-15 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874m1uvkdz.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <874m1ty6rd.fsf@elephly.net>
[not found] ` <87a8blpeqs.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <871swxxrzc.fsf@elephly.net>
2016-12-30 23:34 ` Seeking advice: preparing releases on GuixSD Ludovic Courtès
2017-01-31 21:03 ` bug#25304: " Ludovic Courtès
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 [this message]
2020-11-16 16:17 ` Miguel Ángel Arruga Vivas
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=87v9e6andh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25304@debbugs.gnu.org \
--cc=rosen644835@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 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).