| Summary: | emerge sync stopped working after portage update | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Karl-Robert Ernst <karl.r.ernst> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Disregard that, the issue somehow fixed itself and its working now. Sorry to have bothered you. |
Unfortunately I can't say for sure which version of portage broke it, but I remember that some of the portage-2.2_rc8x still worked. After downgrading to that, emerge --sync worked again. Reproducible: Always Steps to Reproduce: Actual Results: Error message: !!! getaddrinfo failed for '[fe80': [Errno -3] Temporary failure in name resolution rsync: failed to connect to fe80::2%eth1: Network is unreachable (101) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.7] !!! Exhausted addresses for [fe80 >>> Starting rsync with rsync://[fe80::2%eth1]/gentoo-portage... >>> Checking server timestamp ... >>> Retrying... make.conf contains as sync address: SYNC="rsync://[fe80::2%eth1]/gentoo-portage"