From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>, git@vger.kernel.org
Subject: Re: fetch failure from git2.kernel.org?
Date: Sun, 22 Apr 2007 11:26:01 -0700 [thread overview]
Message-ID: <7virbonu4m.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <alpine.LFD.0.98.0704221050350.9964@woody.linux-foundation.org> (Linus Torvalds's message of "Sun, 22 Apr 2007 10:53:13 -0700 (PDT)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Sun, 22 Apr 2007, Randal L. Schwartz wrote:
>>
>> is this known? transient?
>
> Junio seems to have tightened his permissions on kernel.org, and as a
> result the most recent pack is unreadable by anybody but him (I'm not sure
> if such private files even get mirrored out - but even if they do, they
> will get mirrored out with the same tight permissions and won't be
> readable).
That's not *me* per-se, it's Nico ;-).
Anybody who runs the new pack-objects that has been cooking in
'next' would get this.
I think this patch minimally fixes it, but some existing tests
(e.g. t5300) assume that pack/idx are writable which makes them
break.
diff --git a/builtin-pack-objects.c b/builtin-pack-objects.c
index c72e07a..4eb88e8 100644
--- a/builtin-pack-objects.c
+++ b/builtin-pack-objects.c
@@ -1783,11 +1783,17 @@ int cmd_pack_objects(int argc, const char **argv, const char *prefix)
write_index_file(last_obj_offset, object_list_sha1);
snprintf(tmpname, sizeof(tmpname), "%s-%s.pack",
base_name, sha1_to_hex(object_list_sha1));
+ if (chmod(pack_tmp_name, 0444))
+ die("unable to make temporary pack file readable: %s",
+ strerror(errno));
if (rename(pack_tmp_name, tmpname))
die("unable to rename temporary pack file: %s",
strerror(errno));
snprintf(tmpname, sizeof(tmpname), "%s-%s.idx",
base_name, sha1_to_hex(object_list_sha1));
+ if (chmod(idx_tmp_name, 0444))
+ die("unable to make temporary index file readable: %s",
+ strerror(errno));
if (rename(idx_tmp_name, tmpname))
die("unable to rename temporary index file: %s",
strerror(errno));
prev parent reply other threads:[~2007-04-22 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 10:03 fetch failure from git2.kernel.org? Randal L. Schwartz
2007-04-22 12:53 ` Alex Riesen
2007-04-22 12:56 ` Randal L. Schwartz
2007-04-22 14:20 ` Petr Baudis
2007-04-22 17:53 ` Linus Torvalds
2007-04-22 18:26 ` Junio C Hamano [this message]
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=7virbonu4m.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=torvalds@linux-foundation.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 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.