From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Collin Funk <collin.funk1@gmail.com>
Subject: Re: Can we have gnulib-tool.py emit the same copyright header?
Date: Wed, 28 Feb 2024 03:26:59 +0100 [thread overview]
Message-ID: <7024084.N7aMVyhfb1@nimes> (raw)
In-Reply-To: <77a35fc5-e06c-45e7-ab8f-d52a8b91519f@gmail.com>
Collin Funk wrote:
> I tried to run --version and got this:
>
> [collin@debian gnulib]$ gnulib-tool.py --version
> Traceback (most recent call last):
> File "/home/collin/.local/src/gnulib/pygnulib/main.py", line 1197, in <module>
> main()
> File "/home/collin/.local/src/gnulib/pygnulib/main.py", line 442, in main
> % (info.package(), info.date(), version, info.copyright(),
> ^^^^^^^^^^^
> File "/home/collin/.local/src/gnulib/pygnulib/GLInfo.py", line 109, in date
> result = pattern.findall(result)[0]
> ~~~~~~~~~~~~~~~~~~~~~~~^^^
> IndexError: list index out of range
Huh? For me, it works fine:
$ ./gnulib-tool.py --version
gnulib-tool (GNU gnulib 2024-02-27 23:33:49) 0.1.7153-431d6
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Bruno Haible, Paul Eggert, Simon Josefsson, and Dmitry Selyutin.
$ python3 --version
Python 3.10.12
$ git --version
git version 2.34.1
$ git log -n 1 ChangeLog | grep ^Date:
Date: Wed Feb 28 00:33:49 2024 +0100
Bruno
next prev parent reply other threads:[~2024-02-28 2:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 1:41 Can we have gnulib-tool.py emit the same copyright header? Collin Funk
2024-02-28 2:07 ` Bruno Haible
2024-02-28 2:19 ` Collin Funk
2024-02-28 2:26 ` Bruno Haible [this message]
2024-02-28 2:51 ` Collin Funk
2024-02-28 7:53 ` Collin Funk
2024-02-28 11:00 ` Bruno Haible
2024-02-28 21:18 ` Collin Funk
2024-02-28 21:30 ` Bruno Haible
2024-02-28 21:48 ` Collin Funk
2024-02-28 23:34 ` 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=7024084.N7aMVyhfb1@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).