From: Paul Eggert <eggert@cs.ucla.edu>
To: Simon Josefsson <simon@josefsson.org>
Cc: Bruno Haible <bruno@clisp.org>, Reuben Thomas <rrt@sc3d.org>,
bug-gnulib <bug-gnulib@gnu.org>, Paul Smith <psmith@gnu.org>
Subject: Re: GNULIB_REVISION
Date: Thu, 25 Apr 2024 11:49:34 -0700 [thread overview]
Message-ID: <0f3fcc57-19d8-484a-b7a8-5ddd04000284@cs.ucla.edu> (raw)
In-Reply-To: <87edatbaon.fsf@kaka.sjd.se>
On 4/25/24 10:43, Simon Josefsson wrote:
> https://gitlab.com/gsasl/inetutils/-/jobs/6706396721
That's an malloc failure on the server side. The savannah admins should
be told about the issue soon after it happens. Routine clones of GNU
projects shouldn't fail like that. (It's never happened to me, but then
I don't clone from Savannah all that often - maybe Savannah is giving
less server memory to clients that seem to hog?)
> Btw, using --depth 1 is incompatible with gnulib's git-version-gen
We could fix that by not requiring git-version-gen for the Gnulib
submodule. git-version-gen is pretty useless for that anyway, as for
Gnulib it currently outputs a string like "0.1.7513-648ae" which is not
much more useful than the commit ID
"648aeb575db7af9ddd51cf17d1b56ee91e9ef3c5".
>> Isn't the real problem that we don't put (for example) gzip's own
>> commit ID into the coreutils tarball? If we did that, Gnulib's commit
>> ID would come for free, since it can be derived from gzip's commit ID.
>
> I suppose you meant s/coreutils/gzip/
Yes, sorry.
> SHA1 git
> commits aren't long-term stable either, since SHA1 is broken
As you say, they're good enough for now. And anyway I would think SHA1
is good enough longer term unless an adversary infects your Git
repository (and in that case you probably have bigger problems...).
next prev parent reply other threads:[~2024-04-25 18:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:27 'relocatable' project built without --enable-relocatable Reuben Thomas
2024-04-23 19:46 ` Bruno Haible
2024-04-23 19:58 ` Reuben Thomas
2024-04-23 23:24 ` Bruno Haible
2024-04-24 20:36 ` Reuben Thomas
2024-04-25 12:07 ` Bruno Haible
2024-04-25 12:22 ` Reuben Thomas
2024-04-23 23:51 ` Gnulib in Debian Bruno Haible
2024-04-24 11:26 ` Reuben Thomas
2024-04-24 13:56 ` Simon Josefsson via Gnulib discussion list
2024-04-24 19:15 ` Reuben Thomas
2024-04-25 13:29 ` GNULIB_REVISION Bruno Haible
2024-04-25 16:26 ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 17:00 ` GNULIB_REVISION Paul Eggert
2024-04-25 17:43 ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 18:49 ` Paul Eggert [this message]
2024-04-25 17:48 ` GNULIB_REVISION Collin Funk
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=0f3fcc57-19d8-484a-b7a8-5ddd04000284@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=psmith@gnu.org \
--cc=rrt@sc3d.org \
--cc=simon@josefsson.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.
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).