From: Stefan Monnier <monnier@iro.umontreal.ca>
To: git@vger.kernel.org
Subject: Re: [BUG] Destructive access to an "objects/info/alternates" repository
Date: Sun, 03 Jan 2021 11:50:35 -0500 [thread overview]
Message-ID: <jwv1rf26k9n.fsf-monnier+gmane.comp.version-control.git@gnu.org> (raw)
In-Reply-To: 20201229154403.xutnk2aoawdrjfwx@chatter.i7.local
>> FWIW, I just tried it with
>>
>> git clone --shared ~otheruser/nongnu
>>
>> and got the same result.
>> I also tried with another repository, still with the same result (tho
>> different pack.idx names, of course).
>
> I've tried several times to reproduce this, but I am unable to do so. You may
> need to provide the tarball with ~otheruser/nongnu contents for someone to be
> able to properly debug this.
OK, you can try with the following tarball:
https://www.iro.umontreal.ca/~monnier/nongnu.tar.gz
untar it (as "otheruser") into ~otheruser (which will create
~otheruser/nongnu) and then do (as your normal user):
git clone --shared ~otheruser/nongnu
cd nongnu
git gc
It "worked" (i.e. gave me the unlink failure warnings) for me, so
hopefully it will "work" for others as well.
The `git clone` will likely give you some message about HEAD not being
found, which is normal.
Stefan
next prev parent reply other threads:[~2021-01-03 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 18:50 [BUG] Destructive access to an "objects/info/alternates" repository Stefan Monnier
2020-12-28 19:00 ` Konstantin Ryabitsev
2020-12-28 19:29 ` Stefan Monnier
2020-12-28 20:17 ` Stefan Monnier
2020-12-29 15:44 ` Konstantin Ryabitsev
2021-01-03 16:50 ` Stefan Monnier [this message]
2021-01-04 13:54 ` Konstantin Ryabitsev
2021-01-04 20:47 ` Stefan Monnier
2021-01-04 21:20 ` Konstantin Ryabitsev
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=jwv1rf26k9n.fsf-monnier+gmane.comp.version-control.git@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=git@vger.kernel.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 NNTP newsgroup(s).