From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] GCC Upgrade Problems - Why does emerge --sync not work
Date: Fri, 4 Aug 2006 08:43:54 +0100 [thread overview]
Message-ID: <20060804084354.5d3fc528@hactar.digimed.co.uk> (raw)
In-Reply-To: <000e01c6b797$39059650$d302a8c0@NX6120>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
On Fri, 4 Aug 2006 17:25:13 +1000, Richard Watson wrote:
> >>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
> >>> Checking server timestamp ...
> rsync: failed to connect to 140.211.166.165: Connection refused (111)
> rsync error: error in socket IO (code 10) at clientserver.c(107)
> [receiver=2.6.8]
The server is refusing the connection, there's nothing wrong at your end
except you need to try a different rsync server.
--
Neil Bothwick
The severity of the itch is inversely proportional to the reach.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-04 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 7:25 [gentoo-user] GCC Upgrade Problems - Why does emerge --sync not work Richard Watson
2006-08-04 7:43 ` Neil Bothwick [this message]
2006-08-04 23:11 ` Richard Watson
2006-08-05 8:22 ` Richard Watson
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=20060804084354.5d3fc528@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--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