| 1 |
Mark Knecht wrote: |
| 2 |
> On Jan 29, 2008 4:21 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 3 |
>> On Tue, 29 Jan 2008 16:16:25 -0800, Mark Knecht wrote: |
| 4 |
>> |
| 5 |
>>> First step would be eix-sync which is |
| 6 |
>>> failing with only a message |
| 7 |
>>> |
| 8 |
>>> problems running time emerge --sync |
| 9 |
>> Run emerge --sync directly so you can see the actual error message. |
| 10 |
>> |
| 11 |
>> |
| 12 |
>> -- |
| 13 |
>> Neil Bothwick |
| 14 |
> |
| 15 |
> Hi Neil, |
| 16 |
> Thanks. It looks like the following. I guess I'll keep trying. What |
| 17 |
> I'm not understanding is why my other machines don't have a problem |
| 18 |
> but this one does. Possibly because it has a bigger update to do? |
| 19 |
> |
| 20 |
> Maybe I should run my own portage server here for our 6 home machines? |
| 21 |
> |
| 22 |
> - Mark |
| 23 |
> |
| 24 |
> dev-php/PEAR-HTML_Common/PEAR-HTML_Common-1.2.4.ebuild |
| 25 |
> dev-php/PEAR-HTML_Common2/ChangeLog |
| 26 |
> dev-php/PEAR-HTML_Common2/Manifest |
| 27 |
> dev-php/PEAR-HTML_Common2/PEAR-HTML_Common2-2.0.0_beta1.ebuild |
| 28 |
> dev-php/PEAR-HTML_Javascript/ChangeLog |
| 29 |
> dev-php/PEAR-HTML_Javascript/Manifest |
| 30 |
> io timeout after 180 seconds -- exiting |
| 31 |
> rsync error: timeout in data send/receive (code 30) at io.c(165) |
| 32 |
> [receiver=2.6.9] |
| 33 |
> rsync: connection unexpectedly closed (3195946 bytes received so far) |
| 34 |
> [generator] |
| 35 |
> rsync error: error in rsync protocol data stream (code 12) at |
| 36 |
> io.c(458) [generator=2.6.9] |
| 37 |
>>>> Retrying... |
| 38 |
> |
| 39 |
> |
| 40 |
>>>> Starting retry 1 of 3 with rsync://64.127.121.98/gentoo-portage |
| 41 |
>>>> Checking server timestamp ... |
| 42 |
> timed out |
| 43 |
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 44 |
> rsync.c(276) [receiver=2.6.9] |
| 45 |
>>>> Retrying... |
| 46 |
> |
| 47 |
> |
| 48 |
>>>> Starting retry 2 of 3 with rsync://140.211.166.165/gentoo-portage |
| 49 |
>>>> Checking server timestamp ... |
| 50 |
> rsync: connection unexpectedly closed (0 bytes received so far) [receiver] |
| 51 |
> rsync error: error in rsync protocol data stream (code 12) at |
| 52 |
> io.c(458) [receiver=2.6.9] |
| 53 |
>>>> Retrying... |
| 54 |
> |
| 55 |
> |
| 56 |
>>>> Starting retry 3 of 3 with rsync://134.68.220.73/gentoo-portage |
| 57 |
>>>> Checking server timestamp ... |
| 58 |
> timed out |
| 59 |
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 60 |
> rsync.c(276) [receiver=2.6.9] |
| 61 |
> |
| 62 |
> !!! Rsync has not successfully finished. It is recommended that you keep |
| 63 |
> !!! trying or that you use the 'emerge-webrsync' option if you are unable |
| 64 |
> !!! to use rsync due to firewall or other restrictions. This should be a |
| 65 |
> !!! temporary problem unless complications exist with your network |
| 66 |
> !!! (and possibly your system's filesystem) configuration. |
| 67 |
> |
| 68 |
> Sector9 ~ # |
| 69 |
|
| 70 |
Have you tried a different mirror? It looks like the mirror you are |
| 71 |
using is having a problem based on the rsync errors. |
| 72 |
-- |
| 73 |
gentoo-user@l.g.o mailing list |
Archives