From: "louis brazeau" <lbrazeau@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can't emerge --sync
Date: Wed, 17 May 2006 19:08:46 -0400 [thread overview]
Message-ID: <bb1a21350605171608s3faad342u692a2f17510a1232@mail.gmail.com> (raw)
In-Reply-To: <20060515224556.GA7021@localhost>
On 5/15/06, Pablo Antonio <pabloa@gmail.com> wrote:
> On 13:02 Mon 15 May , Matias Grana wrote:
> > > On 10:30 Mon 15 May , Matias Grana wrote:
> > > > hi;
> > > > Beginning a week ago or so, I can't emerge --sync anymore. It always
> > > > quits with a timeout error. Like this:
> > > >
> > > > receiving file list ...
> > > > 143979 files to consider
> > > > rsync error: timeout in data send/receive (code 30) at io.c(171) [sender=2.6.8]
> > > > rsync: connection unexpectedly closed (3358508 bytes received so far) [receiver]
> > > > rsync error: error in rsync protocol data stream (code 12) at io.c(463) [receiver=2.6.8]
> > > > rsync: connection unexpectedly closed (3358508 bytes received so far) [generator]
> > > > rsync error: error in rsync protocol data stream (code 12) at io.c(463) [generator=2.6.8]
> > > > >>> retry ...
> >
I had the same problem and re-emerging rsync solved it.
Good luck!
--
Louis Brazeau
Informaticien
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-05-17 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 13:30 [gentoo-user] can't emerge --sync Matias Grana
2006-05-15 14:19 ` Pablo Antonio
2006-05-15 14:37 ` Neil Bothwick
2006-05-15 16:02 ` Matias Grana
2006-05-15 22:45 ` Pablo Antonio
2006-05-17 23:08 ` louis brazeau [this message]
2006-05-15 22:16 ` [gentoo-user] " James
-- strict thread matches above, loose matches on Subject: below --
2017-07-15 10:00 [gentoo-user] Can't " Peter Humphrey
2017-07-15 10:05 ` Adam Carter
2017-07-15 10:14 ` Daniel Wagener
2017-07-15 13:11 ` Peter Humphrey
2017-07-15 14:07 ` Marc Joliet
2017-07-15 15:47 ` Peter Humphrey
2017-12-15 11:44 ` Marc Joliet
2017-07-15 10:22 ` Alexander Kapshuk
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=bb1a21350605171608s3faad342u692a2f17510a1232@mail.gmail.com \
--to=lbrazeau@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