bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Collin Funk <collin.funk1@gmail.com>, bug-gnulib@gnu.org
Subject: gnulib-tool.py in gettext
Date: Wed, 10 Apr 2024 13:26:49 +0200	[thread overview]
Message-ID: <8335772.3ujTIJ0xDA@nimes> (raw)

Hi Collin,

Can you please look into this one?

$ export GNULIB_TOOL_IMPL=sh+py
$ git clone https://git.savannah.gnu.org/git/gettext.git
$ sh -x ./autogen.sh
...
+ .../gnulib-tool --copy-file tests/init.sh gettext-tools
.../gnulib-tool: *** gnulib-tool.py produced different files than gnulib-tool.sh! Compare .../gettext and .../glpybdZoLD.
.../gnulib-tool: *** Stop.

The Python implementation has created a tests/ directory instead of a
gettext-tools/tests/ directory.

Bruno





             reply	other threads:[~2024-04-10 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 11:26 Bruno Haible [this message]
2024-04-10 13:04 ` gnulib-tool.py in gettext Collin Funk
2024-04-10 14:33   ` Bruno Haible
2024-04-13  1:41 ` Collin Funk
2024-04-13  1:51   ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8335772.3ujTIJ0xDA@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=collin.funk1@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.
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).