public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Switched from rsync to git, now emerge --sync fails
Date: Wed, 13 Oct 2021 18:50:10 -0000 (UTC)	[thread overview]
Message-ID: <sk79p2$2gt$1@ciao.gmane.io> (raw)
In-Reply-To: 20211013193716.3f8f4988@digimed.co.uk

On 2021-10-13, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 13 Oct 2021 18:25:12 -0000 (UTC), Grant Edwards wrote:
>
>> Yesterday I switched my gentoo repo from rsync to git, and the initial
>> --sync with an empty directory did a git clone successfully.
>> 
>> Today, when I try to sync, it always fails:
>> 
>>   $ sudo emerge --sync >>> Syncing repository 'gentoo' into
>> '/var/db/repos/gentoo'... /usr/bin/git fetch origin
>>   error: RPC failed; HTTP 504 curl 22 The requested URL returned error:
>> 504 fatal: the remote end hung up unexpectedly
[...]

>> After the initial sync which does a git clone, how do you do
>> subsequent sync operations?
>
> emerge --sync works here. What do you have in repos.conf?

I didn't have a sync-depth setting. Setting that to 1 fixed the
problem. It was apparently timing out because it takes too long for
the server to respond to a fetch with an unlimited depth.  Seems like
maybe it ought to default to 1? Is there some reason it should default
to doing unlimited depth fetch operations?

--
Grant






  reply	other threads:[~2021-10-13 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 18:25 [gentoo-user] Switched from rsync to git, now emerge --sync fails Grant Edwards
2021-10-13 18:37 ` Neil Bothwick
2021-10-13 18:50   ` Grant Edwards [this message]
2021-10-13 19:35     ` [gentoo-user] " Neil Bothwick
2021-10-13 20:11     ` Rich Freeman
2021-10-14  2:50       ` Grant Edwards
2021-10-14  8:22         ` Peter Humphrey
2021-10-14  8:28           ` Miles Malone
2021-10-14  9:52             ` Wol

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='sk79p2$2gt$1@ciao.gmane.io' \
    --to=grant.b.edwards@gmail.com \
    --cc=gentoo-user@lists.gentoo.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