View previous topic :: View next topic |
Author |
Message |
rkfsm Tux's lil' helper
Joined: 03 Jun 2005 Posts: 100 Location: Charleston, SC, USA
|
Posted: Wed Apr 17, 2013 10:18 pm Post subject: Manifest issues in new install [Somewhat solved] |
|
|
Hi
I am doing a fresh install on a new computer. The ONLY file that I have tweaked is make.conf (below). Otherwise the system, freshly extracted from a stage 3 tarball, and portage snapshot are all unmodified.
emerge --sync gives me:
Quote: | Number of files: 165042
Number of files transferred: 174
Total file size: 281.49M bytes
Total transferred file size: 1.45M bytes
Literal data: 1.45M bytes
Matched data: 0 bytes
File list size: 3.81M
File list generation time: 0.009 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 44.96K
Total bytes received: 4.41M
sent 44.96K bytes received 4.41M bytes 84.86K bytes/sec
total size is 281.49M speedup is 63.18
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9]
>>> Retrying...
>>> Starting retry 1 of 1 with rsync://[2001:48a8:0:8:0:3:0:232]/gentoo-portage
>>> Checking server timestamp ...
rsync: failed to connect to 2001:48a8:0:8:0:3:0:232 (2001:48a8:0:8:0:3:0:232): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
>>> Retrying...
!!! Exhausted addresses for rsync24.us.gentoo.org
|
and any emerge command (i.e. emerge -uD world) gives me:
Quote: | Calculating dependencies... done!
>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: '/usr/portage/virtual/udev/udev-197-r2.ebuild'
|
Last edited by rkfsm on Thu Apr 18, 2013 10:49 pm; edited 1 time in total |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9645 Location: almost Mile High in the USA
|
Posted: Wed Apr 17, 2013 10:35 pm Post subject: |
|
|
It looks like your portage rsync failed, is your network setup properly?
Unfortunately I don't know much about ipv6 so I can't help there.
After portage rsyncs properly I suspect the manifest file problem should go away... _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21490
|
Posted: Thu Apr 18, 2013 1:15 am Post subject: |
|
|
OP may be one of those unfortunate users who has enough of an IPv6 stack that the tools try to use it, but not enough of one that it actually provides full connectivity. OP: what is the output of ifconfig? Am I correct to assume that your NIC was configured via DHCP? |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Thu Apr 18, 2013 9:19 am Post subject: |
|
|
Try :
Code: | echo 'PORTAGE_RSYNC_EXTRA_OPTS = "-4"' >> /etc/portage/make.conf |
|
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Apr 18, 2013 6:47 pm Post subject: |
|
|
krinn wrote: | Code: | echo 'PORTAGE_RSYNC_EXTRA_OPTS = "-4"' >> /etc/portage/make.conf |
|
krinn ... that will actually have rsync prefer ipv4 ... to prefer ipv6 you would use PORTAGE_RSYNC_EXTRA_OPTS="-6". Also, it should be noted that the ipv6 useflag is not enabled by default (at least with my profile), so perhaps something for the OP to look into.
best ... khay |
|
Back to top |
|
|
rkfsm Tux's lil' helper
Joined: 03 Jun 2005 Posts: 100 Location: Charleston, SC, USA
|
Posted: Thu Apr 18, 2013 10:48 pm Post subject: Manifest issues in new install [Somewhat solved] |
|
|
I resolved this with a web resync and got the system to boot from the hard drive for the first time. Now the network adapter is not recognized even with genkernel. I will post about this other issue in a more appropriate forum. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21490
|
Posted: Fri Apr 19, 2013 2:12 am Post subject: |
|
|
khayyam wrote: | krinn wrote: | Code: | echo 'PORTAGE_RSYNC_EXTRA_OPTS = "-4"' >> /etc/portage/make.conf |
|
krinn ... that will actually have rsync prefer ipv4 ... to prefer ipv6 you would use PORTAGE_RSYNC_EXTRA_OPTS="-6". Also, it should be noted that the ipv6 useflag is not enabled by default (at least with my profile), so perhaps something for the OP to look into. | If we assume that I was right (and the OP neither confirmed nor denied that I was), then attempting to use IPv6 was his problem and krinn's suggestion to force use of IPv4 is a good one. |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Fri Apr 19, 2013 9:38 am Post subject: |
|
|
Hu wrote: | If we assume that I was right (and the OP neither confirmed nor denied that I was), then attempting to use IPv6 was his problem and krinn's suggestion to force use of IPv4 is a good one. |
Hu ... no doubt, I'd just assumed that the OP *was* using ipv6 as I've never had any issue with rsync using ipv4 even though I have the ipv6 useflag set and no -4 defined in PORTAGE_RSYNC_EXTRA_OPTS. This may be as I have enable_ipv6="false" defined in net for certain networks, I can't say.
best ... khay |
|
Back to top |
|
|
|